User Account Locked
Trigger a flow when a user account auto-locks in Okta.
|Date and Time||Date and time the event was triggered in Okta.||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.||Date and Time|
|ID||Identifier of the Okta actor who granted the user privilege.||String|
|Alternate ID||Email address of the Okta actor.||String|
|Display Name||Display name of the Okta actor.||String|
|Type||Type of the Okta actor.||String|
|ID||Identifier of the Okta user unlocked.||String|
|Alternate ID||Alternate ID of the Okta user unlocked.||String|
|Display Name||Display name of the Okta user unlocked.||String|
|Type||Type of the Okta user unlocked.||String|
|UUID||Universal unique identifier of the Webhook event.||String|
|Event Details||Raw JSON payload returned from the Okta API for this event.||Object|
|Headers||Object representing the headers for the response. Each key of the header is parsed into a header string as "key: value" (
|Source||Source of user-specific data.||String|
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 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.