A workflow is a repeatable process you build as a vertical funnel: inputs at the top, ordered steps narrowing down, and a deliverable at the spout. The daemon walks the funnel in order and pipes each node's output into the next — control flow is enforced by the engine, not improvised by the model, so a workflow is repeatable and auditable (Power-Automate-style).

The four node types

• Input A seed value — the object/data the process starts from (e.g. a query, an ID, a block of text).
• Action A deterministic tool call. Pick a tool (a built-in or a connected integration) and bind its parameters. Runs exactly as specified — no model involved.
• AI A reasoning step. Write an instruction and the chosen model produces text (summarize, classify, draft). The only place the model decides anything.
• Output The deliverable — captures the previous node's result as the workflow's final output.

Piping outputs forward — placeholders

Every node has a short id (shown on its card: n1, n2, …). Reference an earlier node's output anywhere in a later node's instruction or action parameters with {{n1}}. Example: an AI node with Summarize {{n1}} and {{n2}} into a short report receives the live outputs of nodes 1 and 2.

Model & permissions

The Model field picks which model runs the AI nodes; the daemon auto-swaps to it before the run (leave blank to use whatever's loaded). Read-only mode refuses side-effecting actions (anything that writes/sends); Autonomous pre-authorizes them. Run launches now (watch it in Agents); Schedule runs it daily.