Skip to main content
Every Graph node leaves values for later nodes. The next node can take the default payload, or one named field.

Insert value

On a field that supports it, Insert value (plus) opens Previous nodes, Settings form when the Graph declares fields, and Secrets when the field allows them. Previous nodes lists every node above this one along edges, not the whole canvas. A sibling that is not above this node does not appear. Hint when the list is empty: Connect an incoming node to add its result here. Each row is Node: Field. The click inserts {{…}}. One incoming Trigger, or several Message triggers (Live, Telegram, Telegram account): the menu and the token both use Trigger. Example: Trigger: Chat ID inserts {{Trigger.chatId}}. {{Trigger.text}} is the trigger that started this Run.
Incoming triggers of different kinds share Trigger.text. Other fields use that node’s name (Live, Telegram, Webhook, cron trigger, …) and apply only when that node started the Run.
Rename a Tool or Agent in Name and the token follows the unique name: a node named Extract tables becomes {{Extract tables.text}}. Two nodes with the same name: the token uses the node’s id. Declared Instance fields are a separate group: Settings form. If none of the nodes above this one is a Trigger, the list also has Test input (Manual node) → {{Input}} (the Manual Test input, or the Run’s input text).

Empty field

Leave a field blank and some nodes use the Result of every immediate previous node, joined with a blank line. Agent User prompt works this way. So do several Tools (each Tool page says whether empty is allowed). That default is always Result (the node’s main text). It is not Chat ID, Files, or another named field. On Telegram send, empty Text uses previous Result (the message body). Empty Chat id is not Trigger: Chat ID and is not previous Result. Insert Trigger: Chat ID when the id must come from the Trigger. A Run that started from Telegram can still fill Chat id from that incoming chat. Workflow issues and Invalid appear when empty Chat id cannot be filled that way (for example after a cron Trigger). A field that requires a value does not fall back. File id on Extract tables is one of those: empty fails.

Result

Result is the primary text of the node. You see it under View results. Insert label: Result (Triggers use a kind-specific name instead: Message text, Body, Input text, Summary). Token field text. A bare {{Extract tables}} also resolves to that text; Insert value always writes the field form ({{Extract tables.text}}). Agent, Condition, Respond, and every Tool currently expose only Result in Previous nodes. Named fields for a Trigger are on that Trigger’s Output. Those fields appear when the Trigger sits above this node along edges.

JSON keys

A dotted key after a field reads inside JSON. {{Each item.item.data.email}} is the email column when the Loop walks a page from Read records. Insert value lists keys it can see. On Item inside that Loop: key, collection, data, createdAt, updatedAt, and columns from the collection schema. On Send email Result: ok, to, messageId, error. A missing key fails the step. A key uses letters, digits, and underscore, at most 6 parts. An index is not a key. Code still builds a new object when the step needs one.

Loop

On a node inside the card, Previous nodes lists that Loop. Result is the current element (Each item) or the Loop input (While). Index starts at 0. Item is the same text as Result. On a node connected from the handle on the right of the card, Result is JSON { "iterations", "stopped" }. Iterations and Stopped are those values. Item and Index are not listed there.

Agents and Tools

Previous nodes shows one row per Agent, Condition, Respond, or Tool above this node: Name: Result. The text is that node’s View results output. Extract tables Result is a markdown summary, not the table rows. Put tables into State with Import from a file and the same File id.

Photos and Files

Photos and Files expand to a JSON array of attachments, not a single File id.
id is the opaque id Extract tables needs. name is the filename — tools that take File id reject a filename. kind is photo, file, or email_part. Do not insert Trigger: Files into File id. Copy one id, let Agent decides pick it, or parse the array in Code.