Glossary
Workflow — the scenario you assemble in the editor: a graph of nodes and edges. The unit that gets saved, versioned and published.
Graph — the nodes and edges themselves. In JSON that is { nodes, edges }.
Node — a unit of work: a model call, an API request, a branch, a file read.
Port (handle) — a named point on a node that an edge attaches to. A port has a wire type and a payload type.
Wire — what an edge carries: order only, value only, both, a token stream, or a resource attachment. See Wires.
Edge — a connection between two ports.
Entry — the graph boundary where the user’s message, or the caller’s object, arrives. There is exactly one per graph.
Exit — the boundary whose value is returned as the answer.
Execution (run) — one execution of a workflow, with its own history, status and cost.
Session — the chain of runs belonging to one conversation. Session-scoped memory lives inside it.
Thread — a sub-branch of a conversation in channels that distinguish them (a topic in a Telegram group, say).
Deploy — pushing a specific saved version of the graph into a channel. A draft only works on the Test tab.
Channel — a delivery route: public chat, widget, Telegram, webhook, schedule.
Credit — the billing unit; one credit is one cent. See Credits.
Workspace — the working space: its own workflows, connections, files, knowledge bases and collections. Data is scoped to it.
Connection — stored credentials for an external service (a model, mail, Telegram, a CRM). Nodes reference a connection instead of keeping keys inside themselves.
Secret — a named encrypted workspace value, available in templates as
{{ secret.NAME }}.
Knowledge base — a set of documents split into chunks and indexed for semantic search. See Knowledge bases and RAG.
Collection — a JSON document store, worked with through the db_* nodes.
Agent — a node that converses with a model over several rounds and can call tools.
Tool — a node attached to an agent over a link_extension wire. The model calls it, the
graph does not.
Memory — a node that keeps conversation history and injects it into the model request.
Template — text with Jinja substitutions: {{ inputs.message }},
{{ nodes.<id>.output }}, {{ variables.<name> }}. See Templates.