connections

Call connections.publish_local_post

Push one local post out to this workspace's Google Business Profile — 'post this update to our Google Business Profile', 'publish a local post about our sale'. Publish one local post to this workspace's Google Business Profile. It is PUBLIC — customers see it on the business's listing — so calling it raises the approval card showing the exact wording, which is the operator's confirmation, and only their approve publishes it. Check connections.business_profile_status first and do not offer this when can_publish is false. The text goes out exactly as written. Not for whether a local post can go out right now — that is connections.business_profile_status. 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/connections.publish_local_post

Request

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

Idempotency-Keystring required

Your key for this write: send the same key when you retry and the first result comes back instead of a second action. Keys are honoured for at least 24 hours. 1–200 visible ASCII characters. Replaces the idempotency_key body field, which still works until 2026-12-31; this action needs a key on one of the two, and the header is the one to send.

Request body

piece_idstring required

The content piece this post came from. It is what makes the published post reconcilable back to what the operator approved — never invent one, and never reuse another piece's id.

textstring required

The post body, exactly as the operator approved it. On a Business Profile the text IS the post — there is no caption/body split — so do not append hashtags, links or sign-offs the operator did not write.

media_urlstring nullable required

One photo or video URL, or null for a text-only post. A Business Profile local post carries at most ONE media item; a second is refused rather than dropped.

media_type'image' | 'video' nullable required

What media_url points at. Null when there is no media. Must match the asset — a mislabelled type is refused by Google, not silently corrected.

media_mime_typestring nullable required

The asset's MIME type, e.g. image/jpeg or video/mp4. Null when there is no media. Read it off the asset — never guess one to satisfy the field.

idempotency_keystring

Deprecated on REST: send the Idempotency-Key header instead. Still accepted until 2026-12-31; if both are sent they must match.

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.