Nodes
Nodes are the units of work in a flow. Workbench ships a large catalog — hundreds of nodes — and you compose them on the canvas from the palette. The families:
ModelsLLM + embedding nodesOne node per chat or embedding model, across every supported provider. The node is the model. Picking a different model means dropping a different node onto the canvas. This is what lets a flow outlive any single model.
Agents & toolsagent loop + tool definitionsAn agent node runs a full tool-calling loop against a model. A tool node declares a function (name, description, JSON-Schema parameters) the model can call. Agents can use built-in web tools, or other flows as sub-tools.
Data, text & logictransforms + control flowParsers and serializers (JSON, CSV, XML, YAML), string and list operations, math, dates, conditionals (if/else, switch, comparators, boolean gates), and routing. The glue that shapes data between model calls.
KnowledgeretrievalRetrieval nodes — semantic and keyword search, SQL queries, document browsing, and graph traversal — for grounding a model in your own content. See Knowledge bases.
Integrationsexternal servicesNodes that read from and write to the systems your team already uses. These get their own page — see Integrations.
The catalog is the source of truth
The palette in the editor always reflects what's available — the catalog grows over time, and a flow you've already published keeps running regardless of what's added. You build the behavior in the editor and call the finished flow by its inputs and outputs; your integration never enumerates nodes.