maestro
latest
false
Maestro user guide
- 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
- Integrations
- Operating
- Monitoring
- Optimizing
- Reference information
Node that starts a workflow on demand from the Flow interface, API, or another workflow.
Starts the workflow on demand. The workflow runs when explicitly invoked — from the Flow interface, via the Flow API, or by a Subflow node in another workflow.
Configuration
| Field | Required | Description |
|---|---|---|
| Input schema | No | Defines the input variables the workflow accepts when triggered. Each entry specifies a variable name, type, and whether it is required. |
Input variables
Variables defined in the input schema are available to all nodes in the workflow from the start of execution. When the workflow is triggered manually from the interface, the operator can supply values for these variables in the trigger dialog.
When the workflow is triggered via the API or as a subflow, the caller provides values for the input variables in the request payload or Subflow node configuration.
Notes
- A workflow can have a Manual Trigger alongside other trigger types. Each trigger type operates independently.
- For workflows that should run on a time-based schedule, use the Scheduled Trigger instead.
- For workflows that should start in response to an external event, use an integration trigger.