Subflows

A Subflow is a Flow that is triggered by another Flow, using the Trigger Step templates in both the Subflow itself and the main Flow.

We recommend using Subflows in the following cases:

• Trigger them to do calculations and return data to the main Flow.
• Isolate the logic that can be re-used to reduce the size and complexity of Flows (as large Flows can take longer to load and edit, and smaller Flows can easily be re-used and quickly iterated upon).
• Encapsulate modal logic in one place.
• Trigger Flows across different accounts.
• Program them to take over a conversation, and set them up to run synchronously or asynchronously.

Any Flow within your solution can trigger a Subflow as many times as needed during the business logic execution. For example, Subflow #1 can also trigger Subflow #2 and so on. Since Subflows are separate Flows, they have a cold start, meaning they need more time to start their execution.

The data between Subflows can be transferred through Shared Merge fields.