# Edges (/docs/concepts/edges)

How nodes are connected and how data passes between them.



An edge is a connection between two nodes. It defines execution order and enables data passing.

Drawing edges [#drawing-edges]

1. Hover over a node's output port (right side) - it highlights
2. Click and drag from the output port
3. Release on another node's input port (left side)

The edge appears as a line connecting the two nodes.

Data passing [#data-passing]

When Node A connects to Node B via an edge:

* Node A executes first
* Node A's output becomes available to Node B
* Node B can reference Node A's data using `{nodeAResponse.result.field}`

Deleting edges [#deleting-edges]

Click an edge to select it, then press **Delete** or **Backspace**.

Multiple outputs [#multiple-outputs]

A node can have multiple outgoing edges - its output is available to all downstream nodes. Execution follows the graph topology (nodes with no unresolved dependencies run next).

Condition node branching [#condition-node-branching]

The Condition node supports multiple output routes. Based on expression evaluation, execution follows one branch and skips others. Each route is a separate edge from the Condition node to different downstream nodes.

Next steps [#next-steps]

* [Triggers](/docs/concepts/triggers) - what starts the execution chain
* [Configuring Nodes](/docs/editor/configuring-nodes) - using upstream data in node settings