- Introduction
- Getting started
- Build on any canvas
- Build with Case
- Reference
- Defining case keys (system vs. external)
- Establishing task I/O and write-back contracts
- Modeling primary and secondary stages
- Triggering a case from Data Fabric
- Implementing stage-level personas and permissions
- Setting SLAs and automated escalation rules
- Configuring a rework loop (re-entry)
- Configuring and testing the Case Manager Agent (preview)
- Build with Flow
- Build with BPMN
- Operating
- Monitoring
- Optimizing
- Reference information
Tasks
Task building blocks in Maestro Orchestrate for process execution, including BPMN task types and UiPath Platform implementation options.
Tasks provide the building blocks for process execution. UiPath Platform™ capabilities are accessed via standard BPMN task types.
The Implementation configuration defines how each task interacts with external systems or internal logic. Depending on the task type—Service, User, or Send—you can trigger automations, route work to agents, wait for connector events, or send messages to other systems.
The available actions follow a consistent design: select an action, define inputs and outputs, and optionally update process variables.
Available task types
In Maestro Orchestrate, the task type you select determines what the step does at runtime and which UiPath Platform components it calls. Some types run work inside Maestro Orchestrate, others orchestrate Robots, agents, API workflows, queues, or Business Rules.
| Task type | Description | UiPath Platform component(s) involved |
|---|---|---|
| None | No action is triggered. Typically used as a placeholder or when a step does not need to perform any automation. | None |
| Create action app task | Creates a task for a human user in UiPath Action Center for manual input or approval. | Apps (Action Apps only), Action Center |
| Start and wait for RPA workflow | Starts an unattended RPA process (UiPath Robot) and waits for its completion before continuing. | Robots |
| Start and wait for agent | Initiates an AI or software agent registered with UiPath Autopilot/Maestro Orchestrate and waits for the agent’s output before moving on. | Agent Builder |
| Start and wait for external agent | Launches and waits for the result from an externally hosted agent (outside the UiPath ecosystem), often via HTTP or a messaging interface. | External agents via APIs |
| Start and wait for external workflow | Launches and waits for the result from an externally hosted workflow (outside the UiPath ecosystem), often via HTTP or a messaging interface. | External workflows via APIs |
| Start and wait for API workflow | Starts an API-first workflow (built using UiPath Integration Service) and waits for its response. | API Workflows, Integration Service |
| Start agentic process | Starts a process composed of tasks/decisions, built using UiPath Maestro Orchestrate. Does not wait for completion. | Maestro Orchestrate |
| Start and wait for agentic process | Starts a process composed of tasks/decisions, built using UiPath Maestro Orchestrate. Waits for completion before continuing. | Maestro Orchestrate |
| Execute business rule [Preview] | Evaluates business rule logic (defined via UiPath Business Rules / DMN) and returns the outcome. | DMN files |
| Create queue item | Adds a new item to a UiPath Orchestrator queue for background processing or load balancing. | Queues, Robots |
| Create and wait for queue item | Adds a queue item and waits for its processing and completion result before proceeding. | Queues, Robots |
| Bulk add queue items | Adds up to 15,000 items to an Orchestrator queue in a single batch. | Queues, Robots |
| Delete queue items | Removes items with New status from an Orchestrator queue. | Queues, Robots |
| Postpone transaction item | Defers an in-progress transaction item to a later date and returns it to New status. | Queues, Robots |
| Set transaction progress | Updates an in-progress transaction item with a custom status string visible in Orchestrator. | Queues, Robots |
| Set transaction status | Sets the final state of a transaction item to Successful or Failed. | Queues, Robots |
| Execute connector activity | Calls a prebuilt connector activity (for example, Salesforce, SAP, ServiceNow) from UiPath Integration Service. | Integration Service, Data Fabric |
| Wait for connector event | Listens for an event from a connector (for example, a record created in Salesforce) and continues the workflow once the event is triggered. | Integration Service, Data Fabric |
| Execute script | Runs a custom script (for example, JavaScript) to call coded functions. | Maestro Orchestrate |
For required fields and behavior of each queue activity, refer to Queue task activities.
Access to different action tasks depends on the cloud offering you use. For details, refer to Maestro Orchestrate feature availability.
Connector configuration experience
Every BPMN process or Case workflow item that uses an Integration Service connector uses one of two configuration experiences in the properties panel. This includes:
- Connector activities and triggers, including start events and events that wait for a connector event.
- External agents and automations.
- Case tasks, triggers, and rules that use a connector, such as stage entry and exit rules that wait for a connector event.
| Older experience | Newer experience | |
|---|---|---|
| Used by | Existing connector items that show the upgrade message | Every connector item you add, including items added to existing processes and cases |
| Activity selection | Select the Connector, the connection, and then the Activity | Select the activity in Select activity, and then the connection |
Connector items that use the older experience keep their configuration and continue to run unchanged. A process or case can contain items that use both experiences. The properties panel of an older item shows the following message: A newer version of this activity is available. To upgrade, remove it and add it again.
No automatic upgrade is available. To use the newer experience for an existing connector item, remove it, add it again, and configure its inputs again. The item works the same way after you add it again.