SoftTech AI Registry
UiPath · Maestro

Agent Orchestration in Maestro Processes

AI agents invoked inside UiPath Maestro processes: a process step starts an agent, the agent returns structured output, and that output is mapped to process variables used to route subsequent process execution such as RPA workflows, API workflows, connector activities or human approval tasks.

Recorded characteristics

Function
UiPath documents agents in Maestro as Service Tasks in BPMN processes: when the process reaches the Service Task, Maestro invokes the agent with input parameters for that process instance, the agent returns output data, and that output is used to determine the next steps in the workflow. Service Task implementation types include "Start and wait for agent" (deployed UiPath agent) and "Start and wait for external agent" (agent hosted outside UiPath, with CrewAI, Salesforce and ServiceNow given as examples). The same process model can also start and wait for RPA workflows and API workflows, execute connector activities, create queue items, evaluate business rules and create Action Center tasks. In the Maestro Flow canvas, an inline Autonomous Agent node is configured with a model, system prompt, user prompt and declared output variables; its structured output is referenced as $vars.<agent>.output.<field> and consumed by downstream Decision or Switch nodes to select a branch.
Data access
Agent inputs are the process-instance values passed into the agent through Service Task inputs or, in Flow, through prompt expressions referencing upstream process variables. An Autonomous Agent can additionally be connected to a Context resource pointing at a context index in the organisation, with configurable retrieval mode, query, result count, relevance threshold and citations. Built-in tools can analyse supplied files, transform a CSV row by row and summarise documents. Maestro documentation states inputs and outputs are passed by reference and governed by platform services such as Orchestrator, Integration Service and Data Fabric. Agents can be configured to report the tools used, decisions made and trace data for debugging and transparency. UiPath documentation reviewed does not establish any broader standing data access for the orchestration layer itself.
Actions
Can take actions
External actions
Conditional
Human confirmation
Conditional
Permission basis
Mixed
Administrative control
Documented controls include: designing the BPMN process or Flow and choosing each task or node implementation; selecting the agent, external agent, RPA workflow, API workflow, connector activity or business rule a task calls; mapping inputs, outputs and process variables; configuring gateways, decisions and branches; adding human approval through User tasks/Action Center or through an Escalation resource on an Autonomous Agent; agent-level model, system prompt, user prompt, temperature, maximum tokens, maximum iterations (1-100, default 25) and guardrails; publishing the process as a solution version and deploying it to Orchestrator, which requires the Packages - Create permission or an Automation Publisher role; configuring execution identity for child processes through folder isolation or explicit Package Requirements execution settings (runtime type, account including "Run as myself", and machine); upgrading a deployed process to a new published version; and instance management plus monitoring of running instances.
Default state
Disabled
Availability
UiPath lists agents, external agents, Integration Service agent connections, human-in-the-loop, action tasks, API workflows, instance management, debugging/simulating/upgrading/publishing and the monitoring dashboard as available on both Automation Cloud/Test Cloud and Automation Cloud Dedicated/Test Cloud Dedicated. The feature availability page notes that use of external agents is supported only for Google Vertex, Azure Foundry, Databricks and Snowflake, and that access to agents integration and API workflows depends on the cloud offering. Some adjacent items are marked preview, including Start and wait for Function, Execute business rule, Case Manager Agent and building a Maestro Case with a coding agent.
Licensing
UiPath states Maestro requires a combination of platform, user and consumption licences, with entitlements depending on the Unified Pricing or Flex plan, and that the same Maestro licensing applies to Maestro Case, Maestro Flow and Maestro BPMN processes. Work run inside a Maestro instance consumes the native consumables of the task types used. A debug run does not consume Agent Units or Platform Units for process execution, although services the debug run calls consume their own units.
External model or provider
Not established for the orchestration layer itself. Maestro is documented as vendor-neutral orchestration; in the Flow Autonomous Agent node the model is selected per agent from the models available to the organisation, defaulting to the organisation default agent model. No specific model or provider is named for Maestro orchestration in the documentation reviewed.
Limitations and uncertainty
Authority is mediated: the agent returns output, and any persistent operational change is performed by the configured downstream task (RPA workflow, API workflow, connector activity, queue item, message) or by a tool connected to an Autonomous Agent. UiPath documentation reviewed does not establish that the orchestration layer grants agents arbitrary system access. External agents retain their own authority and controls; invoking CrewAI, Salesforce or ServiceNow through Maestro does not transfer those systems' authority to UiPath. Human approval is optional and depends on process design, so unattended end-to-end execution is possible. Identity is documented at the child-job level (Orchestrator account and machine, folder identities, Integration Service connections, Action Center users) rather than as a single documented agent identity, so permission basis is recorded as mixed. Agent Builder authoring, Action Center itself, Autopilot and the Conversational Agent node are treated as separate matters and are not part of this record.

Evidence