maestro
latest
false
Maestro user guide
- Introduction
- Getting started
- Building with Maestro BPMN
- Understanding Maestro BPMN modeling
- Opening the modeling canvas
- Modeling your process
- Aligning and connecting BPMN elements
- Autopilot for Maestro (Preview)
- Process Repository
- Implementing a simple BPMN process
- Implementing a complex BPMN process
- Debugging
- Simulating
- Evaluations (Preview)
- Common implementation scenarios
- Building with Maestro Case
- Introduction to Maestro Case
- Maestro BPMN vs. Maestro Case: when to use case management
- The Maestro Case lifecycle: from event trigger to app experience
- Build your first case with Maestro Case
- Build a Maestro Case with a coding agent (preview)
- Defining case keys (system vs. external)
- Establishing task I/O and write-back contracts
- Exit rules and early stage termination
- 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)
- Case Manager input and output contract
- Maestro Case component dictionary
- Building with Maestro Flow
- Maestro Automate
- Integrations
- Operating
- Monitoring
- Optimizing
- Reference information
RPA Workflow node for running a UiPath RPA process published in Orchestrator and waiting for it to complete, with its configuration fields and output variables.
Starts a UiPath RPA process published in Orchestrator and waits for it to complete. Use this node to incorporate robot-executed automation into your Flow workflow.
Configuration
| Field | Required | Description |
|---|---|---|
| Process | Yes | The Orchestrator process to start. Select from the list of processes available in your organization. |
| Folder | Yes | The Orchestrator folder that contains the process. |
| Input arguments | No | Key-value pairs passed to the RPA process as input arguments. Must match the process's defined input argument names and types. |
| Timeout | No | Maximum time to wait for the process to complete. |
Output
The node's output mirrors the selected process's own output arguments — the fields and types vary by process. Access them downstream as $vars.<nodeId>.output.<argumentName>.
If the process fails, the node populates an error output instead. Refer to Error handling for the error shape and how to route on it.
Notes
- The RPA Workflow node starts a job in Orchestrator and waits for it to reach a terminal state before continuing. Ensure the timeout is long enough for the process to complete.
- The process must be published in Orchestrator before it can be selected in the node configuration.