Sync User in External Application
Trigger a flow when an admin syncs users from an external application to Okta.
|Use App Instance ID?||Choose from
Choose the app to trigger a flow for when an admin syncs a user. Choose
Note: This displays a maximum of 1000 apps.
Choose from a list of existing application instances, dependent on the application chosen in the previous step.
Note: This displays a maximum of 2000 app instances. This event will only trigger for the selected application instance. If you don't see your application instance in the list use the Use App Instance ID? dropdown list and the App Instance ID field to be able to trigger the event for a specific application instance.
|Application Instance ID||
A unique app instance ID. Choose
To find the application instance ID for an app:
|Date and Time||Date and time the event was triggered in Okta API.||String|
|Message||Message details about the event.||String|
|Event ID||Event's unique identifier key.||String|
|Event Type||Type of event that was published.||String|
|Event Time||Timestamp when the notification was delivered to the service.||String|
|Admin||Okta admin who synced the user.||Object|
|ID||ID of the Okta admin who synced the user.||String|
|Alternate ID||Email address of the Okta admin.||String|
|Display Name||Display name of the Okta admin.||String|
|Okta User||Okta user who was synced.||Object|
|Alternate ID||User's email address.||String|
|Display Name||User's display name.||String|
|Type||Type of Okta user.||String|
|Application User||User's details for the target application.||Object|
|ID||User's ID in the target application.||String|
|Alternate ID||User's alternate ID in the target application (usually their email address).||String|
|Display Name||Display name of the user for the target application.||String|
|Type||Type of user in the target application.||String|
|ID||ID of the target application.||String|
|Alternate ID||Alternate ID of the target application.||String|
|Display Name||Display name of the target application.||String|
|Type||Type of the target application.||String|
|UUID||Webhook event's universal unique identifier.||String|
|Event Details||Raw JSON payload returned from the Okta API for this particular event.||Object|
|Headers||Object representing the headers for the response; each key of the header will be parsed into a header string as "key: value" (
|Source||Source of user-specific data.||Object|
|Debug Data||Information on the triggered event used for debugging; for example, returned data can include a URI, an SMS provider, or transaction ID.||Object|
While you can create additional user or group fields for an Okta event, the Okta API only supports four fields for Okta connector event cards: ID, Alternate ID, Display Name, and Type. Values will be returned for these four input fields only. No other fields are supported for users or groups, and data from such fields will not be returned by this event card.