UiPath Documentation
maestro
latest
false

Maestro user guide

Choosing a Maestro modeler

Maestro is UiPath's agentic business orchestration engine. It provides governance, observability, domain logic, and security: an enterprise backbone for durable process execution.

Maestro Business Process Model and Notation (BPMN), Maestro Flow, and Maestro Case Management are modeling experiences that let you build business orchestrations with Maestro. All three integrate tightly with the key components of the UiPath platform, including Agents, Integration Service, RPA, Action Center, and Data Fabric, as well as external agents and workflows. All are built on the same orchestration backbone, and their process instances are surfaced in Maestro Instance Management.

This page helps you decide which modeler to use.

Structured process orchestration: Maestro Business Process Model and Notation (BPMN) and Maestro Flow​

Maestro BPMN and Maestro Flow are process orchestration modelers. They are best suited for business processes that take deterministic steps and branch in predefined ways, even when individual components (such as agents) execute non-deterministically.

The choice between BPMN and Flow is a matter of modeling preference, not process functionality or use case. Both handle complex business orchestration with robust error handling.

BPMN fits when:

  • Your team already speaks BPMN, and BPMN is the common language you use for design and implementation.
  • Your team needs to follow BPMN standards for compliance or governance reasons.
  • You are extending an existing BPMN process.

Flow fits when:

  • You prefer a visual experience aimed at automation developers.
  • You want to develop using coding agents such as Claude or Codex.

Use cases for Maestro BPMN and Maestro Flow​

These are processes where the steps and branches are known at design time, even when individual steps (such as agents) reason non-deterministically:

  • Purchase-to-pay and invoice processing: receive an invoice, extract fields, match it with a purchase order, route exceptions to an approver, and post to an Enterprise Resource Planning (ERP) system. The path is fixed; only the data varies.
  • Straight-through application processing: loan origination, account opening, or claim intake where the happy path and its rejection and referral branches are all defined up front.
  • Multi-agent orchestration: wrap multiple agents in deterministic pre- and post-processing. Gather inputs, call the agent, validate outputs, and take actions in systems based on the results. Flow's built-in agent nodes make this pattern straightforward.
  • Document processing pipelines: extract, validate, enrich, route, and write back, where the pipeline steps can be expressed in advance.

Goal-driven orchestration: Maestro Case Management​

Maestro Case Management is a case management canvas. Where BPMN and Flow lay out a process as a path through predefined steps, Case Plans are a set of stages that a case moves through dynamically, with the route decided at runtime by rules, an orchestrating Case Manager agent, or both.

Case Management is best suited for long-lived, goal-driven work where the next step depends on what just happened and no single flowchart captures every path: claims, investigations, disputes, and approvals that run for days or weeks, involve multiple teams and systems, and treat exceptions as the norm rather than the edge case.

Case Management fits when:

  • The path isn't known at design time: the next step depends on what just happened, and outcomes (approved, rejected, needs more info) reroute the work rather than just advancing it.
  • Exceptions are the norm, not the edge: re-entry, rework loops, and "send it back a stage" are expected behavior, not error paths.
  • Multiple roles and systems across departments touch the same case: case workers, managers, AI agents, RPA, and external systems all contribute to one shared record.
  • Advanced Service Level Agreement (SLA) and escalation management are required: deadlines are tracked at the case, stage, and task level, and a breach must trigger a defined action.

Use cases for Maestro Case Management​

These are processes where the path is determined at runtime, can span days or weeks, and treats exceptions as the norm:

  • Insurance claims: multi-party (claimant, adjuster, inspector), missing-document and dispute exceptions, SLA-driven.
  • Disputes and chargebacks: back-and-forth evidence gathering, escalation paths, non-linear progression.
  • Know Your Customer (KYC) / Anti-Money Laundering (AML) remediation: staged document collection, regulatory decision points, full audit trail.
  • Customer escalation management: tiered resolution, re-entry when a fix doesn't hold, multi-team handoffs.
  • Investigations and referrals: ad-hoc approvals, cross-department coordination, policy-dependent routing.

At a glance​

Maestro BPMNMaestro FlowMaestro Case Management
Project format.bpmn.flowCase plan
Primary userProcess architect, Business Process Management (BPM) practitionerDeveloper, automation builderCase designer, operations lead
StructureBPMN process diagramSequence of nodes with branching and loopsStages containing tasks
Path determinedAt design timeAt design timeAt runtime, by rules, a Case Manager agent, or both
DecisioningGateways, Decision Model and Notation (DMN)Decision and Switch nodesRules (DMN), agent, or hybrid

Can I use more than one?​

Yes. All three modelers run on the same Maestro runtime and deploy to Orchestrator. You can use Flow for developer-built automations, BPMN for structured process modeling, and Case Management for goal-driven case work, all within the same organization. Processes built with any modeler can call each other through Orchestrator.

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated