# Actionable notifications

> Actionable notifications in Action Center for completing tasks from Outlook, Slack, and Microsoft Teams without opening Action Center.

Applies to Automation Cloud and Test Cloud only.

Actionable notifications let users complete tasks directly from Outlook, Slack, or Microsoft Teams, without opening UiPath Action Center. They provide a faster and more efficient way for reviewers to respond to tasks generated in Agents, Maestro, or RPA workflows.

Refer to [this forum post](https://forum.uipath.com/t/approve-or-reject-human-tasks-escalations-from-outlook-slack-etc-general-availability/5708430?u=akshay_agnihotri) for a demo video on working with actionable notifications.

## Overview

You can enable actionable notifications across the following UiPath components, using App tasks, created with the **Create App Task** activity:

* **Agents**: via [escalations](https://docs.uipath.com/agents/automation-cloud/latest/user-guide/agent-escalations-and-agent-memory)
* **Maestro**: via [user tasks](https://docs.uipath.com/maestro/automation-cloud/latest/user-guide/user-task)
* **RPA**: via the [Create App Task](https://docs.uipath.com/action-center/automation-cloud/latest/user-guide/create-user-action) activity

When enabled, assignees receive an interactive message in their chosen communication channel (Outlook, Slack, or Teams), allowing them to complete simple tasks inline.

## Enabling actionable notifications in Create App Task activity

To configure actionable notifications for a task, follow these steps:

1. Open the **Properties** panel of the **Create App Task** activity.
2. Select **Show additional options**.
3. Expand the **Actionable Notification** section.
4. Enable the toggle for **Actionable Notification**.
5. Select your preferred channel:
   * Outlook
   * Slack
   * Microsoft Teams
6. Configure the contents of the notification:
   1. Add or modify **Task Fields** as required.
   2. Add **Actionable Buttons** to define outcomes (for example: `Approve`, `Reject`, `Review`).

Figure 1. Enabling actionable notifications

:::tip
Keep the task design simple to ensure consistent rendering across all channels.
:::

## Prerequisites

Before using actionable notifications, complete the following setup steps:

### Notification channels

In the **Manage Notifications** view of the **Notification** settings page, ensure you enable the channels you need (Outlook, Slack, or Microsoft Teams). For more information on customizing notifications, refer to [Managing notifications](https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/managing-notifications).

### **Integration Service setup**

For Slack and Microsoft Teams, you or your administrator must:

1. Set up Integration Service connections for the respective connectors under one of your tenant's folder (for example, under the **Shared** folder):
   * [Microsoft Teams connector](https://docs.uipath.com/integration-service/automation-cloud/latest/user-guide/uipath-microsoft-teams)
     :::important
     For the Microsoft Teams connector, consider taking these additional steps:
       * To receive notifications, set **Include Bot** to **Yes** when creating the connection.
       * Ensure your Teams admin has already added the `UiPath Notifications` app to your Microsoft Teams workspace.
       :::
   * [Slack connector](https://docs.uipath.com/integration-service/automation-cloud/latest/user-guide/uipath-salesforce-slack)
2. Ensure these connections are active and shared across the organization.

### Microsoft Entra admin consent for Outlook

Actionable notifications in Outlook use Microsoft Entra ID–based token authentication for Actionable Messages. Before assignees in your organization can receive and complete actionable notifications in Outlook, a Microsoft 365 tenant administrator must grant admin consent to the UiPath Microsoft Entra application.

This is a one-time, tenant-wide setup step. It applies only to the Outlook channel; Slack and Microsoft Teams use Integration Service connections instead, as described above.

Granting this consent requires Microsoft 365 tenant administrator privileges, which are typically owned by your IT organization. If you are a UiPath administrator without these privileges, contact the IT organization that owns your Microsoft 365 subscription to grant the required consent.

:::warning
Grant this consent by August 26, 2026. Until a tenant administrator grants admin consent, assignees in your organization cannot receive or complete actionable notifications in Outlook.
:::

#### Grant admin consent

To grant admin consent, a Microsoft 365 tenant administrator must:

1. Go to the [Actionable Email Developer Dashboard](https://aka.ms/ActionableMessagesPortal) and sign in with an account that has administrator privileges.
2. Select the **AAD Consent** button in the left-side panel to open the Admin Consent Dashboard, which lists the third-party providers registered for your organization.
3. Use the search bar to find the UiPath provider by **Name**, **Provider ID**, or **Microsoft Entra ID**.
4. Select **Grant Consent** next to the UiPath provider to start the consent flow.
5. Sign in when prompted.
6. Review the requested permissions.
7. Ensure **Consent on behalf of your organization** is selected, so that consent applies tenant-wide and individual users are not prompted again.
8. Select **Accept** to grant consent.

When the flow completes, the provider status changes to **Consented**, and actionable notifications sent to Outlook work for all users in the tenant.

:::tip
If the status remains **Consenting**, select **Refresh Consent Status** to update it.
:::

For the full Microsoft reference on this process, see [Get approval from admins](https://learn.microsoft.com/en-us/outlook/actionable-messages/enable-entra-token-for-actionable-messages#get-approval-from-admins) in the Microsoft documentation.

#### Revoke admin consent

To revoke consent later, a Microsoft 365 tenant administrator must:

1. Open the Azure portal.
2. Go to **Enterprise Applications**.
3. Search for the UiPath app's service principal.
4. Delete it from its **Properties** page.

### Personal notification settings

In the Notifications settings page, under **My Notifications**, enable the **Action Assigned** event to receive task alerts. 
   :::important
   Make sure the email address linked to your UiPath account matches the one used in Slack or Teams to receive notifications correctly.
   :::

### **Action App Requirements**

Actionable notifications work only with Action App tasks and support primitive data types. Complex types are not yet supported. Action App tasks support the following field types:

* Number
* String
* Date
* Boolean

If the Action App includes complex fields, users will still receive a message containing a link to the Action Center task instead of an inline actionable form. If the Action app includes primitive data types only, then users will be able to interact with the field properties of the Action app specified in the Action schema, as in the following table:

Table 1. User interaction with Action App property types

| Property Type | Behavior in Notification | Description |
| --- | --- | --- |
| **Input** | Read-only | Displays pre-filled values, and it is not editable. |
| **Input/Output** | Editable | Populated by automation. Reviewer can update. |
| **Output** | Blank | Must be filled by the reviewer. |
| **Outcomes** | Buttons | Represent the available task actions (for example: Approve, Reject) |

Figure 2. Configuring action schema

  

:::note
When changing an Action App schema, always recheck field bindings in the associated **Agent escalation**, **User task**, or **Create App Task** activity to ensure data is passed correctly to the actionable notification.
:::

## Viewing and completing actionable notifications

After completing all prerequisites and publishing or running the automation, follow these steps:

1. The task assignee receives an actionable message in their selected channel: Outlook, Slack, or Teams.
2. The message includes the form fields and action buttons defined in the Action schema of the Action app.
3. The reviewer can complete the task directly from the message. For additional context, use the link in the message to open the full task in Action Center.
   :::note
   The Slack or Teams user account must use the same email address as their UiPath account to receive the notification.
   :::

### Known limitations

The known limitations of actionable notifications are the following:

* Actionable notifications are available only for App tasks, created using the **Create App Task** activity.
* The supported field types in actionable notifications are: Number, String, Date, Boolean.
* Attachments are not supported in actionable notifications.
* Each field in an actionable notification has a 14,000 character limit.
* You can include a maximum of 10 task fields in the Action schema of the Action app used for sending the actionable notification. If the Action App contains more than 10 fields, the notification only displays a link to the Action Center task.

### Example use case

Check the following use case as an example for actionable notifications sent via Outlook:

1. An RPA workflow creates an Action App task for an approval request.
2. The Action App Action schema contains two fields:
   * Boolean for the **Approve** or **Reject** outcomes.
   * String for a **Comment** option.
3. The reviewer receives an actionable email containing the two fields and outcome buttons: Approve or Reject, and Comment.
4. The reviewer completes the task directly in Outlook.
5. The automation proceeds automatically based on the reviewer’s input.

### Troubleshooting

Check the following troubleshooting steps to know how to solve issues when using actionable notifications:

* If you do not receive a notification:
  1. Verify that your channels are enabled in **Manage Notifications**.
  2. Confirm that **Action Assigned** is enabled under **My Notifications**.
  3. Check that **Slack/Teams Integration Service** connections are active and shared.
  4. Ensure the same email is used in UiPath, Slack, and Teams.
  5. For Outlook, confirm that a tenant administrator has granted [Microsoft Entra admin consent](#microsoft-entra-admin-consent-for-outlook) to the UiPath Microsoft Entra application.
* If fields do not display in the actionable notification sent to the reviewer:
  1. Ensure the Action App contains only primitive fields.
  2. Limit the number of fields to 10 or fewer.
  3. Recheck bindings after modifying the Action App schema.
* If the reviewer cannot edit the fields in the actionable notification: Confirm that the field type is set to **Input/Output** or **Output** in the Action schema, as only these field types are editable, and **Input** is read-only.