Skip to main content
The Workflow node lets you redirect the conversation from within a flow to another workflow in the same project. It’s useful for splitting large automations into smaller, reusable flows.
Don’t confuse it with the WhatsApp Flows node — that node triggers a native WhatsApp form (Meta Flow) within the conversation, and has nothing to do with jumping to another workflow in the project.

​
Configuration

Select the target workflow from a dropdown listing all the project’s workflows, sorted alphabetically.
1

Select the workflow

Click the node to open its configuration panel and choose the target workflow from the dropdown.
2

(Optional) Go to the target workflow

Use the “Go to workflow” button to open the selected workflow’s canvas directly and edit it, without leaving the builder.
While no workflow is selected, the node shows “Click to configure your workflow”. If the configured workflow was deleted or is no longer available, the node shows a warning indicating it’s unavailable.

​
Data masking (DLP)

The node includes Data Loss Prevention settings to mask sensitive information in the logs generated by this node.

​
Outputs of the target workflow

Available since the End node was enabled in every workflow.
If the workflow you selected declares outputs with End nodes, the node draws them as connection points, one per output, with its display name and the color of its type (Success, Error or Neutral).
  • Connect each output to the matching branch. That’s how the parent workflow branches on how the child ended.
  • The child workflow runs inside the parent when outputs are connected: the parent waits for it to finish and continues down the output it took, instead of redirecting the conversation.
  • The variables declared in each output’s schema become available in the parent’s variable picker as $memory.response.<variable>.
  • The node reads the target workflow’s current outputs: as soon as you add an output in the child, it shows up here.
  • A node with outputs can’t be collapsed, because collapsing it would hide the connection points its routes hang from. If you had collapsed it before the child had outputs, you can still expand it.
Nodes whose target workflow has no outputs behave exactly as before.

​
Flow behavior

  • If the target workflow declares no outputs, the node has a single output: it redirects the flow and doesn’t distinguish between success and error.
  • If the target workflow declares outputs, the node shows one per output and the flow continues down the one the child took.
  • Conversation context and variables are shared automatically between workflows; you don’t need to map variables manually.
This node isn’t available inside a developer skill or pocket skill (for example, tools) — you can’t insert a jump to another workflow in that context.