Trigger Workflow Block
What it does: Launches another published workflow from inside the current workflow, optionally passing in variables and waiting for it to finish.
In simple terms: Like calling a function in code. Your workflow says "run that other workflow now" and can either wait for the result or continue immediately.
When to Use This
- ✅ Shared sub-workflows — Extract common logic (e.g. "Send onboarding email + Slack alert") into one workflow and call it from many others
- ✅ Modular automation — Break a large workflow into smaller, testable pieces
- ✅ Fan-out — Trigger multiple child workflows in parallel from one parent
- ✅ Conditional sub-flows — Use inside a Switch branch to run specialised workflows per case
How It Works
- Select the target workflow from the dropdown (only published workflows appear)
- Optionally map input variables — values from the current workflow are passed to the target
- Choose whether to wait for completion or fire-and-forget
Configuration
Target Workflow
Select the workflow you want to trigger from the dropdown. Only published workflows are listed — draft workflows cannot be triggered.
The target workflow must be published before it appears in the dropdown. Publish it first from its own editor.
Wait for Completion
| Setting | Behaviour |
|---|---|
| Off (default) | Fire-and-forget — the current workflow continues immediately without waiting |
| On | The current workflow pauses until the triggered workflow finishes, then resumes |
Use On when you need the result of the sub-workflow before continuing. Use Off for background tasks like logging, notifications, or parallel processing.
Input Variables
Pass values from the current workflow into the triggered workflow's variables:
| Field | Description |
|---|---|
| Variable ID | The ID of a variable in the target workflow to populate |
| Value | The value to set — supports {{variable}} references from the current workflow |
You can add as many mappings as needed. Variables not listed keep their default values in the target workflow.
Example: Shared Notification Sub-Workflow
Parent workflow (Order Processing):
[Process Order] → [Trigger Workflow: "Send Notifications"]
Input Variables:
orderId = {{order.id}}
customer = {{customerName}}
amount = {{orderTotal}}
Wait for completion: OffChild workflow ("Send Notifications"):
[WhatsApp message to {{customer}}] → [Slack alert to #orders]The parent triggers the child immediately and continues to the next step without waiting.
Tips
- Only published workflows appear — if you don't see a workflow in the dropdown, check that it's published.
- Avoid circular triggers — don't set up Workflow A to trigger Workflow B which triggers Workflow A. This causes infinite loops.
- Use
Wait for completion: Onsparingly — it holds up the parent workflow and counts against execution time limits. - Input variable IDs must exactly match variable IDs in the target workflow (found in the target workflow's Variables panel).
