Device Added to User
Trigger a flow when a device is added to a user in Okta Verify.
This operation uses the device.user.add Okta event.
This event card replaces the identical card found in the Okta connector. There's no change in the card name or functionality.
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. |
Date & Time |
|
Version |
Versioning indicator. |
Text |
|
Actor |
Object |
|
|
ID |
ID of the Okta actor who changed 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 |
|
Device |
Object |
|
|
ID |
ID of the device where the Okta user is added. |
Text |
|
Alternate ID |
Alternate ID of the device where the Okta user is added. |
Text |
|
Display Name |
Display name of the device where the Okta user is added. |
Text |
|
Type |
Type of the device where the Okta user is added. |
Text |
|
Detail |
Details of the device where the Okta user is added. |
Object |
|
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. |
Text |
|
Debug Context |
Object |
|
|
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 |