Automation runs & approvals
The other half of Automations: run history per lifecycle state with cancel, plus the approvals queue — the human gate an automation pauses on before any money-moving or irreversible step (approve releases the dispatch; reject routes to the failure path).
If you are building a front end
Your front end calls this over the same-origin `/api/v1` proxy — no backend code to write, no schema to design. Endpoints: GET/POST /api/v1/wf/executions, GET /api/v1/wf/executions/:id, POST /api/v1/wf/executions/:id/cancel, GET /api/v1/wf/approvals, POST /api/v1/wf/approvals/:id/decide.
Bring any front end — hand-written, or generated with Lovable, v0, Bolt, Claude, or Cursor. You get auth, a multi-tenant database, payments through your own Stripe, and email/SMS without writing or hosting a backend.
- How to turn it on
- Linked from the Automations page; same 'workflows' module toggle.
- Who can use it
- RBAC: wf.executions.read (runs) / wf.executions.act (cancel) / wf.approvals.read (queue) / wf.approvals.act (decide).
- The API behind it
GET/POST /api/v1/wf/executions, GET /api/v1/wf/executions/:id, POST /api/v1/wf/executions/:id/cancel, GET /api/v1/wf/approvals, POST /api/v1/wf/approvals/:id/decide- Where it lives
- /workflows/runs
See it in context
Workflow automation — the full walkthrough, step by step: Triggers, sequences, and approvals — the busywork runs itself, no code.
Machine-readable
This page is generated from our published capability catalog. Point your AI assistant at /features.json (or /llms.txt) and it can read every feature, how to enable it, and the endpoints behind it — then build against them.