In this guide:

1. Okta Workflows guides
2. Specific app unassignment notification
3. Any app unassignment notification
4. Related Okta Workflows guides
5. Okta Workflows resource

Okta Workflows guides

Okta Workflows guides offer questions and answers from the Okta Workflows community office hours. They also come from the #okta-workflows channel on the Mac Admins Slack and other places. Read all the other guides.

How do you send an email notification using Okta Workflows when a user is unassigned from an app?

This guide will teach you how to send an email notification using Okta Workflows when a user is unassigned from an app.

Specific app unassignment notification

This flow will run when a user is unassigned from an application:

How the flow works

1. The flow runs when a user is unassigned from an application (the Okta-Unassigned from Application event card).
   • In the card options, you must configure the application for which this flow will run. This example uses the Salesforce app.
     
2. The Text-Compose card generates a message that includes user information and application details.
3. The Gmail-Send Email card sends the notification email.
   • You can also use the Slack connector to send a message to Slack.

Any app unassignment notification

There are two approaches to running a flow without configuring for a specific app:

1. Use the Okta-User Unassigned from Application event card without configuring a specific application.
2. Use an Okta event hook

Use Okta-User Unassigned from Application event card

Use the Okta-User Unassigned from Application event card, specifying All Apps instead of a specific app in the card’s Options.

A flow with this event card set up will run when a user is unassigned from any app.

The Application object holds the information about the application.

Use an Okta event hook

To run a flow when a user is unassigned from any application, set up a flow with an API Endpoint and create an Okta event hook.

The event hook that triggers the flow:

How the flow works

1. The API Endpoint card gives the flow an API endpoint. When a user is unassigned from an app, the event hooks call the API, which runs the flow.
2. The Object-Get Multiple card extracts user and application information from the API endpoint.
3. The Text-Compose card generates a message that includes user information and application details.
4. The Gmail-Send Email card sends the notification email.

What is the difference between using the event card and the event hook?

Let’s say you want to be notified when a user is unassigned from three specific apps. Using the Okta-User Unassigned from Application event card configured for all apps, you will need to add logic to check for those apps. This means the flow will run for any app unassignment and then check the logic to determine whether to continue running.

An Okta event hook allows you to configure a filter on the event hook side. This means the flow will only run when the filter matches the app you are interested in. Using an event hook is usually more granular and less noisy.

The following resources will help you learn about Okta event hooks:

• Understanding Okta Workflows Events.
• Okta Workflows Tutorial: Notify When a User is Added to a Group (with Event Hook filtering).

Related Okta Workflows guides

• Okta Workflows Tutorial: Send an Email Notification for a New Okta Event.
• Understanding Okta Workflows Events.
• Okta Workflows Tutorial: Notify When a User is Added to a Group (with Event Hook filtering).

Okta Workflows resource

🚀 New to Okta Workflows? The Getting Started with Okta Workflows page has all the resources to help you get started.

📺 Like learning from videos? Watch Okta Workflows videos.

❓Have a question? Ask during community office hours, post on the community forum, or email me.

🙋🏻‍♀️ Want to learn from the community? Join the #okta-workflows channel on the Mac Admins Slack.

📖 Want to learn more about Okta and automation? Take the Okta Workflows training on Okta Learning.