User Unassigned from Application

Trigger a flow when a user is unassigned from an app in Okta.

Scopes

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

Options

This event card is triggered when the specified app instance in your Okta org receives a user update.

Field	Definition	Type	Required
Use App Instance ID?	Choose how you want to designate the app instance that registers the change and triggers the flow: Yes: Manually enter the app instance identifier using the App Instance ID field. No: Select the app instance using the Application and Application Instance fields in the dropdown list.	Dropdown	TRUE
Application	Specify the app to monitor for the user change. If you don't want to filter for a specific app, select -- All Apps -- from the dropdown list. If you want to filter for a specific instance of an app in your org, choose the app from the dropdown list. The dropdown displays up to 1000 apps. To specify an app that isn't in the list: Select Yes for the Use App Instance ID? option. Choose -- Enter App Instance ID -- in the Application dropdown menu. Choose -- Enter App Instance ID -- in the Application Instance dropdown menu. Manually enter the app instance identifier in the App Instance ID field.	Dropdown	TRUE
Application Instance	Select an instance of an Application within your Okta org. If you want the event triggered when the user change happens only for a specific instance of an app, choose that app instance from the dropdown list. The dropdown displays up to 2000 app instances. If you want the event triggered when the user change happens for any apps in your org, select -- All App Instances --. However, this option only appears if you select -- All Apps -- for the Application option, as you can't select all instances of a specific application.	Dropdown	TRUE
App Instance ID	Specify an app instance using its unique identifier. This field is necessary if you choose Yes for the Use App Instance ID? option. Follow these steps to find the app instance identifier for an app: In the Admin Console, go to ApplicationsApplications. Click the app to open it. When the app opens, check the page URL in your browser. The app instance ID is found in the URL: https://{yourcompany}.okta.com/admin/app/{yourappname}/instance/{YOURAPPINSTANCEID}/ For example, if the app URL is https://acme.okta.com/admin/app/office365/instance/0oahjhk34aUxGnWcZ0h7/ then the app instance ID is 0oahjhk34aUxGnWcZ0h7.	Text	FALSE

Output

Field	Definition	Type
Date and Time	The date and time when the event was triggered in the Okta API.	Text
Message	Any 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	Timestamp when the notification was delivered to the service.	Text
Version	Versioning indicator.	Text
Admin	Details about the Okta admin who unassigned the user.	Object
ID	The unique identifier of the Okta admin.	Text
Alternate ID	Email address of the Okta admin.	Text
Display Name	Display name of the Okta admin.	Text
Type	The type of the Okta admin.	Text
Okta User	Details about the Okta user who was unassigned from the application.	Object
ID	The unique identifier of the Okta user.	Text
Alternate ID	Email address of the Okta user.	Text
Display Name	Display name of the Okta user.	Text
Type	Type of Okta user.	Text
Application User	User's details in the target app.	Object
ID	User's identifier in the target app.	Text
Alternate ID	User's alternate ID in the target app. This is usually their email address.	Text
Display Name	Display name of the user in the target app.	Text
Type	Type of the user in the target app.	Text
Application	Details of the target app.	Object
ID	Identifier of the target app.	Text
Alternate ID	Alternate ID of the target app.	Text
Display Name	Display name of the target app.	Text
Type	The type of the target app.	Text
UUID	The universal unique identifier of the webhook event.	Text
Event Details	The raw JSON payload returned from the Okta API for this particular event.	Object
Headers	An object that represents the headers for the response. Each key of the header is parsed into a header string as a key and value pair, for example, Content-Type: text/plain.	Object
Source	The source of any user-specific data.	Object
Debug Context
Debug Data	Information on the triggered event that you can use for debugging. For example, returned data can include a URI, an SMS provider, or a 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.

User Unassigned from Application

Scopes

Options

Output

Related topics