The Call Workflow node runs another workflow in the same workspace, then optionally continues with that workflow’s output. Use it to reuse shared automations (notifications, enrichment, sync jobs) without duplicating canvas logic.
Paid feature: Call Workflow is available on Pro, Business, and Enterprise plans. Free workspaces see an upgrade prompt when adding or configuring this node.
Configuration
| Field | Description |
|---|---|
| Target workflow | Another workflow in the same organization |
| Inputs (JSON) | Object passed as the child workflow’s inputs. String values support {{templates}} |
| Wait for completion | When on (default), this step waits and returns the child result |
| Timeout (ms) | Max wait when waiting for completion (default 60000) |
| On child failure | Fail this step, or continue with an error payload |
Example
Parent workflow receives a lead, then calls a shared “Notify Slack + CRM” workflow:
Target: Notify Slack + CRM
Inputs:
{
"email": "{{inputs.email}}",
"name": "{{lastOutput.fullName}}"
}
Wait for completion: on
Downstream nodes can read the child result from {{lastOutput.output}} (and also executionId, status, error).
Nesting rules
- Maximum nesting depth: 5 linked workflows.
- Circular chains (A → B → A) are rejected at runtime.
- The child must belong to the same organization.
- Child executions store a
_linkedFromreference to the parent execution for debugging.
When to use Call Workflow vs Action/HTTP
| Goal | Prefer |
|---|---|
| Reuse a TogoFlow automation you already built | Call Workflow |
| Call an external SaaS API | Action or HTTP Request |
| Keep orchestration readable across teams | Call Workflow with wait on |
Related
- Workflow Editor — canvas shortcuts and toolbar
- Variables & Templates
- Execution
- Node Reference — Call Workflow sits under Tools with Action and HTTP