Application Deactivated

Trigger a flow when an application is deactivated in Okta.

Scopes

See Event cards for the list of required OAuth scopes needed by this card.

Output

Field	Definition	Type
Date & Time	Date and time the event was triggered in Okta API.	Text
Message	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	Time stamp when the notification was delivered to the service.	Text
Version	Versioning indicator.	Text
Admin	Okta admin who deactivated the application.	Object
ID	ID of the Okta admin who deactivated the application.	Text
Alternate ID	Email address of the Okta admin.	Text
Display Name	Display name of the Okta admin.	Text
Type	Type of data returned.	Text
Okta Application	Okta application that was deactivated.	Object
ID	ID of the Okta application that was deactivated.	Text
Alternate ID	Alternate ID of the Okta application that was deactivated.	Text
Display Name	Display name of the Okta application.	Text
Type	Type of Okta application that was deactivated.	Text
UUID	Webhook event's universal unique identifier.	Text
Event Details	Raw JSON payload returned from the Okta API for this particular event.	Text
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).	Text
Source	Source of user-specific data for the application.	Text
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.	Text

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.

Application Deactivated

Scopes

Output

Related topics