maestro
latest
false
- Introduction
- Getting started
- Process modeling with BPMN
- Process modeling with Case Management
- Designing a persistent case entity schema
- 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)
- Managing live case instances: pause, migrate, and retry
- Maestro case management component dictionary
- Process modeling with Flow
- Getting started
- Core concepts
- Node reference
- Build guides
- Best practices
- Reference
- Process implementation
- Debugging
- Simulating
- Publishing and upgrading agentic processes
- Common implementation scenarios
- Extracting and validating documents
- Process operations
- Process monitoring
- Process optimization
- Reference information
Maestro user guide
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.