- 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
- What is Maestro Automate?
- Capabilities comparison
- Integrations
- Operating
- Monitoring
- Optimizing
- Reference information
Maestro Automate: a lightweight Maestro runtime for short-running workflows of AI agents and APIs, built on the Flow canvas.
Maestro Automate is a lightweight runtime for short-running workflows of AI agents and APIs. Workflows are built on the Flow canvas and run on the same Maestro engine as Maestro Orchestrate, with a runtime envelope and a run price sized for work that finishes within minutes or hours.
You choose Maestro Automate when you create the project and the platform governs it from the first run.
Maestro Automate and Maestro Flow share the same build tools, and you can convert between them. For the full comparison, refer to Choosing between Maestro Orchestrate and Maestro Automate.
Consumption
Maestro Automate meters consumption per run at a reduced rate compared with Maestro Orchestrate, and a monthly allowance of runs is included, depending on your pricing model and platform tier. For the rates and allowances that apply to your organization, refer to Licensing – Unified Pricing or Licensing – Flex Plan.
Building a Maestro Automate workflow
Maestro Automate workflows are built on the Flow canvas, so the Flow documentation applies without change for functional components. The canvas, node set, evaluations, variables, expressions, control flow, error handling, triggers, and publishing behave the same way. You can create a new Maestro Automate project from any surface that you can build with Maestro Flow.
Refer to the following pages for how to build:
- Getting started: what Flow is and how to build a first workflow
- Core concepts: the canvas, data flow, control flow, and triggers
- Node reference: every available node
- Deploying a Flow: publishing a workflow to Orchestrator
Where Maestro Automate differs
Runtime limits, live-instance control, monitoring, and trace retention are where the two products part ways. Refer to Choosing between Maestro Orchestrate and Maestro Automate for the comparison.