# List workflows

> The account's recurring workflows with their schedule, next run and step list.

Canonical: https://revnu.com/docs/workflows
Last updated: 2026-10-24

```bash
curl -H "Authorization: Bearer $REVNU_API_TOKEN" https://revnu.com/api/v1/workflows
```

## Response

`{ "workflows": [{ workflowId, name, description, status, scheduleText, scheduleEcho, scheduleError, deliverTo, nextRunAt, version, steps: [{ id, title, details, gate? }], url }, …] }`.

`status` is `live`, `paused` or `proposed`. A `proposed` workflow is one the agent drafted and nobody has approved yet. It runs on its schedule when the account's Proposed Workflows setting is Just Do It (the default), and otherwise waits until it's approved on its dashboard page or with [resume](https://revnu.com/docs/workflow-resume.md). `scheduleEcho` is how Revnu understood `scheduleText`, and `scheduleError` is set when it couldn't. `url` opens the workflow in the dashboard, where it can also be edited in chat. Reading needs only `results:read`; changing, running or deleting one needs `workflows:write`.

## Frequently asked questions

### Can a read-only token start a workflow run?

No. [Running a workflow](https://revnu.com/docs/workflow-run.md) needs `workflows:write`, which also allows editing and deleting. A reporting token with `results:read` and `leads:read` can read workflows, runs and the leads each run found.

### Which scope does this need?

`results:read`. A token without it gets `403` with `requiredScope` in the body. `GET /me` shows a token's scopes.

### Are responses cached?

No. Every response is `Cache-Control: no-store`, so what you read is current.