maestro
latest
false
- Introduction
- Getting started
- Process modeling with BPMN
- Process modeling with Case Management
- Designing a persistent case entity schema
- 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)
- Managing live case instances: pause, migrate, and retry
- Maestro case management component dictionary
- Process modeling with Flow
- Getting started
- Core concepts
- Node reference
- Build guides
- Best practices
- Reference
- Process implementation
- Debugging
- Simulating
- Publishing and upgrading agentic processes
- Common implementation scenarios
- Extracting and validating documents
- Process operations
- Process monitoring
- Process optimization
- Reference information
Maestro user guide
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.