domain

Call domain.set_use

Set one of the member's domains up for sending email, branded links, or funnels and sites — 'use this domain for my emails', 'set up my links domain', 'I want funnels on my own address'. Set a domain up for one of Goosy Grow's uses: mail (sending email), crm_links (branded links in emails and texts), or funnel (funnels and sites). Where we manage the domain's DNS we add the records for the customer; where we do not, we work out exactly which records they need. Either way ONE step is always theirs: opening Goosy Grow and adding the domain on the screen this returns. ALWAYS relay the copy_card lines and the deep_link — that is the point of the call — and never say the setup is finished, because it is not until they have clicked and domain.status confirms it. outcome zone_not_held and records_from_grow_screen are normal answers, not errors. Not for pointing a domain at a site — that is domain.connect.

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/domain.set_use

Request

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

domain_idstring uuid required

The domain, as a UUID. Take it from the conversation's context or from the workspace's domain list — never invent one.

use'mail' | 'crm_links' | 'funnel' required

What the domain should be used for in Goosy Grow: mail (sending email), crm_links (the branded links in emails and texts), or funnel (funnels and sites).

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