Workflows

A workflow is a graph of typed nodes: a trigger, optional input, AI steps, conditions, tools, actions and an output. Each node type declares its own configuration schema, so the builder can validate a workflow before it ever runs.

Node types#

• Triggers — manual, webhook, or when a conversation starts.
• Input — a typed form of values the run begins with.
• AI — generate text from a prompt template, or classify into one of a set of categories.
• Condition — branch on a run variable.
• Tool — an outbound HTTP request, disabled unless explicitly allowed.
• Action — create a contact, send a notification.
• Output — the response the run returns.

Templates#

Prompt and request templates interpolate run variables with {{path.to.value}}, resolved against the values produced by earlier steps.

Validation#

A workflow must have exactly one trigger, no cycles, edges that point at real nodes, and valid configuration on every node. Unreachable nodes are reported as warnings. Problems appear in the builder as you edit rather than at run time.

Preview#

The builder has two views of the same workflow. Build is the editor. Preview draws the workflow as a diagram: every step as a card showing its type, name and a one-line summary, and every connection as an arrow, with both sides of a branch labelled “If true” and “Otherwise”. It reads the definition you are editing, so unsaved changes appear straight away and are marked as such.

• Read-only — the preview can pan, zoom, fit to view and select a step. It has no way to move, delete, reconnect or reconfigure anything; the editor stays on the Build tab.
• Inspect a step — selecting a card dims everything that is not upstream or downstream of it, and shows what that step does and what it is connected to. Credentials are never shown: an HTTP step lists its header names, never their values.
• Walkthrough — the same workflow as a numbered list, with each step's summary and where the run goes next. It is always on the page, works with a keyboard and a screen reader, and is the presentation used on narrow screens where a diagram would be unreadable.

Runs#

Running a workflow records a run with a status and a step-by-step timeline, including each step's output, error and duration. Tool and action steps are simulated unless a step explicitly allows outbound traffic and its target host is on that step's allowlist.