Phone Verification SMS Sent
Trigger a flow when a user logs in and a verification message is sent 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 | Event's unique identifier key. | 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 |
| Actor | ||
| ID | Unique identifier of the Okta actor who triggered the phone verification message. | String |
| Alternate ID | Email address of the Okta actor. | String |
| Display Name | Display name of the Okta actor. | String |
| Type | Type of Okta actor. | String |
| Okta User | ||
| ID | Unique identifier of the Okta user receiving the phone verification message. | String |
| Alternate ID | Email address of the Okta user. | String |
| Display Name | Display name of the Okta user. | String |
| Type | Type of Okta user. | String |
| Phone | ||
| ID | Unique identifier of the device receiving the verification message | String |
| Alternate ID | Alternate ID of the device receiving the verification message. | String |
| Display Name | Display name of the device receiving the verification message. | String |
| Type | Type of device receiving the verification message. | String |
| UUID | Webhook event's universal unique identifier. | String |
| Event Details | Raw JSON payload returned from the Okta API for this particular event. | Object |
| 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). |
Object |
| Source | Source of user-specific data. | Object |
| 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 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.