maestro
latest
false
Maestro Orchestrate user guide
- 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
Connector trigger
Start a workflow when an event happens in a connected app, such as a new email, a new record, or a deleted lead.
A Connector trigger starts a workflow when something happens in another app, for example a new email in Gmail or a deleted lead in Marketo. Each app offers its own list of events. Popular connectors lists common apps, with a link to each connector.
Set it up
- Select the trigger on the canvas, then select Connector trigger in the Change trigger list.
- Choose the app, then the event. The trigger is named after the event, for example Lead Deleted.
- In the Connector section, select a connection to the app, or create one. Connector nodes describes connections.
- Optionally, under Input arguments, add values that other nodes read under
$vars.<node ID>.output.
Output
The trigger's output holds the event's data, such as the email or the record that changed. Select { } Insert in a later node to see the fields.
Next steps
- Connector event: wait for an event partway through a run instead.
- Triggers: the other ways to start a workflow.