fleet workflow <list|create|delete|trigger> [flags]Manages simple trigger-to-action workflows stored in the fleet database. Each workflow binds one trigger type to one action type — it is not a staged, multi-agent pipeline. You can list workflows, create or delete them, and manually trigger one by ID.
Workflows are distinct from the reactive event chain (which is the primary coordination model in Fleet). The list output is JSON; an empty list renders as [].
| --name <n> | Workflow name (required for create) |
| --trigger-type <t> | Trigger type to fire on (required for create) |
| --action-type <a> | Action to run when triggered (required for create) |
| --trigger-config <c> | Optional trigger configuration for create |
| --action-config <c> | Optional action configuration for create |
List configured workflows
fleet workflow listCreate a trigger-to-action workflow
fleet workflow create --name nightly-eval --trigger-type schedule --action-type evalManually fire a workflow by ID
fleet workflow trigger 2No. A workflow is a single trigger-to-action binding. For ordered, gated multi-agent sequences see `fleet pipeline`; for event-driven coordination see the reactive chain (watcher + fabric).
No. `workflow trigger <id>` runs the workflow's action directly, bypassing its trigger condition.
One binary. Five minutes. See every agent, coordinate every handoff, and keep a full audit trail of what your fleet did.