Overview
The Run Workflow action allows you to run another workflow asynchronously and independently from your current workflow. This effectively “queues” the workflow but does not wait for a response. You can select the workflow to run and map its inputs from the inputs or action outputs of the parent workflow. Advanced settings allow you to conditionally run the child workflow based on specified conditions. If the conditions are not met, you can configure a custom stop message explaining why the workflow was not run. The outputs of the queued child workflow are processed separately in the queued workflow’s table tab.
Usage Examples
Queue any workflow asynchronously - The "Run Workflow" action allows you to queue up and run any other workflow from within your current workflow. The queued workflow will run asynchronously and independently from the parent workflow that triggered it. You can use your main workflow to set up and initiate various other workflows and processes downstream without them interfering with the completion of the parent workflow. The outputs of the queued workflow will be processed separately in that workflow's own run.
Inputs
Choose a workflow - When choosing a workflow, you’ll be able to select any workflow from the current Teamspace.
Select the workflow you want to run.Dynamic inputs - Inputs display dynamically within the action configuration section based on the workflow you are trying to queue or run. They match the inputs required by the child workflow.
Use parent workflow inputs or previous action outputs as input to the child workflow.
Advanced Inputs
Run conditionally toggle - This toggle under the advanced settings allows you to run the child workflow based on certain conditions rather than running it automatically.
Turn the run conditionally toggle on and add one or more conditions.Custom stop message - If the conditions for running the workflow are not met, you can configure a custom message to explain why the workflow did not run. By default this message is set to “Did not run.”
Edit the default "Did not run" stop message to add reasoning.
Outputs
The Run Workflow action does not directly produce any outputs in the parent workflow where it is executed. Instead, the outputs and logs are processed and displayed within the separate, asynchronous child workflow table tab that is being queued and run by the Run Workflow action.
Example of a conditional workflow run that did run:
{ "queued": [ "WRUN-{example_workflow_run_id}" ], "invalid": [], "workflowConfigUUID": "WCFG-{example_workflow_config_id}" }Example of a conditional workflow run that did not run:
{ "queued": [], "invalid": [], "workflowConfigUUID": "WCFG-{example_workflow_config_id}" }
Troubleshooting
Workflow not running as expected - If the workflow you queued using the Run Workflow action is not running as expected, check the conditions you set in the advanced settings. If the run conditionally toggle is on, ensure the condition(s) you added are being met. If the conditions are not met, the workflow will not run.
Missing outputs from queued workflow - The outputs from the workflow you queue using the Run Workflow action will not appear in the top-level/parent workflow. They will only be visible and processed within that separate, asynchronous queued workflow run. To view the outputs, you need to check the table view or logs of the specific queued workflow run itself. If you need to access the outputs of the queued workflow in the current parent workflow, use the Run Workflow (Inline) action instead.
Unable to get a predictable value for comparisons on conditional runs - The categorize action can be used to generate a predictable and stable response that can be used for evaluating a condition. This is a best practice that greatly simplifies conditional runs. The simplest way to do this is to take a value and categorize “TRUE” or “FALSE” with a description that describes your condition.
Related Actions
Run Workflow (Inline) - This is a standard action to run another workflow, but unlike Run Workflow, the queued workflow will run in line as an action of the parent workflow that triggered it, and you’ll be able to reference the outputs of the inline workflow in the parent workflow. This is useful if you need to see the results of the queued workflow.