Skip to main content
Edges connect one node’s output to another node’s input, turning your canvas into an executable graph. Connecting two nodes with an edge Edges don’t just move data — they orchestrate execution. When a node finishes, its outputs flow along connected edges. Any downstream node whose inputs are now ready is queued to run next. Read more about the execution model in the Execution Flow guide.

​
How Edges Affect Execution

  • Data flow: Outputs from an upstream node become inputs for downstream nodes.
  • Scheduling: As soon as required inputs are available, the next node is eligible to run.
  • Most nodes wait for inputs to be available on all input ports before running and run on one input item per port at a time.
  • Others (like the Merge node) run on all available input items at once.

​
Edge Types (What You’re Connecting)

  • Input edges: Connect output → input. These drive the main flow of data and execution.
  • Config edges: Connect config nodes → config ports. These provide static configuration and run before the main node executes.

​
Quick Tips

  • You can fan out one output to multiple inputs to branch execution.
  • You can fan in multiple outputs to a single node, as long as it receives the inputs it expects.