---
title: "Call automations.list"
method: POST
path: "/api/v1/tools/automations.list"
tags: ["automations"]
---

# Call automations.list

`POST /api/v1/tools/automations.list`

## Request

- Base URL: `https://app.goosybear.ai`
- URL: `https://app.goosybear.ai/api/v1/tools/automations.list`
- Auth: HTTP bearer

'what automations do we have?', 'is that automation still on?' — list this workspace's automations, the same rows its Automations board shows: each one's definition id, name, status (Running, Needs a look, Paused or Not scheduled), the project it lives in, its schedule in words, when it last ran and when it fires next, plus a count per status. It answers one page — as many automations as fit, in the board's order — and `counts` on every page covers every automation, not only the rows shown; when `next_cursor` comes back, call again with it as `cursor` for the rest, and `limit` asks for fewer. It changes nothing. Not for whether one automation's inbound webhook is set up — that is `automations.webhook_token_status`.

Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with `workspace_ambiguous` and lists the choices — offer them, never pick one.

## Headers

- `x-request-id` string

## Request body

- object
  - `limit` integer: At most this many automations on the page. Omit it to get as many as fit in one answer.
  - `cursor` string: Where to continue: pass the `next_cursor` from the previous page, with the same filters. Omit it for the first page.
  - `name` string: Only the automations whose name contains this, ignoring case. Omit it to list them all.
  - `workspace` string: Which workspace to run in — its slug. Omit to use your default. With more than one reachable workspace and no default, the call is refused and the choices are listed.

## Response `200`

The call was admitted and dispatched. `ok` says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.

- union
  - object: The tool ran and answered.
    - `ok` true, required
    - `automations` object[], required
      - `definition_id` string, nullable, required
      - `board_id` string, required
      - `name` string, required
      - `status` string, required
      - `lives_in` string, nullable, required
      - `schedule` string, required
      - `last_run_at` string, nullable, required
      - `next_fire_at` string, nullable, required
    - `counts` object, required
      - `total` integer, required
      - `running` integer, required
      - `paused` integer, required
      - `needs_a_look` integer, required
      - `not_scheduled` integer, required
    - `next_cursor` string: Present when there is another page: pass it back as `cursor` to read it. Absent on the last page.
    - `next` string: What to call next to read, change or fix one of these automations.
    - `workspace` string, required: The slug of the workspace this call ran in.
    - `working_in` object, required: Which workspace this call ran in, and how that was decided. Present on every workspace-scoped result.
      - `label` string, required: The chip words — e.g. "working in: Acme Main".
      - `note` string, required: Why this workspace — e.g. "your default", "this call only".
      - `workspace` string, required: The resolved workspace's slug.
      - `source` 'call-override' | 'key-pin' | 'stored-default' | 'sole-reachable', required: Which rung of the R7 precedence resolved the workspace.
  - ToolRefusal: A call that was admitted and dispatched, and did not succeed.
    - `ok` false, required
    - `code` string, required: The typed reason — e.g. `workspace_ambiguous`, `invalid_arguments`, or the tool's own failure code.
    - `message` string, required: A sentence a person can act on.
    - `workspaces` string[]: On a workspace refusal: the slugs this key may pass as `workspace`.
    - `issues` object[]: On `invalid_arguments`: which fields failed, and why.
      - `path` string, required
      - `message` string, required
    - `path` string: On an authoring refusal: where in your call's input it points, e.g. `steps.<key>.params.<field>`.
    - `fix` string: On an authoring refusal: the change to your call that would pass.
    - `instruction` string: On an authoring refusal: what to do next with it.

## Other responses

- `400`: The request could not be used: the body is present but not a JSON object (`tenant_api.malformed_body`); it is a top-level array carrying more messages than this endpoint accepts (`tenant_mcp.batch_too_large`); or the `Idempotency-Key` header is malformed (`tenant_api.idempotency_key_invalid`), disagrees with the body's `idempotency_key` (`tenant_api.idempotency_key_conflict`), or was sent to an action that cannot replay a retry (`tenant_api.idempotency_unsupported`). Nothing ran.
- `401`: No bearer credential, or one that did not resolve. Deliberately ONE undifferentiated answer for absent / unknown / revoked / expired, so the endpoint is never an oracle over the key space.
- `403`: The credential is good but the surface is not open to it — the platform or account API switch is off, or the holder lacks the `api.access` capability. The `code` says which.
- `404`: No such tool. The body names no tool and is identical for every unrecognised name.
- `429`: Over this key's per-minute cap. Carries `Retry-After` and `error.retry_after_seconds`.

---

[API](https://skmtc.dev/goosybear/apis/goosy-bear-api.md) · [All operations](https://skmtc.dev/goosybear/apis/goosy-bear-api/llms.txt) · [OpenAPI document](https://skmtc.dev/goosybear/apis/goosy-bear-api/revisions/6d82fb124064?raw)