page

Call page.schedule_publish

Put a site live at a chosen time instead of now — 'publish it on Monday morning', 'schedule this to go live at 9am', 'put it up next Tuesday'. Schedule a page to publish at a chosen time. Send at as an ISO-8601 timestamp WITH its UTC offset, resolved against the member's own timezone. It must be at least five minutes away and within the next year. This is a public, consequential act. Call it on the ask: it raises the approval card showing the page's name, its address and the time being committed to, which is the member's confirmation. Never say a page is scheduled unless the result says it is. If replaced is true, say you moved an existing schedule rather than adding a second one. Not for publishing right now — that is page.publish. 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/page.schedule_publish

Request

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

site_idstring uuid

The SITE the member means, as a site UUID. You are NOT shown the id of the site open on screen — it never appears in your context, so there is nothing to copy. When they say 'this site', 'the site I'm looking at', or name no site at all, they mean that on-screen site, and the way to reach it is: where this schema leaves site_id OPTIONAL, OMIT IT ENTIRELY — that is the primary path, not a fallback, and the turn's own surface resolves it server-side. Where the schema REQUIRES it, call page.list with name set to the site they named — it returns that one site's id, or the candidates to ask them about. Never pass a board, board-item, thread or any other id that merely happens to be nearby in the conversation — those name different objects and will be refused — and never one you composed.

atstring required

When to publish, as an ISO-8601 timestamp that INCLUDES the UTC offset (for example 2026-09-08T09:00:00-06:00). Never send a bare local time — it would be read as UTC and the page would publish at the wrong hour. Resolve the operator's words against their timezone and state the time back to them in their own words. It must be at least five minutes from now and within the next year.

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.