Network Composition
Network composition lets one workflow call another as a reusable sub-system.
In the canvas, hold Option and click a Network node to open its sub-network directly.
Why composition matters
Without composition, teams copy/paste logic and drift into inconsistent behavior.
With composition:
- shared modules are maintained once
- interfaces are explicit and testable
- cross-team rollout is faster and safer
Good composition design
- Keep subflow contracts narrow.
- Version interfaces intentionally.
- Define owner and deprecation policy.
- Track failure and adoption metrics.
Composition use cases
- shared normalization pipelines
- policy and approval subflows
- reusable enrichment stages
- common retry and fallback envelopes