Settingsintermediate

Capability node types reference

Every node in the advanced editor's Node Palette: what it does, when to use it, and what it produces for the rest of the flow.

5 min read

Capability node types reference

The advanced editor builds a capability by connecting nodes into a flow. Every capability must contain a Trigger — the run fails without one — and normally ends with a Response; what happens between them is up to you.

The full node set

These are the ten entries in the Node Palette. Click one to drop it on the canvas.

  • Trigger — The entry point. Its only setting is the trigger type — Manual, Webhook, Schedule or Event. — Every capability needs one, and the run fails if there isn’t one. Input parameters are declared on the capability itself, not here.
  • API Call — Sends an HTTP request to an external service using a configured API and endpoint. — Any time the capability needs to talk to an outside system.
  • Condition — Evaluates a field against a value and records whether it passed. Operators: Equals, Not equals, Contains, Greater than, Less than, Is empty, Is not empty. — When a later step needs to know what came back from an earlier one (e.g., status is shipped vs. cancelled). See the note under Connecting nodes about what True/False branches do today.
  • Transform — Reshapes data between steps — pluck fields, rename them, format a string. — When an API returns more (or differently shaped) data than the response needs.
  • Response — Returns the final result to the AI specialist that called the capability. — Add one. Only the first Response node in the capability supplies the returned value; with no Response node at all, the capability returns every node’s output.
  • Loop — Walks an array and leaves the last item in a named variable, plus the item count. It does not re-run the nodes after it once per item. — Reading the size of a list, or picking up its final entry. Not a way to fan out repeated work.
  • Delay — Pauses the flow for a configured number of milliseconds before continuing, capped at 60 000 ms. — Rate-limited APIs, retry-after-wait patterns. Use sparingly — the customer is waiting on this.
  • Variable — Stores a value under a name so later nodes can read it with {{...}}. — When the same value is needed in multiple later nodes and recomputing it is expensive.
  • AI Process — Runs an inline AI step against arbitrary text — classify, extract, summarize, generate. — When the API returns free-form text the capability needs to interpret before responding (e.g., summarize a long support history).
  • Command — Runs one of four allow-listed network lookups against a target you supply: DNS Lookup (dig), Name Server Lookup (nslookup), Domain Info (whois) and Ping. — Domain and connectivity diagnostics. Nothing else can be run — arbitrary commands are rejected.

Picking between the guided editor and the advanced editor

If your capability is a single endpoint call — “look up an order by ID” — use the Guided editor. It’s a one-form alternative that wires up the call for you with no nodes at all. The advanced editor is for flows the guided form can’t express.

Note that the advanced editor is only offered on a capability that already has nodes: both ways in — the Advanced toggle in the editor header and the Switch to advanced editor item in the overflow menu — are hidden while a capability is new, and on a guided capability with an empty canvas.

Connecting nodes

Open a node’s ⋮ menu and choose Connect to…, then click the node it should feed. On a Condition node, use its True and False buttons instead and click the node that each branch should reach.

Two things to know about how a saved flow runs. First, it runs every connected node once, in the order the edges lay out — a Condition’s True and False targets both run, whichever way the condition evaluated, so treat a Condition as a value you can read downstream rather than as a switch that skips work. Second, values are shared globally rather than passed along an edge: any node can read any earlier node’s output, its stored variables, and the original input.

Each node is configured by clicking it and editing in the properties panel on the right, or via ⋮ → Configure. Use Save as you go; the canvas is stored with the capability and is there when you come back.

See also

Tags

Ai FeaturesReference
Back to Settings