--- title: Attribute Collector node description: Collects user attribute values during a journey for use in registration or profile update flows in Advanced Identity Cloud. component: auth-node-ref version: latest page_id: auth-node-ref::attribute-collector canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/attribute-collector.html llms_txt: https://docs.pingidentity.com/auth-node-ref/llms.txt docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md revdate: 2026-06-04T17:39:33Z keywords: ["Nodes & Trees", "Journeys", "Authentication", "Schema", "Policy", "Custom Attributes"] page_aliases: ["auth-node-attribute-collector.adoc"] superseded_by: https://docs.pingidentity.com/auth-node-ref/latest/attribute-collector.html section_ids: example: Example add_date_and_datetime_fields_to_a_journey: Add date and datetime fields to a journey availability: Availability inputs: Inputs dependencies: Dependencies configuration: Configuration outputs: Outputs callbacks: Callbacks outcomes: Outcomes errors: Errors --- # Attribute Collector node The Attribute Collector node collects the values of attributes for use later in the flow. For example, to populate a new account during registration. This node supports three types of attributes:\ `string`\ `boolean`\ `number` To request a value, the attribute must be present and viewable in the identity schema for the current identity object. | | | | - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | You can find more information about the identity schema in [Advanced Identity Cloud identity schema](https://docs.pingidentity.com/pingoneaic/identities/identity-cloud-identity-schema.html). | The node lets you configure whether the attributes are required to continue and whether to use a policy filter to validate the input values. ## Example ### Add date and datetime fields to a journey The Attribute Collector node lets you add properties (attributes) that follow a date or datetime (date and time of day). The format of the date comes from the locale set in your browser. The following table displays the differences between date and datetime: | Display format | Managed object field format | Notes | | -------------- | ------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Date only | String formatExample: `frIndexedString1` | The format of the date comes from the locale set in your browser.For example, if the locale is English, then the format presented to the end user is `MM-DD-YYYY`. If the local is French, the format is `DD-MM-YYYY`. | | Date and time | String format (date and time of day)Example: `frIndexedDate1` | The format of the date comes from the locale set in your browser.For example, if the locale is English (United States), the format presented to the end user is `MM-DD-YYYY`. If the locale is French, the format is `DD-MM-YYYY`. You can only use the date general purpose extension attributes for datetime. Don't attempt to use the indexed date properties with the date format. | | | | | - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | The rendering of the date to the end user changes, depending on the locale set in the browser. However, the server *stores* the date value in UTC format as `YYYY-MM-DDHH:MM:SS`. For example, `2026-06-10T08:01:00Z`. | To render the date or datetime UI element to an end user with the Attribute Collector node, you must do the following: 1. Specify the property to use as date or datetime: * [General purpose extension attributes](https://docs.pingidentity.com/pingoneaic/identities/user-identity-properties-attributes-reference.html#general-purpose-extension-attributes). Recommended. Use OOTB indexed attributes: * Use the `String` indexed properties, such as `frIndexedString1` for date *only*. * Use the `Date` indexed properties, such as `frIndexedDate1` for datetime *only*. * [Create your own custom attributes](https://docs.pingidentity.com/pingoneaic/identities/customize-object-types.html#create-custom-properties). Create custom attributes, prefixed with `custom_`. 2. Apply formatting and policies to the property for `Date` or `Datetime`. 1. In the Advanced Identity Cloud admin UI, go to Identities > Configure > *object type*, for example, Alpha realm - User. 2. Switch to the Properties tab and select the property you specified. 3. Select one of the following from the Property Format list: * `Date` for a date property. * `Date/Time` for a datetime property. 4. On the Validation tab, select one of the following checkboxes: * Valid formatted date for a date property. * Valid datetime for a datetime property. 3. Add the property name to the Attributes to Collect field in the Attribute Collector node. For an in-depth use case, add the `date` or `datetime` property to an Attribute Collector node in a registration flow. The following video shows an example of a journey collecting the datetime from an end user using the Attribute Collector node: **Video (Video)** <\_images/mp4/attribute-collector-datetime.mp4> ## Availability | Product | Available? | | ---------------------------------------------- | ---------- | | PingOne Advanced Identity Cloud | Yes | | PingAM (self-managed) | Yes (1) | | Ping Advanced Identity Software (self-managed) | Yes | (1) This functionality requires that you configure AM as part of a [Ping Advanced Identity Software deployment](https://docs.pingidentity.com/platform/8.1/sample-setup/). ## Inputs For validation, this node reads the Identity Attribute (default: `userName`) from the shared node state. It uses the value to look up the identity object. It prompts the user for the attributes to collect. ## Dependencies None. ## Configuration | Property | Usage | | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Attributes to Collect | A list of the attributes to collect from the client. The attributes must exist in the identity schema for the current identity object.Default: none | | All Attributes Required | When enabled, all attributes collected in this node are required in order to continue.Default: Not enabled | | Validate Input | Select this option to validate the collected attributes against the validation policies specified for the property.Learn more in [Use policies to validate data](https://docs.pingidentity.com/pingoneaic/idm-objects/policies.html).If you enable this option, the collected attributes must be *user editable*.> **Collapse: How do I make an attribute user-editable?** > > 1. In the Advanced Identity Cloud admin UI, go to Identities > Configure > *object type*, for example, Alpha realm - User. > > 2. Switch to the Properties tab and select the property you want to make user-editable. > > 3. On the Display tab, select the Show in User-facing Form checkbox.Default: Not enabled | | Identity Attribute | The property used to locate the identity.Default: `userName` | ## Outputs The node writes the attributes and their values to the shared node state. ## Callbacks The node sends the following callbacks: * `BooleanAttributeInputCallback` Prompts the user to select a boolean value for the attribute being collected. * `NumberAttributeInputCallback` Prompts the user to enter a number value for the attribute being collected. * `StringAttributeInputCallback` Prompts the user to enter a string value for the attribute being collected. Learn more in [Supported callbacks](https://docs.pingidentity.com/pingoneaic/am-authentication/callbacks-supported.html). ## Outcomes Single outcome path; on success, downstream nodes can read the attributes from the shared node state. ## Errors This node doesn't log any error or warning messages of its own.