items

Call items.place

Bring an existing item — a photo, video, document, file, table, email, post, site, automation — onto the canvas the member is on now, as its home; a project the member names is work.file — 'put the leads table on this canvas', 'bring the logo file into this project', 'add the welcome email here'. Any item: a site, an automation, a video or short, a post, an image or photo, a document, an uploaded file, a data table, an email or a widget. This verb finds the item itself, so call it on the ask: put the member's words for the thing in item_name, a generic name too ('the new doc', 'that photo from Friday'), for any item but a widget. Among several matches it takes the one in the project the member is on, then the exact name; otherwise it moves nothing and answers with the matches by name and place, so you can ask which. The item then lives in the project the member is on (where their new work starts when they are on none); if it lived in another project it leaves that one, because an item lives in one place. Nothing is copied or deleted, and the member can undo it. Send item_id instead only when this conversation already showed you the item's id. Not for putting it in a project the member names (work.file), or for showing the item here while it stays where it lives (work.shortcut).

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/items.place

Request

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

item_kind'site' | 'automation' | 'video' | 'post' | 'image' | 'document' | 'file' | 'table' | 'email' | 'widget' required

What it is: a site, an automation, a video (or short), a post, an image (a photo or picture), a document, an uploaded file, a data table, an email or a widget.

item_idstring uuid

Its id, only when a verb or the page already showed it to you (a project's from board.tree, a widget's from widget.list). Otherwise send item_name: never call a list just to find an id.

item_namestring

The member's words for its name, title or subject ('the latte video', 'price list', 'the Monday report automation'), a generic name included. It works for every kind but a project and a widget; the tool finds the item itself, with no read first, and when several things match the answer lists them by name and place so you can ask which.

idempotency_keystring

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

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