Action Center

DELIVERY:

Last updated Nov 20, 2025

Actionable notifications

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.

Overview

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

Agents: via escalations
Maestro: via user tasks
RPA: via the Create App Task 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:

Open the Properties panel of the Create App Task activity.
Select Show additional options.
Expand the Actionable Notification section.
Enable the toggle for Actionable Notification.
Select your preferred channel:
- Outlook
- Slack
- Microsoft Teams
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.

Integration Service setup

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

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
- Slack connector
Ensure these connections are active and shared across the organization.

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:

The task assignee receives an actionable message in their selected channel: Outlook, Slack, or Teams.
The message includes the form fields and action buttons defined in the Action schema of the Action app.
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:

An RPA workflow creates an Action App task for an approval request.
The Action App Action schema contains two fields:
- Boolean for the Approve or Reject outcomes.
- String for a Comment option.
The reviewer receives an actionable email containing the two fields and outcome buttons: Approve or Reject, and Comment.
The reviewer completes the task directly in Outlook.
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.
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.