Workflow

The Workflow block executes another (child) workflow from within the current (parent) workflow. It reads the child workflow's Input Form Trigger schema and presents a mapping UI so you can pass parent variables into the child's expected inputs. This is the primary mechanism for modularizing complex automations into reusable sub-workflows.

Overview

Select a child workflow: Pick any workflow in your workspace (except the current one)

Map inputs: The block reads the child's Input Form Trigger and shows each expected field. Map parent variables or hardcode values for each one.

Execute: The child workflow runs to completion with the mapped inputs

Return results: The child's final output is returned to the parent as the block's result output

How It Works

The child workflow must use an Input Form Trigger as its start block. That trigger defines the input schema (field names, types, and descriptions). When you select the child workflow in this block, the Input Mapping UI dynamically renders those fields so you can wire them up.

At runtime the block:

Resolves all mapped values from the parent workflow's current state.
Invokes the child workflow's executor, passing the resolved inputs.
Waits for the child to finish.
Returns success, childWorkflowName, and the full result from the child execution.

The dropdown only shows workflows in your workspace that are different from the current one. You cannot call a workflow recursively.

Configuration

Select Workflow*

Select...

Input Mapping

Map fields defined in the child workflow's Input Trigger to variables/values in this workflow.

Fields

Field	Required	Description
Select Workflow	Yes	The child workflow to execute. Must have an Input Form Trigger.
Input Mapping	--	Dynamic mapping of parent values to the child's trigger schema. Appears after you select a workflow.

Outputs

Output	Type	Description
`success`	boolean	Whether the child workflow completed successfully
`childWorkflowName`	string	Name of the executed child workflow
`result`	json	The full execution result from the child workflow
`error`	string	Error message if the child workflow failed

Best Practices

Design child workflows with clear Input Form Triggers -- name fields descriptively so the mapping UI is easy to use in the parent.
Keep child workflows focused -- a child workflow should do one thing well, making it reusable across multiple parents.
Check the success output -- use a Condition block after the Workflow block to handle failures gracefully.