Flow Trigger
Executing another flow to split up logic in smaller chunks
Last updated
Executing another flow to split up logic in smaller chunks
Last updated
Flow Trigger has only one default action - Trigger flow. Optionally, you can select to execute the triggered flows synchronously or asynchronously.
Include the ID of the flow you want to execute.
Select execution mode. The default is asynchronously
If you include 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 you need to trigger multiple flows, you can place this additional trigger:
Right Behind the First Trigger: This way, multiple flows will be triggered sequentially, one after another.
At the End of the Triggered Flow: If you want the second flow to run after the first one completes its execution, you can place the Flow Trigger at the end of the first triggered flow. This ensures that the flows execute in a specific order.
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.
It immediately triggers the flow and continues with the next subsequent step in the initial flow. If it is set to asynchronously, the flow with the 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.
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.
