Connecting Nodes

Edges define how data flows between nodes. Understanding handles and routing is key to building effective workflows.

Drawing Connections

1. Hover over a node to reveal its handles — small circles on the edges of the node
2. Output handles appear on the right side of a node
3. Input handles appear on the left side
4. Click and drag from an output handle to an input handle to create an edge

Output Handles

Most nodes have a single output handle that carries their result data. Some nodes have multiple output handles for conditional routing:

Node	Output Handles	Description
Switch	case-1, case-2, ... + fallback	One handle per routing rule, plus optional fallback
All nodes (optional)	failed	Error output when "Enable Failed Output" is on
All nodes (optional)	fallback	Validation error output when "Enable Fallback Output" is on

Input Handles

Most nodes have a single input handle. The Merge node is an exception — it has two input handles (data1 and data2) to accept data from separate sources.

How Data Flows

Single Input

When multiple upstream nodes connect to the same input handle, the downstream node runs once per upstream source:

Node A → [output: {name: "Alice"}]
Node B → [output: {name: "Bob"}]
Both connect to → Transform node

Result: Transform runs twice — once with Alice's data, once with Bob's data

Multiple Items

When an upstream node produces multiple items, the downstream node processes each item individually:

Query Node → [output: [{id: 1}, {id: 2}, {id: 3}]]
Connects to → Transform node

Result: Transform runs 3 times — once per item

Multiple Input Handles (Merge)

The Merge node waits for data on both input handles before executing:

Node A → connects to Merge "data1"
Node B → connects to Merge "data2"

Result: Merge waits for both A and B to complete, then combines the data

Fan-Out and Fan-In

• Fan-out: One node's output connects to multiple downstream nodes — they all run in parallel
• Fan-in: Multiple nodes connect to a single downstream node — it waits for all of them

         ┌→ Node B ─┐
Trigger ─┤          ├→ Merge → Save
         └→ Node C ─┘

In this example, B and C run in parallel after the trigger. Merge waits for both before combining.

Edge Validation

The platform prevents invalid connections:

• No circular references — you cannot create a cycle in the graph
• No duplicate edges — only one edge per output-to-input pair
• Type matching — edges can only connect output handles to input handles