Connections#

A connection (or "edge") is the line that joins two nodes. Drag from a node's output handle onto another node to draw one. Click a connection to select it and the inspector on the right switches to its details.

Labels#

Give a connection a short label to describe what flows along it — for a decision node's outputs that's usually the condition (yes, no, paid, trial); on a step-to-step edge it might be a trigger (on retry, after timeout).

Labels are capped at 40 characters and render as a small chip near the source end of the line.

Payloads#

A connection can also carry a typed payload — useful when you want to sketch the actual data that moves between two steps (a request body, a queue message, a webhook envelope) without leaving the canvas.

Select a connection and click Attach data in the inspector. You'll get:

• A type picker — currently JSON or Text.
• A monospace editor with a 10,000-character limit.
• Live validation for the JSON kind.

When a connection carries a payload, the canvas chip shows a small icon next to the label — {} for JSON, a document for text. Connections with broken JSON tint red so they're easy to spot.

When to use which type#

• JSON — structured data with keys and values. The editor validates it as JSON on every keystroke and again on save, so what you store is always parseable.
• Text — anything else: a copy-paste of a log line, a CSV row, a pseudo-code snippet, a free-form note. No validation runs.

What payloads are not#

Payloads are documentation, not execution. Simple Hello doesn't run your flow, doesn't pipe the payload from one node to the next, and doesn't enforce that the data matches anything downstream. They exist so the people reading the flow can see at a glance what shape of data the connection represents.

Removing a payload#

Open the connection in the inspector and click Remove at the top of the Payload section. The connection itself stays — only the attached data is cleared.