Phone Verification SMS Sent

Trigger a flow when a user logs in and a verification message is sent in Okta.

This event card is being deprecated from the Okta connector. Replace this event card with the identical card found in the Okta Devices connector. There's no change in the card name or functionality.

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 API.

Text

Message Message details about the event.

Text

Event ID Event's unique identifier key.

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

Actor
ID Unique identifier of the Okta actor who triggered the phone verification message.

Text

Alternate ID Email address of the Okta actor.

Text

Display Name Display name of the Okta actor.

Text

Type Type of Okta actor.

Text

Okta User
ID Unique identifier of the Okta user receiving the phone verification message.

Text

Alternate ID Email address of the Okta user.

Text

Display Name Display name of the Okta user.

Text

Type Type of Okta user.

Text

Phone
ID Unique identifier of the device receiving the verification message

Text

Alternate ID Alternate ID of the device receiving the verification message.

Text

Display Name Display name of the device receiving the verification message.

Text

Type Type of device receiving the verification message.

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 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 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.

Related topics

Okta connector

Workflow elements

Guidance for Okta connector

Okta API documentation