A workflow is a repeatable, multi-step process that agents run on their own, pausing only where you ask. You build it on the board, save it as a version, activate that version, and then run it by hand, on a schedule, or from your own systems over the API. In a governed deployment everyone assigned sees and edits the same workflows (Working in a governed deployment).
The five step types
| Step | What it does (the rail's words) | Pauses for you |
|---|
| Task | "An agent works an objective and produces an output." | Only with a hold or go-ahead switched on |
| Handoff | "The run pauses until you read a message and give the go-ahead." | Always |
| Conditional | "An Opus evaluator picks one labelled branch; the others are skipped." | No |
| AMPG update | "Build the next training PDF from upstream results and create the AMPG version." | When you hold the PDF for review |
| Redact PII | "Write a copy of a file with personal data masked, hashed or its rows dropped - before it leaves the run." | No |
Where to go
| I want to | Page |
|---|
| Add and wire steps, set parameters and run settings, save and activate a version | Build |
| Turn a finished chat into a workflow (type "Convert this to a workflow" in the composer) | Chat: turn a conversation into a workflow |
| Run now or on a schedule, read the runs list and a run page, approve, send back or stop a waiting step | Run, schedule, approve |
| Train the next knowledge-graph version from a run's results | Knowledge-graph update node |
| Start runs from another application (governed deployments, API key) | Trigger from outside |
| Redact personal data at chosen stages of a run | PII redaction |
| Share a workflow, with its dependencies, to other deployments | Libraries and sharing |
| Act on held steps without opening the run | Inbox |
The lifecycle
- Open Workflows from the dock (or Workflow Management, then Workflows). The list shows Name, Status (Active or Inactive), Nodes, Version and Last Updated, newest first, with Search workflows....
- Build on the board; the chip reads Ready to save when every step is complete.
- Save as version. Every save creates a new version; nothing runs until one is active.
- Activate a version in the Workflow Versions table. Run Now, Run on Schedule and Share unlock; the active version is the one schedules and API keys use.
- Run, follow it on the run page, and act on Needs you steps on the card, in the Summary or in the Inbox.
Notes
- 20 steps per workflow; 256 workflows per user; name 80 characters; description 1,000; graph definition 8 MiB.
- An agent, connector or knowledge graph used by an active workflow version cannot be deleted or repointed until the workflow is detached or another version is activated.