inbox

Call inbox.set_channel_autonomy

Decide whether one channel's replies go out on their own or always wait for the member — 'let it reply to SMS by itself', 'I want to approve every Instagram reply', 'stop it sending without me'. Change whether ONE inbox channel sends its replies on its own or always waits for the operator. Setting a channel to send on its own removes the human tap from every future reply there. Call it on the ask: it raises the approval card showing how that channel replies now and after, which is the member's confirmation, so it can still be declined after you call it. Not for how that channel's replies sound — that is inbox.set_channel_reply_instructions. Over the API it answers in two calls: without confirmation_id it proposes — says what would happen, returns a confirmation_id and changes, spends and sends nothing; the same arguments again with that confirmation_id, on a member's own API key, do it.

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/inbox.set_channel_autonomy

Request

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

channel'email' | 'sms' | 'messenger' | 'ig_dm' | 'gbp_review' | 'fb_comment' | 'ig_comment' required

Which channel to change.

mode'suggest' | 'auto' required

suggest — every reply waits for the operator. auto — replies on this channel go out on their own.

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