contact

Call contact.get

Say what we know about one customer — 'who is this lead?', 'what's the story with that contact?', 'have we talked to them before?'. Read one customer's record — who they are, which ways exist to reach them, their tags, whether we may message them, and their recent history. Address them by their id, or by ONE key you already hold from the conversation (an email, a phone number, a Messenger id). It deliberately returns no addresses or phone numbers, and there is no way to list customers with it. The summary is small on purpose; ask for section timeline or notes when it says more exists. Not for writing on their record — that is contact.note.

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.get

Request

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

The customer to read, when you already have their id. Give EXACTLY ONE address: this customer id, or the identity pair (identity_kind WITH identity_value). Neither, or both together, is refused rather than guessed at.

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

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

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.

section'summary' | 'timeline' | 'notes'

Which part to read. summary (the default) is the record plus the newest few history rows and notes; timeline is the recent history only; notes is their notes only. Ask for timeline or notes when the summary says more exists.

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.