Import Group Created
Trigger a flow when an import group is created in Okta.
|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|
|ID||Unique identifier of the Okta admin who created the group.||String|
|Alternate ID||Email address of the Okta admin.||String|
|Display Name||Display name of the Okta admin.||String|
|Type||Role of the Okta admin.|
|ID||Unique identifier of the application associated with the created import group.||String|
|Alternate ID||Alternate ID of the application.||String|
|Display Name||Display name of the application.||String|
|ID||Unique identifier of the created import group.||String|
|Alternate ID||Alternate ID of the created import group.||String|
|Display Name||Display name of the created import group.||String|
|Type||Type of the created group.||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" (
|Source||Source of user-specific data.||Object|
Information on the triggered event used for debugging.
For example, returned data can include a URI, an SMS provider, or transaction ID.
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.