Group Privilege Revoked
Trigger a Flow when a group’s admin privilege is revoked in Okta. The group granted privileges can be an Okta sourced group, and AD-sourced group, or an LDAP-sourced group.
|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||ID of the Okta actor who revoked the group privilege.||String|
|Alternate ID||Email address of the Okta actor.||String|
|Display Name||Display name of the Okta actor.||String|
|Type||Type of data returned.||String|
|ID||ID of the group where the privilege was revoked.||String|
|Alternate ID||Alternate ID of the group where the privilege was revoked.||String|
|Display Name||Display name of the group where the privilege was revoked.||String|
|Type||Type of the group where the privilege was revoked.||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
|Source||Source of user-specific data.||String|
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.