activities
latest
false
UiPath logo, featuring letters U and I in white

Workflow Activities

Last updated Jul 10, 2025

Create App Task

UiPath.Persistence.Activities.UserAction.CreateUserAction

Description

Creates an App task in Action Center. Action properties are created by adding an Action control within the App, which defines input fields, while Apps provides the visual interface for rendering the task in Action Center.

Note:

App tasks are available in Studio version 2022.10 or higher.

Project compatibility

Windows | Cross-platform

Windows configuration

Designer panel
  • Title - The title of the action you want to create. This field supports strings and String variables only.
  • Priority - Input the priority level of the action as an argument of type UiPath.Persistence.Activities.Model.Task.TaskPriority. Set the Default value parameter of the argument using the TaskPriority Enum value. The following options are available: TaskPriority.Low, TaskPriority.Medium, TaskPriority.High, TaskPriority.Critical.
  • Apps - Choose the Action app you have created and deployed within the Apps instance of your organization and tenant, while using Studio.

    Once you choose an Action app, the action properties will become accessible as properties in the activity. Create variables and input variables for each field accordingly.

    If you update the Action App, then a Refresh property, next to the Action Definition Name field is displayed, that you can use to update the activity with the latest changes.

    Note: The Apps dropdown only displays apps that are deployed and have actions.
  • Orchestrator Folder Path - The path to the Orchestrator folder where you want to create the task, and where you deployed the corresponding app. The folder path must be the same as the path where the previously selected app was deployed to. This field is automatically populated when you select an option from the Apps dropdown list, matching the folder where the selected app is deployed. Once populated, the field becomes read-only and cannot be changed.
Properties panel

Input

  • TaskCatalog - An optional business classification of task items. This field supports only strings and String variables.
    Important: Make sure the action catalog exists prior to the action creation. Otherwise, action creation fails with the following error message: "No task catalog exists with name [action_catalog_name] Error code: 2451."
  • Labels - The robot adds the inputted labels to the action, allowing future filtering. This field supports string values only, and has naming restrictions.
    Note: To allow automatic actions labeling through Persistence activities, the robot account executing the workflow needs View, Create, and Delete permissions on Tags.

Misc

  • TimeoutMS - Specifies the amount of time (in milliseconds) to wait for the activity to run before an error is thrown. The default value is 30000 milliseconds (30 seconds).

Output

  • TaskObject(Output) - The task object that is returned from Orchestrator as a UserActionData object after the action is created. This object can be passed to the Wait For App Task And Resume activity in order to suspend the execution of the workflow until the action is completed.

Actionable notification

Note: Currently, Outlook is the only notification channel that supports actionable notifications.
Prerequisites: For actionable notifications to work as expected, you need to:
  • Enable a Microsoft Outlook 365 connection in the Integration Service within the tenant your Studio automation is linked to.
  • Verify that the user assigned to the actionable notification is subscribed to the Action assigned notification event.

If you want the task assignee to receive an actionable notification instead of a regular email, enable Actionable notification from the activity properties panel.

To enable actionable notifications, follow these steps:
  1. In the activity Properties panel, select Show additional options.
  2. Expand Actionable notification and enable the option via the toggle button.
  3. Select the desired channel for Actionable notifications.
  4. Configure the notification contents by adding new Task fields or Actionable buttons if necessary.


Cross-platform configuration

Designer panel
  • Title - The title of the action you want to create. This field supports strings and String variables only.
  • Priority - Input the priority level of the action as an argument of type UiPath.Persistence.Activities.Model.Task.TaskPriority. Set the Default value parameter of the argument using the TaskPriority Enum value. The following options are available: TaskPriority.Low, TaskPriority.Medium, TaskPriority.High, TaskPriority.Critical.
  • Apps - Select an Action app you have created and deployed within the Apps instance of your organization and tenant, while using Studio. Once you choose an Action app, the action properties will become accessible as properties in the activity. Create variables and input values for each field accordingly.

    If you update the Action App, then a Refresh property, next to the Action Definition Name field is displayed, that you can use to update the activity with the latest changes.

    • If your activity is part of a solution in Studio Web, select + Resource to access an automatically generated Action app. Here, you can establish an Action schema and configure the app.
    Note: The Apps dropdown list only displays apps that are deployed and have actions. However, for workflows that are part of a solution within Studio Web, the Apps dropdown list also displays local action apps from that solution, even if they haven't been deployed yet.
  • Orchestrator Folder Path - The path to the Orchestrator folder where you want to create the task, and where you deployed the corresponding app. The folder path must be the same as the path where the previously selected app was deployed to. This field is automatically populated when you select an option from the Apps dropdown list, matching the folder where the selected app is deployed. Once populated, the field becomes read-only and cannot be changed.
Properties panel

Input

  • TaskCatalog - An optional business classification of task items. This field supports only strings and String variables.
    Important: Make sure the action catalog exists prior to the action creation. Otherwise, action creation fails with the following error message: "No task catalog exists with name [action_catalog_name] Error code: 2451."
  • Labels - The robot adds the inputted labels to the action, allowing future filtering. This field supports string values only, and has naming restrictions.
    Note: To allow automatic actions labeling through Persistence activities, the robot account executing the workflow needs View, Create, and Delete permissions on Tags.

Misc

  • TimeoutMS - Specifies the amount of time (in milliseconds) to wait for the activity to run before an error is thrown. The default value is 30000 milliseconds (30 seconds).

Output

  • TaskObject(Output) - The task object that is returned from Orchestrator as a UserActionData object after the action is created. This object can be passed to the Wait For App Task And Resume activity in order to suspend the execution of the workflow until the action is completed.

Actionable notification

Note: Currently, Outlook is the only notification channel that supports actionable notifications.
Prerequisites: For actionable notifications to work as expected, you need to:
  • Enable a Microsoft Outlook 365 connection in the Integration Service within the tenant your Studio automation is linked to.
  • Verify that the user assigned to the actionable notification is subscribed to the Action assigned notification event.

If you want the task assignee to receive an actionable notification instead of a regular email, enable Actionable notification from the activity properties panel.

To enable actionable notifications, follow these steps:
  1. In the activity Properties panel, select Show additional options.
  2. Expand Actionable notification and enable the option via the toggle button.
  3. Select the desired channel for Actionable notifications.
  4. Configure the notification contents by adding new Task fields or Actionable buttons if necessary.


Was this page helpful?

Get The Help You Need
Learning RPA - Automation Courses
UiPath Community Forum
Uipath Logo White
Trust and Security
© 2005-2025 UiPath. All rights reserved.