Node Explained · Lesson 10 of 12
USE CASE Node: Reusable Workflows as a Single Step
When two workflows need the same check, the copies start to drift. Build it once and call it as a single step: the child's START inputs become the node's inputs, and its END mapping becomes the node's outputs.
What You Will Learn
- Calling another workflow as a single step with a USE CASE node, instead of rebuilding its logic
- Why the child's START inputs become the node's inputs and its END mapping becomes the node's outputs
- How the child gets its own execution record, logs and debugger, nested inside the parent rather than hidden from it
- Improving one child workflow once and watching every workflow that calls it get better at the same time
- Combining a USE CASE node with FOREACH for the standard batch pattern: handle one item properly, then call it once per row
- Why copy-pasted logic across workflows always drifts, and why that is the real cost