Run workflow: reuse a flow inside another
Build “clean and QA an image” once and call it as a single step from every campaign — one run, one cost total, and fixing it once fixes it everywhere.
In this article (5)
The moment you have three flows that all start by cleaning an image, you want that prep to exist once. The Run workflow card runs a saved flow as a single step inside another.
Using it
Add the card, pick the child workflow. Its inputs appear as rows, pre-filled to match your current flow's columns by name — edit any of them to a fixed value or a placeholder such as {previous.text}.
It runs once per item, inside the same run. That matters: you get one monitor, one cost total, and per-key parallelism across the whole thing — not a swarm of child runs to reconcile. The child's steps appear inline in results as <card> / <step>.
What the child needs
A batch input card, whose columns are its input interface — that is what the parent matches names against. Otherwise a child is an ordinary saved flow; nothing about it is special-cased.
Fix once, fixed everywhere
The child is resolved when the run starts, so improving the child improves every parent's next run. No re-wiring, no copy-paste drift. A run already in flight keeps the version it started with.
The guardrails
- Nesting is capped at 5 deep.
- A flow cannot call itself, directly or round a longer circle — the cycle is rejected rather than discovered at runtime.
- A child may itself branch or loop; a Repeat inside a child is unrolled inside the parent's run and behaves exactly as it would on its own.
Worth pairing with pinning
A shared prep step is the ideal candidate for Reuse output: tick it on the child's expensive step and the same input is never paid for twice, no matter how many parent flows call it.