The Run Workflow step executes another workflow as a child process within the current workflow. It passes data to the child workflow's start step and receives the child's final output when it completes, enabling modular workflow design.

• Reuse a common workflow (e.g., "generate and email report") across multiple parent workflows
• Break complex automations into manageable, independently testable sub-workflows
• Call shared processing logic from different contexts without duplicating steps
• Organize large workflows into a hierarchy of smaller, focused workflows

The step starts with no field sets. They are copied from the child workflow at runtime. Execution happens in two phases: Phase 1 creates a child WorkflowRun, copies the parent's input to the child's start step, and queues the child's start jobs. The parent step then waits. Phase 2 triggers when the child workflow completes. The child's final output is copied to the parent step's output, and the parent workflow advances. A recursion depth limit prevents infinite nesting.