Concepts

Workflows

A workflow is a directed graph of nodes on a visual canvas. Each node does exactly one thing: trigger, decide, call an agent, wait for a human, call an API, or emit evidence. The canvas shows the graph statically when idle and lights up node-by-node during live execution.

The node palette — 22 types in five groups

TriggersStart a workflow. Schedule (cron), webhook, manual, objective trigger, and signal-based triggers.5 types

AI & AgentsAI Model node (generic LLM call), Agent node (predefined assistant), human:task (Human-in-the-Loop), and team:invoke (multi-agent delegation).4 types

Control flowIf/else, switch, loop (fixed + loop-item subworkflow), parallel branches, wait, and sub-workflow call.7 types

HTTP & integrationsHTTP request, tool call, MCP call, webhook emit, and transform nodes.5 types

GovernanceApproval gate (blocks until policy resolves), budget gate (hard-stops on overspend), VOLT emit (manual evidence write), and policy assert.4 types

Live execution overlay

When a workflow runs, the canvas stays open and updates in real time. Each node pulses when it becomes active, shows a green tick when it completes successfully, and shows a red badge when it errors. Tool calls emitted by agent nodes appear as a scrolling side-panel. The overlay does not require a browser refresh — it streams execution events via the collector WebSocket.

This is what "on rails you can see" means in practice: you are watching the actual execution graph, not a log file.

Versioning

Every workflow save creates a new version. The version history panel shows the diff between versions as a node-level change list. You can restore any previous version with one click. Restore creates a new version — it does not overwrite history. Deleted versions are kept in the audit log indefinitely.

Version metadata includes the saving user, timestamp, and a brief change note. If a workflow version was active during a run, the execution trace records the exact version that was running.

The workflow library

The library has two tabs: My Library (user-authored workflows) and Curated (12 Quox-curated templates covering common ops patterns). Curated templates are tagged with the agent types and tools they require. A template can be imported into your workspace with one click and then customised on the canvas.

Workflows can be exported from My Library as JSON and imported by another team member. Importing a workflow does not carry over execution history or VOLT traces — those remain scoped to the originating org.

The ?fromObjective= URL parameter pre-populates the workflow builder with context from an existing objective, including the objective title and any constraints. This is the path taken by the "Save as Workflow" CTA on the Home view.

Starting a workflow from a conversation

The Home view "Save as Workflow" CTA sends the current conversation to the WorkflowBuilder with the conversation context pre-filled as a human:task node and the conversation summary as the workflow description. This path was wired in P10.I-2 and is available to all users.