User Account Locked
Trigger a flow when a user account auto-locks in Okta.
Scopes
See Event cards for the list of required OAuth scopes needed by this card.
Output
| Field | Definition | Type |
|---|---|---|
|
Date & Time |
Date and time the event was triggered in Okta. |
Text |
| Message | Message details about the event. |
Text |
| Event ID | Unique identifier of the event. |
Text |
| Event Type | Type of event that was published. |
Text |
| Event Time | Time stamp when the notification was delivered to the service. |
Date & Time |
| Version |
Versioning indicator. |
Text |
|
Actor |
||
| ID | Identifier of the Okta actor who granted the user privilege. |
Text |
| Alternate ID | Email address of the Okta actor. |
Text |
| Display Name | Display name of the Okta actor. |
Text |
| Type | Type of the Okta actor. |
Text |
|
Okta User |
||
| ID | Identifier of the Okta user being locked. |
Text |
| Alternate ID | Alternate ID of the Okta user being locked. |
Text |
| Display Name | Display name of the Okta user being locked. |
Text |
| Type | Type of the Okta user unlocked. |
Text |
| UUID | Universal unique identifier of the Webhook event. |
Text |
| 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" (Content-Type: text/plain). |
Object |
| Source | Source of user-specific data. |
Text |
|
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. |
Object |
While you can create more 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 this event card doesn't return data from such fields.