How your Nodes actually relate to each other.
A tracker feeds a landing page. An ad account promotes an offer. A Connection records that relationship explicitly, on real Nodes in your Network — so your infrastructure is a graph you can see, not a set of accounts you have to remember are related.
The 4 relation kinds
The 4 real relation kinds
A Node relies on another to operate — a landing page uses the ad account driving traffic to it.
Four relation kinds, nothing invented
Uses, Feeds, Promotes, Managed by — that's the exhaustive set. Uses records that one Node depends on another to operate. Feeds records data or traffic moving from one Node into another. Promotes records one Node marketing or driving demand toward another. Managed by records that one Node is operated or administered through another. Every Connection you create picks exactly one of these four; there's no free-text relation field to misuse.
Only between Nodes you actually have
A Connection can only be drawn between two Nodes already in your Network — never a Marketplace listing you don't own, never a placeholder. That constraint is what keeps the graph honest: it's a record of your real infrastructure, not an aspirational diagram.
What Connections feed into
A Stack groups Nodes; the Connections between them are what make that grouping meaningful rather than arbitrary. A Workflow's Invoke Integration step tests the connection between a Node and a published Integration — the same relationship concept, applied to an external provider instead of another Node in your Network.
Capabilities
What this is backed by: lib/validation/connection-create.ts's CONNECTION_TYPES; rendered with @xyflow/react on /network's graph view.
Related Platform features