User Account Unlocked by Admin
Trigger a flow when an admin unlocks a user's account in Okta.
Scopes
See Event cards for the list of required OAuth scopes needed by this card.
Output
Field | Definition | Type |
---|---|---|
Output |
||
Date and Time |
The date and time the event was triggered in the Okta API. |
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. |
Text |
Version |
Versioning indicator. |
Text |
Admin |
Details about the Okta Admin who performed the unlock operation. |
Object |
ID |
ID of the Okta admin account. |
Text |
Alternate ID |
Email address of the Okta admin. |
Text |
Display Name |
Display the name of the Okta admin. |
Text |
Type |
Type of Okta admin. |
Text |
Okta User |
Details about the Okta user whose account was unlocked. |
Object |
ID |
The unique identifier of the Okta user. |
Text |
Alternate ID |
Email address of the Okta user. |
Text |
Display Name |
Display the name of the Okta user. |
Text |
Type |
Type of Okta user. |
Text |
UUID |
Webhook event's universal unique identifier. |
Text |
Event Details |
Raw JSON payload returned from the Okta API for this particular event. |
Object |
Headers |
The object representing the headers for the response. Each key of the header is parsed into a header string as "key: value". For example, Content-Type: text/plain. |
Object |
Source |
An API link to the associated Okta Event Hook. |
Text |
Debug Context |
Object |
|
Debug Data |
Information on the triggered event used for debugging. For example, returned data can include a URI, an SMS provider, or a 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.