automations

Call automations.propose_webhook_token

'rotate that webhook token', 'give me a new token for the Zapier trigger' — replace the inbound webhook token of one webhook-triggered automation in this workspace, named by its definition_id (automations.list gives it). It answers in two calls: without confirmation_id it proposes, says whether a token exists and whether the automation is live, and changes nothing; the same call again with that confirmation_id, on a member's own API key, rotates it and returns the new token ONCE, in that answer — store it then, nothing can show it again, and every sender on the old token is refused from that moment. Needs an account admin's key. With intent mint it issues an automation's FIRST token the same way. Not for shutting a webhook off — that is automations.revoke_webhook_token.

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

Request

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

intent'mint' | 'rotate' required

mint for an automation that has no token yet; rotate to replace a live one (every existing sender stops working the moment it is rotated).

confirmation_idstring uuid

Omit to propose: the first call says what would happen, returns a confirmation_id and changes nothing. To go ahead, send the same arguments again with that confirmation_id, on a member's own API key; a service account's key can propose but never confirm.

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