Application Activated

Trigger a flow when an application is activated in Okta.

Output

Field Definition Type
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
Version

Versioning indicator.

String
Admin Okta admin who activated the application. Object
ID ID of the Okta admin who activated the application. String
Alternate ID Email address of the Okta admin. String
Display Name Display name of the Okta admin. String
Type Role of the Okta admin.  
Authenticator Authenticator that was activated. Object
ID Unique identifier of the authenticator that was activated. String
Alternate ID Alternate ID of the authenticator that was activated. String
Display Name Display name of the authenticator that was activated. String
Type Activated authenticator type. String
     
UUID Webhook event's universal unique identifier. String
Event Details Raw JSON payload returned from the Okta API for this particular event. String
Headers Object representing the headers for the response; each key of the header will be parsed into a header string as "key: value" (Content-Type: text/plain). String
Source Source of user-specific data for the application. String
Debug Context
Debug Data Information on the triggered event used for debugging; for example, returned data can include a URI, an SMS provider, or transaction ID. String
Note

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.

Related topics

Okta connector

About the elements of Okta Workflows

Guidance for Okta connector

Okta API