Calling One Workflow From Another: Subworkflows
A workflow step can now call another workflow directly, so a chain you've already built doesn't need to be rebuilt inside every automation that needs it.
If you've already built a solid "post to Slack, then log it in the CRM" chain, Workflows now lets you call that entire workflow from inside another one, instead of rebuilding it step by step every time you need it.
What a subworkflow step does
A dedicated step type lets you call another workflow directly as part of the one you're building. Configure it once from the step's own panel, and any workflow that needs that logic can call it rather than duplicating the steps inline.
Why this matters beyond convenience
This is a familiar pattern if you've used another automation tool's version of the same idea — n8n's "Execute Workflow" node and Make's subscenarios solve the same reuse problem. What's worth pairing it with here is the dependency graph we're also shipping: once a chain of steps becomes a subworkflow that multiple automations call into, you can see exactly which workflows depend on it before you change it — rather than editing a shared subworkflow and hoping nothing downstream breaks.
Where to use it
Reach for a subworkflow any time you notice the same sequence of steps showing up in more than one automation. Build it once, call it from wherever it's needed, and when it needs to change, you change it in exactly one place — with the dependency graph telling you everywhere that change will land.