ghl

Call ghl.send_email

Send ONE email to a contact through this workspace's connected CRM, using the CRM's own sending domain — 'email this contact about the offer', 'send them a follow-up email'. It puts a message in a real person's inbox and cannot be recalled, so it PREPARES the send and stops: the operator is shown the subject, the body and who it is going to on a card, and only their approve sends it. Not for this week's marketing campaign email — that is email_campaign.draft. 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/ghl.send_email

Request

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

contactIdstring required

The CRM contact id to email.

subjectstring required

The subject line.

htmlstring

HTML body. At least one of html or text is required — a send with neither is refused.

textstring

Plain-text body. At least one of html or text is required — a send with neither is refused.

fromAddressstring required

A VERIFIED sending address on the connected sub-account. Required: there is no default sender to fall back to, and an unverified address is refused by the provider.

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