automations

Call automations.webhook_token_status

'why isn't my webhook firing?', 'is the Zapier trigger set up?' — for one webhook-triggered automation in this workspace, named by its definition id (automations.list gives it), say whether its inbound token is set up, when it was issued or last rotated, and whether the automation is published, so the endpoint would accept a call. It never returns the token, and it changes nothing. Not for listing the automations — that is automations.list.

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

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/automations.webhook_token_status
  • 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

definition_idstring uuid required

The automation's definition id — the id in its webhook URL. Read it from automations.list or the board, never invent one.

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 6 revisions of this API.