Sub-workflow¶
Group steps into a separately editable child flow and reuse them within the current workflow.
Use it when several locations need the same cleaning, chunking, or field-processing sequence.
Create and edit¶
Add a Sub-workflow node to the current workflow.
Double-click it to edit its steps on a separate canvas.
Configure internal inputs, outputs, and connections.
Return to the main flow and connect the surrounding nodes.
Several call sites can reference the same child flow. After changing shared steps, check that each call site’s inputs and outputs still match.
Pass data¶
The child flow’s first processing node receives the caller’s data. Its final result is available to later main-flow nodes. Agree on a common field structure before reusing the flow.
For example, a cleaning and chunking child flow can accept and return documents, which the main flow then writes to a knowledge base.
When to use Workflow Trigger¶
Sub-workflow organizes reusable steps within the current workflow. To start another published workflow, use Workflow Trigger, select its version, and supply its inputs.
Example: reuse preprocessing¶
Flow: Main flow → Clean and chunking sub-workflow → Write to knowledge base.
Place cleaning and chunking in the child flow. Check that document content and source information remain intact before referencing the sequence from multiple locations.