- Cloud Action Center のリリース ノート
- 基本情報
- アクティビティ
- 長期実行ワークフローを設計する
- ジョブを開始し参照を取得 (Start Job And Get Reference)
- ジョブ完了まで待機し再開
- キュー アイテムを追加し参照を取得 (Add Queue Item And Get Reference)
- キュー アイテム完了まで待機し再開
- フォーム タスク完了まで待機し再開
- 時間差で再開 (Resume After Delay)
- タスクを割り当て
- 外部タスクを作成
- 外部タスクの完了を待機して再開
- タスクを完了する
- タスクを転送 (Forward Task)
- フォーム タスクを取得 (Get Form Tasks)
- タスク データを取得 (Get Task Data)
- アプリ タスクを取得
- タスクのコメントを追加
- タスクのラベルを更新
- アプリ タスクを作成
- アプリ タスク完了まで待機し再開
- タスク タイマーを設定
- アクション
- プロセス
- 通知
- 自分への通知
- アクション可能な通知
- 監査

Action Center
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.
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.
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:
- Add or modify Task Fields as required.
- Add Actionable Buttons to define outcomes (for example:
Approve,Reject,Review).
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):
- Ensure these connections are active and shared across the organization.
Personal notification settings
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
-
文字列
-
日付
-
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:
| プロパティの種類 | Behavior in Notification | 説明 |
|---|---|---|
| 入力 | Read-only | Displays pre-filled values, and it is not editable. |
| 入力/出力 | 編集可能 | Populated by automation. Reviewer can update. |
| 出力 | 空白 | Must be filled by the reviewer. |
| Outcomes | ボタン | Represent the available task actions (for example: Approve, Reject) |
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.
既知の制限事項
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.
ユース ケースの例
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.
トラブルシューティング
Check the following troubleshooting steps to know how to solve issues when using actionable notifications:
- If you do not receive a notification:
-
Verify that your channels are enabled in Manage Notifications.
-
Confirm that Action Assigned is enabled under My Notifications.
-
Check that Slack/Teams Integration Service connections are active and shared.
-
Ensure the same email is used in UiPath, Slack, and Teams.
-
- If fields do not display in the actionable notification sent to the reviewer:
-
Ensure the Action App contains only primitive fields.
-
Limit the number of fields to 10 or fewer.
-
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.