Workflows

A workflow is a DAG of steps — skills, prompts and tool calls — that runs as one unit. It is the difference between asking the agent to do something and having a repeatable procedure with a defined shape.

Provided by @moxxy/plugin-workflows. The executor itself is a swappable block, so how a DAG is walked, retried and resumed can be replaced.

Why they matter more than chat

Enterprises do not buy conversation; they buy repeatable automation with a record. A workflow plus a trigger plus the audit trail is "this ran, under this policy, invoking these tools, at this cost, denied here" — which is an artefact somebody can review.

Running one

moxxy workflows list
moxxy workflows run <name>

Or on a trigger, with no one at the keyboard:

moxxy schedule add nightly --cron "0 3 * * *" --prompt "run the release checklist"
moxxy schedule add once --at "2026-08-01T09:00:00Z" --prompt "…"

Or from an external system, through a verified webhook with HMAC or bearer authentication, include and exclude filters, replay protection and delivery idempotency.

Shape

Steps declare their dependencies, so independent work runs in parallel and the executor only serialises what actually has to be ordered. A step that fails stops its own branch rather than the whole run, and the run is resumable.

Authoring

@moxxy/workflows-builder is the typed builder. The agent can also author one for you and register it, the same way it can author a skill.

Next

• The scheduler
• Webhooks
• Subagents — the other way to fan work out