Edges are the lines that connect nodes on the canvas. They do two things: they set the order in which nodes run, and they carry each node’s result forward so the next node can use it.
Drawing a connection
Every node has connection points called handles. To connect two nodes, drag from the handle on the right edge of the source node to the handle on the left edge of the target node. A line appears between them, and the target node now runs after the source node.
- Hover over the source node until its right-side handle appears.
- Press and drag from that handle toward the next node.
- Release over the target node’s left-side handle.
To remove a connection, click the edge and delete it, or drag its end off the handle.
Branching handles
Most nodes have one input and one output. A few nodes branch:
- The Condition node has two output handles, a true path and a false path, so the workflow can take different routes depending on the result.
- Nodes that produce named fields, such as the AI Prompt node with structured output turned on, still connect with a single edge. You pick which field a later node reads by using a variable tag, not by drawing a separate edge. See Data Flow and Variable Handling.
Passing data between nodes: variable pills
Connecting two nodes lets the second node reference the first node’s output. You insert that reference inside a text field as a friendly variable pill. A pill reads as plain language, for example “input from Summarize”, but it stores the exact tag the workflow engine needs underneath.
The two tag formats a pill can hold are:
[Input from node-1] the whole output of node-1
[[title] from node-1] one named field from node-1The “/” picker
You do not have to type tags by hand. Inside any field that accepts variables, type / to open the insert menu. It lists every upstream node whose output you can use. Pick one and the plugin drops in the correct pill for you.
Keep typing after the / to filter the list, use the arrow keys to move, and press Enter to insert. This is the reliable way to reference another node, because it always writes the exact node id.
Order of execution
The plugin follows the edges from the trigger outward. A node runs only after every node feeding into it has finished, and its result then flows along its outgoing edges. You can watch this happen node by node in the live execution panel.