Import Started
Trigger a flow when an import process is started in Okta API.
Scopes
See Event cards for the list of required OAuth scopes needed by this card.
Output
| Field | Definition | Type |
|---|---|---|
|
Date and 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 |
ID of the Okta actor who started the import process. |
Text |
|
Alternate ID |
Email address of the Okta actor. |
Text |
|
Display Name |
Display name of the Okta actor. |
Text |
|
Type |
Type of data returned. | Text |
|
Application |
||
|
ID |
ID of the Okta application. |
Text |
|
Alternate ID |
Email address of the Okta application. |
Text |
|
Display Name |
Display name of the Okta application. |
Text |
|
Type |
Type of Okta application. |
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.