User Assigned to Application
Trigger a flow when a user is assigned to an application in Okta API.
|Use App Instance ID?||Choose from
Choose an app to trigger a flow for when a user is added to its membership. Choose
Note: The dropdown only displays 1000 apps.
Choose from a list of existing application instances, dependent on the application chosen in the previous step.
Note: The dropdown only displays 2000 app instances. This event will only trigger for the selected application instance. If you do not 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:The unique app instance ID.||
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||Unique identifier of the event.||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 assigned the user.||Object|
|ID||ID of the Okta admin who assigned the user.||String|
|Alternate ID||Email address of the Okta admin.||String|
|Display Name||Display name of the Okta admin.||String|
|Type||Type of the Okta admin.||String|
|Okta User||Okta user who was assigned to the application.||Object|
|ID||ID of the Okta user who was assigned to the application.||String|
|Alternate ID||Email address of the Okta user.||String|
|Display Name||Display name of the Okta user.||String|
|Type||Type of the Okta user.||String|
|Application User||Target application's user details.||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 application user.||String|
|Type||Type of the application user.||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 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.