Subworkflows
Once you've built a workflow that does something well, you can call it from another workflow — the way you'd call a function in code. The Workflow block turns any workflow into a reusable step.
What you will learn
A workflow becomes a block
Any workflow can be invoked as a single block inside another, with an input in and its result out.
Call, run, return
The parent pauses at the call, the child workflow runs start to finish, and its output flows back into the parent.
Reuse and compose
Factor shared logic into one subworkflow instead of duplicating blocks; compose small workflows into big systems.
The workflow you already know
Start with a workflow you've built and trust — say one that classifies a message. On its own it's a complete process you can run.
Here's the shape of it — one workflow invoked as a single block inside another:
It becomes a block
Any workflow can be used as a block inside another. You drop a Workflow block, point it at the workflow you want, and pass it an input — just like calling a function. You don't rebuild its logic; you reuse it.
Call, run, return
When the parent run reaches the Workflow block, the child workflow runs start to finish — its own blocks, its own logic — and its result comes back into the parent, where the next block reads it. The parent doesn't need to know how the child works, only what it returns.
Workflows all the way up
This is how big systems stay manageable: factor shared logic into focused subworkflows and compose them. Each workflow you build becomes a building block for the next — small, tested pieces assembling into larger processes, without turning into a mess.