- Introduction
- Getting started
- Build on any canvas
- Build with Case
- Reference
- Defining case keys (system vs. external)
- Establishing task I/O and write-back contracts
- 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)
- Build with Flow
- Build with BPMN
- Operating
- Monitoring
- Optimizing
- Reference information
Maestro BPMN
Business Process Model and Notation (BPMN) process node for reusing a deployed process or automation as a step in a workflow, with its configuration fields and output variables.
Invokes a Business Process Model and Notation (BPMN) process that is already deployed in your organization, such as an agent or agentic automation built elsewhere, and returns its result. Use this node to reuse a deployed process as a step in your workflow, rather than authoring an agent inline with the Autonomous Agent node.
Before you start: deploy a process
The BPMN process node has no process of its own. It lists the BPMN processes deployed in your organization, so one must be deployed before it appears under the node.
- The Add node panel lists deployed processes under BPMN process, each as its own node.
- If nothing is deployed, the category appears but is empty.
How it works
Deployed processes are loaded from your organization, the same way connector nodes and Extract models are. Adding one to the canvas creates a node bound to that specific process. When it runs, Maestro Orchestrate invokes the process, waits for it to complete, and returns its result before continuing.
Configuration
| Field | Required | Description |
|---|---|---|
| Process | Yes | The deployed BPMN process to invoke. Chosen when you add the node from the Add node panel. |
| Input | No | Values mapped to the process's input schema, bound to workflow data with expressions such as $vars.start.output.request. |
Output variables
| Variable | Description |
|---|---|
output | The process's result, structured according to its output schema. Access fields with $vars.<node>.output.<field>. |
error | Populated if the node fails. Error handling describes the error shape. |
Choosing between an Autonomous Agent and a BPMN process
| Use… | When you want to… |
|---|---|
| Autonomous Agent | Author the agent inline on the canvas: set its model, prompts, tools, and context here. |
| BPMN process | Reuse an agent or agentic automation that is already deployed in your organization. |
Notes
- To test without invoking the real process, use Mock output on the node and supply a sample result.
- The BPMN process node supports an error handle. Connect it to route failures instead of stopping the workflow.
- The list of processes reflects what is deployed in your organization at design time. Deploy the process, then reopen the Add node panel to see it.
Next steps
- Autonomous Agent: author an agent inline instead of reusing a deployed one.
- Error handling: route failures from the node.
- Output mocking: test without invoking the real process.