Settingsintermediate

Capability node types reference

Every node you can place on the visual canvas: what it does, when to use it, and what it produces for downstream nodes.

5 min read

Capability node types reference

The visual canvas builds a capability by connecting nodes into a flow. Every capability begins with a Trigger and ends with a Response; what happens between them is up to you.

The full node set

  • Trigger — The entry point. Defines the inputs the AI specialist must pass when it invokes the capability. — Every capability has exactly one. Declare your input parameters 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 — Branches the flow based on a value from upstream — string comparison, equality, numeric thresholds. — When the next step depends on what came back from a previous one (e.g., status is shipped vs. cancelled).
  • 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. — Every flow needs at least one. You can have multiple Response nodes downstream of branches.
  • Loop — Iterates over an array, executing the inner steps once per item. — Bulk lookups, processing each item in an order, fanning out to N parallel sub-calls.
  • Delay — Pauses the flow for a configured duration before continuing. — Rate-limited APIs, retry-after-wait patterns. Use sparingly — long delays hold the AI back.
  • Variable — Stores a value for later use, or reads a stored value back. — When the same value is needed in multiple downstream 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 — Executes a predefined system command. — Internal-tool integrations and operational tasks. Most tenants won’t need this.

Picking between Simple Tool mode and the canvas

If your capability is a single endpoint call — “look up an order by ID” — use Simple Tool mode. It’s a one-form alternative to the canvas that handles Trigger + API Call + Response automatically. Anything more involved (branching on the response, looping over results, calling two endpoints in sequence) should use the canvas, because Simple Tool mode can’t express those flows.

Connecting nodes

Drag from a node’s output handle to the next node’s input handle. The visual edge between them carries data downstream — every node has access to the output of every node it’s downstream of.

Each node is configured by clicking it and editing in the side panel. Save the capability as a Draft as you go; the canvas state is preserved between sessions.

See also

Tags

Ai FeaturesReference
Back to Settings