Trigger a flow when a policy is activated in Okta API.
|Date and Time
|Date and time when the policy was activated in Okta API.
|Message details about the event.
|Event's unique identifier key.
|Type of event that was published.
|Timestamp when the notification was delivered to the service.
|Okta admin who activated the policy.
|Unique identifier of the Okta admin who activated the policy.
|Email address of the Okta admin.
|Display name of the Okta admin.
|Role of the Okta admin.
|Unique identifier of the Okta policy.
|Alternate ID of the Okta policy.
|Display name of the activated Okta policy.
|Policy type specification when creating a new policy. Specification pertains to source of user-specific data. Valid types include default, legacy, and Active Directory. For this event, the value is
|Type of policy. Valid types include:
|Webhook event's universal unique identifier.
|Raw JSON payload returned from the Okta API for this particular event.
|Object representing the headers for the response; each key of the header will be parsed into a header string as "key: value" (
|Source of user-specific data.
|Information on the triggered event used for debugging; for example, returned data can include a URI, an SMS provider, or transaction ID.
While you can create additional user or group fields for an Okta event, the Okta API only returns values for four fields: ID, Alternate ID, Display Name, and Type.
No other fields are supported for users or groups, and data from such fields isn't returned by this event card.