Multi Flow Trigger

Executing other flows to split up logic in smaller chunks


The Multi Flow Trigger enables you to trigger up to 10 flows by simply specifying their Flow IDs (UUID4 of the respective flows) in a comma-separated manner.


The Multi Flow Trigger has only one default action - Trigger multiple flows. Optionally, you can select to execute the triggered flows synchronously or asynchronously.


  1. Include the IDs of the Flows you want to execute comma-separated in the field.

  2. Select execution mode. The default is asynchronous

If you include a Multi Flow Trigger in a Loop to call many other flow runs (e.g. more than 100), it is best practice to include a small delay, using the Delay Helper, in order to limit the load on the new flow and any systems it may call.

If multiple flows are triggered from one Multi Flow Trigger they cannot access the variables from another flow that has been triggered by the same Multi Flow Trigger. Instead, you can either add another Multi Flow Trigger to the main flow, right behind the first trigger, or add it at the end of the triggered flow.

Synchronous and asynchronous execution:

In both execution modes, it is possible to access variables previously defined in the initial (trigger) flow in the subsequently triggered flows.

This means, that if there is zendesk_contacts defined in the initial (trigger) flow, you can just reference {{ zendesk_contacts[1] }} in the triggered flow to get the first contact of Zendesk from the initial flow.

1. Asynchronous

It immediately triggers the flows and continues with the next subsequent step in the initial flow. If it is set to asynchronously, the flow with the Multi Flow Trigger cannot access the variables of the other flow (as it might not have run yet). Therefore you can't access variables defined in the triggered flows back in the initial (trigger) flow.

2. Synchronous

This mode waits for the underlying flows to be finished executing. If it is set to synchronously, you can access variables defined in the triggered flows back in the initial (trigger) flow.

In case of variables with the same names, the most recent instance will be referenced.

Last updated