Node: Call another workflow

The Call another workflow node runs a second (active) workflow from the point where the current flow is at, like a subroutine. It lets you build reusable blocks — for example, a "Send standard reminder" workflow you call from several different flows — instead of duplicating the same node sequence over and over.

When to use it

• When several automations repeat the same steps (e.g. notifying the team, or asking the customer for a piece of data) and you want to maintain them in one place.
• To break a very long flow into smaller, easier-to-maintain modules.

Requirements

• The target workflow must exist and be active; if it's paused or deleted, the node returns an error and the flow continues according to your error handling (e.g. a Try/Catch node).

Configuration

• Target workflow (required): the workflow to invoke.
• Input (optional): a text or value to pass into the called workflow; it becomes available there as the $caller.input variable.

Variables available in the called workflow

• $caller.workflow_id — the ID of the workflow that made the call.
• $caller.execution_id — the ID of the run that triggered the call.
• $caller.input — the value you set in "Input".

Example

You build a workflow "Notify supervisor handoff" with the email alert + internal note steps. Then, in three different flows (one for WhatsApp, one for Webchat, one for Instagram) you add a Call another workflow node pointing to "Notify supervisor handoff". If you change the alert message tomorrow, you only edit it once.

Tips

• Use it to avoid maintaining the same logic copy-pasted across several workflows.
• The called workflow runs with the same context (contact, conversation, variables) as the calling flow, plus the $caller.* variables.

Troubleshooting

• "Workflow not found" or "not active": confirm the target workflow exists and its active toggle is on.
• No input reaches the called workflow: check that the "Input" field has content and that the target workflow reads $caller.input.