UiPath Delegate acts on your behalf, completing real work end to end across the applications, files, and business systems your teams already use, with governance built in.
An event comes in, agents reason, APIs act, and the workflow finishes within minutes or hours. Build it with your coding agent, in your editor, or on a governed platform, and run it on the Maestro engine.
The AI agent is built on the canvas, the API call is wired on the canvas, the document step and the human step are added on the canvas. No separate tools to configure, nothing to stitch together, and the UiPath Platform™ underneath.
Stay in your editor. Describe the outcome and Claude Code, Codex, Cursor, or Copilot writes the workflow. Debug it like code, with probes, breakpoints, mocks, and a trace of every step and variable.
One way to build. Agents, APIs, documents, data, and human steps are configured, debugged and governed the same way, in a model anyone can read. Evaluate any scenario before it goes live—whole workflow or single node.
Start in Maestro Automate. When a workflow starts carrying the business, convert it to Maestro Orchestrate. Same canvas, same file, nothing to rebuild. The Maestro engine runs underneath either way.
UIPATH MAESTRO
Maestro Automate and Maestro Orchestrate are two products on the same engine: durable, stateful execution built for the enterprise. Automate is for short-running workflows of AI agents and APIs. Orchestrate is for long-running business processes that need durable execution and state management at scale. A customer runs both in one account, and a workflow that outgrows Automate converts to Orchestrate without a rebuild.
Maestro Automate connects agents, APIs and, where the workflow needs them, documents, data, and human steps into one workflow. Every instance runs on the Maestro engine, which keeps a trace of every step and variable and can be retried or cancelled.
Describe the workflow to Claude Code, Codex, or Copilot in VS Code, or a fork such as Cursor. The canvas renders what was generated so you can check and correct it. Studio Web and Studio Desktop are there when you want them.
Probes, breakpoints, and mocks while you build. A trace of every step and variable for every instance once it runs. Retry or cancel any instance, individually or in bulk.
Agents do not behave the same way twice. Whole-workflow or single-node evaluations with mocks, simulations, and LLM-as-judge prove the workflow behaves before it goes live. Free to run.
UiPath agents built inline, third-party agents over A2A and MCP, any system over connectors or raw HTTP, and your existing robots, API workflows and agents called as nodes, not rebuilt.
Policy, access control and an audit trail are inherited from the platform. Guardrails such as PII and prompt-injection screening are available on any agent step. You decide where to apply them.
Short-running workflows where AI agents and APIs do the work together: an event comes in, an agent reasons over live data pulled through APIs, and APIs carry out what the agent decides—done within the hour.
ORDER INTAKE AND ENRICHMENT
An order or lead arrives by webhook. An agent validates it, checks stock and credit over API, and creates the order in the ERP or CRM.
CLAIM TRIAGE
A first notice of loss arrives. An agent classifies severity and coverage against the policy API and routes it to the right adjuster queue.
SERVICE DESK FULFILLMENT
An agent reads the request, pulls the user’s context from identity, ITSM and HR systems over API, decides, and resets, grants or opens the ticket.
INVOICE INTAKE
A document arrives. Extraction and an agent’s judgment validate it against the purchase order over API and post it. Exceptions hand off to Maestro Orchestrate.
TRANSACTION RECONCILIATION
APIs pull the two sides of a transaction. An agent explains the mismatch and proposes the fix. APIs apply it or raise a case.
SCREENING CHECK
A new-customer webhook fires. An agent runs sanctions and adverse-media lookups over API, scores the result and writes it back. Hits hand off to Maestro Orchestrate.
MAESTRO AUTOMATE
An event comes in, agents reason, APIs act, and the instance finishes within minutes or hours. Retry, cancel and a trace of every step are what the work needs. Adopted by the builder, for speed and a canvas they want to use.
MAESTRO ORCHESTRATE
Long-running business processes that need durable execution and state management at scale: multi-day waits on humans or events, full live-instance control, complete process history. Build on the canvas that fits the team: BPMN, Case, or Flow. A workflow that started in Maestro Automate converts to Orchestrate on the same canvas and file.
More to build with, alongside Maestro Automate.
Orchestrate long-running business processes that need durable execution and state management at scale, on the BPMN, Case, or Flow canvas.
Connectors to the systems your workflows call, with authentication and events handled for you.
Build and govern enterprise AI agents on the UiPath Platform.
With Automation Cloud™, you get the full UiPath Platform™, the fastest updates—and the scalability and flexibility to automate any process, anywhere you do business.
Start here
Run the platform yourself, with the world-class automation capabilities you expect and the performance, compliance, and security you require.
Start hereScope, limits, governance, and when a workflow belongs in Maestro Orchestrate instead.
Maestro Automate is for short-running workflows of AI agents and APIs: an instance finishes within minutes or hours, can be retried or canceled, and keeps a trace of every step. Maestro Orchestrate is for long-running business processes that need durable execution and state management at scale: no cap on duration or concurrency, full live-instance control (pause, resume, migrate, go-to), complete process history and SLA monitoring. Both run on the same Maestro engine. Automate uses one canvas; Orchestrate offers three—BPMN, Case and Flow.
Yes. You choose the project type—Maestro Automate or Maestro Orchestrate—when you create the project, and one tenant runs both side by side. Each can call the other: an Automate workflow can hand an exception to an Orchestrate process, and an Orchestrate process can call an Automate workflow as a step.
Yes, by design. Instances are expected to complete within a bounded window, a tenant runs a bounded number of instances concurrently, and traces and logs are retained for a limited period. Run control is retry and cancel. Duration and concurrency are fair-use thresholds—monitored, not enforced by failing an instance—so design against them. A workflow that regularly exceeds them, or needs pause, resume, migration or process history, belongs in Maestro Orchestrate.
In VS Code or a fork such as Cursor, with the Maestro extension and your coding agent—the recommended path. Studio Web needs no install, and Studio Desktop suits teams already building robots there. Create the project as Maestro Automate; the same canvas and file work across all three surfaces.
Platform governance applies from the first run: governance policy, AI Trust Layer model governance, role-based access control, maker-checker publishing approvals and release governance. Guardrails such as PII and prompt-injection screening are available on any agent step. Every instance keeps a trace of every step and variable for a limited retention period. Runtime governance beyond that—AI output watermarking and provenance, tamper-evident audit logs retained for the life of the process, instance data via the Maestro API—is a Maestro Orchestrate capability.
Convert the project to Maestro Orchestrate. It is the same canvas and the same file, so nothing is rebuilt—the workflow gains unbounded duration and concurrency, full live-instance control and complete process history. Coding agents can help with the conversion; there is no dedicated migration tooling.
Yes. Maestro Automate is generally available on Automation Cloud, for Community and Paid plans. Automation Suite availability is to be confirmed. Start on a free trial, or contact us to talk through your estate.
