Node: Call another workflow
How to reuse existing automations by invoking a workflow from within another using the Call another workflow node.
Watch this step in the video · Flow control
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.inputvariable.
Variables available in the called workflow
$caller.input— the value you set in "Input". It's the only$caller.*variable that actually works today.- ⚠️
$caller.workflow_idand$caller.execution_id— not available today: even though they're documented, the node never actually populates them (due to an internal key-naming mismatch) and they always resolve empty. Don't rely on them in messages or conditions.
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.inputvariable (don't rely on$caller.workflow_id/$caller.execution_id, see above).
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.
Related articles
-
Build your first workflow
Omnifox workflows automate your operation: a trigger starts the automation and action nodes do the work. Build a welcome message in minutes.
-
Workflow triggers catalog
Learn which events can start a workflow automatically in Omnifox.
-
Workflows complete guide
Workflows in depth, in 54 chapters: triggers, nodes, variables, testing, history, templates, import and export, with every setting explained and a real workflow end to end.
-
Action nodes available in workflows
Discover the actions a workflow can run automatically.
-
Conditions and branching (if/then) in a workflow
Make your flows take decisions and follow different paths based on each contact data.