Call a Flow
Use the Call a Flow step to trigger another flow within the current flow. The Call a Flow step leverages flow reuse and can save you time from rebuilding entire existing flows.
Guidelines for calling flows:
For a flow to be callable, it must have a trigger type of On Demand.
A callable flow may call another callable flow.
A callable flow can’t call itself (recursion).
A callable flow can’t call a flow that is calling it (looping). For example, if flow A calls flow B, flow B can’t call flow A.
In the list of flows available to your workspace, callable flows are marked with a Callable tag. When you open a flow, the In Use By panel on the right of the flow builder page indicates which parent flows call that flow. You can select from these flows to view the parent flow.
Step Inputs
In the Edit Step menu, you can add details about the step configuration as needed for your flow.
Step Detail
Depending on the flow you call, additional property fields associated with that flow will display in this section. The called flow dictates what data is available to pass to it. Add data to all required property fields.
Flow
Choose the flow that you want to call. The dropdown list populates with all callable flows available to your workspace.
Select View Flow if you want to open the called flow in a new tab.
Use Existing Input
This option is off by default. As a best practice, you generally want to keep it off. You should use the property fields in the Step Detail section to specifically define the input you want to use in the called flow instead of using existing input values.
Step Dependencies
The Call a Flow step is dependent on another step in the flow. After saving your flow step, the dependencies section populates automatically with the following default values:
Dependent On Step Id: ID of the previous step
Dependent On Step Result Status: Successful
You can keep the default values or manually enter other values. The Dependent On Step Id field is required.
Note: If you rearrange the order of steps in your flow, the default Dependent On Step Id value will update to match the ID of the previous step. However, if you manually define a step ID in this field, it will not change even if you rearrange the order of steps in your flow. You can enter the ID of any previous step in the Dependent on Step Id field.
Step Status
You may see one of the following statuses after running the Call a Flow step:
SUCCESSFUL
Occurs when the called flow successfully completes, resolving to either a Successful or Failed status.
FAILED
Occurs when the called flow completes with an Exception status.
Step Outputs
The output of the Call a Flow step depends on the flow that is called and what data is returned after it runs.
Use Cases and Examples
Use the Call a Flow step when you want to execute a flow within another flow.
For example, say you are creating a flow to send budget information from Vista to ProjectSight. Before you send budget data between systems, you may want to process the data. So you could call a flow that processes Vista budget amounts, making sure amounts exist and are assigned a specific budget code. Instead of recreating this flow within your flow, you can call the flow.
