Skip to main content

Sub-workflows

You can call one workflow from another workflow. This allows you to build modular, microservice-like workflows. It can also help if your workflow grows large enough to encounter memory issues. Creating sub-workflows uses the Execute Workflow) and Execute Sub-workflow Trigger nodes.

Sub-wokflow executions don't count towards your plan's monthly execution or active workflow limits.

How data passes between workflows​

As an example, imagine you have an Execute Sub-workflow node in Workflow A. The Execute Sub-workflow node calls another workflow called Workflow B:

  1. The Execute Sub-workflow node passes the data to the Execute Sub-workflow Trigger node (titled "When executed by another node" in the canvas) of Workflow B.
  2. The last node of Workflow B sends the data back to the Execute Sub-workflow node in Workflow A.