Call board.attach_set
'file the week of March 2 posts under the Spring launch project', 'make Q3 retargeting campaign live in the Retargeting project' — make one project of this workspace the home of a posts set (a posts week or rotation) or an ad campaign that has no project yet. The set's posts or ads stay where they are; the project becomes the place the set opens from. A set already at home in another project is refused and left as it is, and repeating the same link changes nothing. Make the project first with projects.create if it does not exist. Not for putting a board inside a project — that is work.file.
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.
Request
- Base URL: https://app.goosybear.ai
- URL: https://app.goosybear.ai/api/v1/tools/board.attach_set
- Auth: HTTP bearer
Headers
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
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.
Changes
No recorded changes to this operation across all 5 revisions of this API.