Phone Verification Call Sent

Trigger a flow when a user signs in and Okta sends a verification phone call.

This operation uses the system.voice.send_phone_verification_call Okta event.

This event card replaces the identical card found in the Okta 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 and Time

The date and time when the event was triggered in the Okta API.

Text

Message

Any 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

Timestamp when the notification was delivered to the service.

Text

Version

Versioning indicator.

Text

Actor

ID

The unique identifier of the Okta actor who triggered the phone verification call.

Text

Alternate ID

Email address of the Okta actor.

Text

Display Name

Display name of the Okta actor.

Text

Type

ID of the Okta actor who changed the user privilege.

Text

Okta User

ID

The unique identifier of the Okta user receiving the phone verification call.

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

The unique identifier of the device receiving the verification call.

Text

Alternate ID

Alternate ID of the device receiving the verification call.

Text

Display Name

Display name of the device receiving the verification call.

Text

Type

Type of device receiving the verification call.

Text

UUID

The universal unique identifier of the webhook event.

Text

Event Details

The raw JSON payload returned from the Okta API for this particular event.

Object

Headers

An object that represents the headers for the response.

Each key of the header is parsed into a header string as a key and value pair, for example, Content-Type: text/plain.

Object

Source

The source of any user-specific data.

Object

Debug Context

Debug Data

Information on the triggered event that you can use 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.

Related topics

Okta Devices connector

Okta Devices API

Device lifecycle

Cards in flows