contact

Call contact.link

Attach an email, phone number or handle you hold to the right customer — 'that's the same person as this lead', 'add this email to their record', 'this number belongs to them'. Attach a key you hold from a conversation — an email, a phone number, a Messenger id — to a customer, or take one off again. Calling it shows the operator an approve card naming the change first, and nothing is written unless they approve it themselves. You cannot approve it for them, and never pass confirm_token. Keys are matched exactly, never on a likeness, and one that already belongs to somebody else is refused rather than moved. Not for looking a customer up — that is contact.get. 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/contact.link

Request

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

contact_idstring uuid required

The customer this key belongs to. Read them with contact.get first — never a guess at who a key belongs to.

identity_kind'email' | 'phone' | 'meta_psid' | 'ig_id' | 'ghl_contact_id' | 'gbp_reviewer' required

Which kind of key this is: an email address, a phone number, a Messenger id (meta_psid), an Instagram id (ig_id), a CRM record id (ghl_contact_id), or a Google reviewer id.

identity_valuestring required

The key exactly as you observed it. It is normalised before it is looked up, so capitals in an address are fine — but a phone number without its country code cannot be matched and will be refused rather than guessed at.

identity_scopestring

The Meta PAGE id the key was seen on. REQUIRED for meta_psid and ig_id — those ids are only unique within one page, so without it nothing can be matched. Leave it out for every other kind.

action'link' | 'unlink' required

link attaches the key to that customer; unlink takes it off again. Both are recorded on their history.

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.