automations

Call automations.list

'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.

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

Headers

x-request-idstring

Your own id for this request, echoed back and recorded on the audit trail. 1–128 characters from A–Z a–z 0–9 . _ : -, starting with a letter or digit; anything else is replaced by a generated id.

Request body

limitinteger

At most this many automations on the page. Omit it to get as many as fit in one answer.

cursorstring

Where to continue: pass the next_cursor from the previous page, with the same filters. Omit it for the first page.

namestring

Only the automations whose name contains this, ignoring case. Omit it to list them all.

workspacestring

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

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.

OR

Changes

No recorded changes to this operation across all 4 revisions of this API.