Trigger a flow when a user is deactivated in Okta API.
|Date and Time||Date and time the event was triggered in Okta API.||String|
|Message||Message details about the event.||String|
|Event ID||Unique identifier of the event.||String|
|Event Type||Type of event that was published.||String|
|Event Time||Timestamp when the notification was delivered to the service.||String|
|Admin||Okta admin who deactivated the user.||Object|
|ID||ID of the Okta admin who deactivated the user.||String|
|Alternate ID||Email address of the Okta admin.||String|
|Display Name||Display name of the Okta admin.||String|
|Okta User||Okta user who was deactivated.||Object|
|ID||ID of the Okta user who was deactivated.||String|
|Alternate ID||Email address of the Okta user.||String|
|Display Name||Display name of the Okta user.||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|
|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 additional 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 data from such fields isn't returned by this event card.