Comment on page
Execute Subflow
Like the built-in Subflow element but better.
This is an advanced action. If your subflow is not optimized or this action is used repeatedly (e.g. in a loop), your Flow may run poorly or fail. Unless you specifically need the functionality provided here, use the native Subflow element.
Flow provides the ability to run a subflow natively through the Subflow element. This action provides additional capabilities such as the ability to schedule the subflow to run at a future date.
The native Subflow element also requires you to select the Flow from a list of known Flows, preventing you from using logic in the calling Flow to choose a specific subflow to execute. This action provides the ability to invoke a Flow using the value of a resource in the calling Flow. This allows you to dynamically execute a subflow based on the result of a decision or formula in the calling Flow.
Please note the following limitations:
- Subflows must be active and auto-launched without a trigger
- Only Text, Number and Boolean types are supported for inputs
- Subflow outputs are not currently accessible from this action
Please note that you will not directly interact with these input fields as you do with some Flow Actions. Instead the Gradient Works custom editor takes care of the heavy lifting.
Name | Required | Type | Description |
|---|---|---|---|
flowApiName | Yes | String | The API name of the Flow to execute |
executionDelay | No | Integer | If Flow is scheduled, number of minutes to wait before invoking Flow |
executionSchedule | No | String | One of 'immediate' or 'scheduled'. Should the Flow be invoked immediately or scheduled to run later. |
flowInputData | No | String | Data that describes the Flow inputs. See action overview for more information about supported inputs. |
flowInterviewGuid | No | String | Automatically provided as $Flow.InterviewGuid. |
This action does not currently support retrieving output variables from the subflow.
Last modified 9mo ago