Workflows overview - CtrlNode

A Workflow is a directed graph of steps. Each step maps to a task (agent, instructions, input files). When a run starts, CtrlNode activates steps in order and passes artifacts forward.

Definition vs run

	Definition	Run
Stored as	Workflow template (`run_number` empty)	Execution instance (`run_number` set)
You edit	Designer canvas, step config	Usually read-only; actions like cancel/archive
Status	`draft` until activated	`active` → `done` / `blocked` / `failed`

One definition can spawn many runs (manual Run, Activate, or a linked Routine schedule).

Designer

/projects/{projectId}/workflows
/projects/{projectId}/workflows/new
/projects/{projectId}/workflows/{workflowId}

Nodes — work steps (tasks) and trigger nodes
Edges — execution order
Save — persists the definition; autosave keeps the canvas in sync

Routines

Single-step scheduled jobs — simpler than full workflows.

Bridge requirement

Starting, resuming, cloning, and re-running workflows requires a connected Bridge. Without it, the UI disables destructive/run actions and the API returns 503. Next: Triggers