EMS

Email Send

Conversations & Messaging · Intermediate · Updated March 2026

Send emails through GHL with HTML content, attachments, CC/BCC, and custom from addresses. Manage email threads within the conversation timeline.

Email remains the workhorse of client communication. Proposals, follow-ups, appointment confirmations, reports — all of it flows through email. Sending emails through MCP means you can trigger personalized emails from external events, build custom email sequences outside the workflow builder, and integrate GHL email sending into larger automation pipelines that span multiple systems.

What This MCP Tool Does

Send outbound emails to contacts with full HTML body support, file attachments, CC/BCC recipients, and custom from addresses. Schedule emails for future delivery and cancel scheduled sends. Retrieve email details including open and click tracking. All emails appear in the contact’s unified conversation timeline.

Endpoint Reference

Send an email: POST /conversations/messages Set the message type to “Email” and include the HTML body, subject line, and optional attachments. The email is sent through GHL’s email infrastructure.

Get email details: GET /messages/email/{emailId} Retrieve the full email including headers, body, and tracking data.

Schedule an email: Include scheduling parameters to queue the email for future delivery.

Cancel a scheduled email: Cancel a queued email before it’s sent.

Authentication

Requires a Private Integration Token (PIT) with the conversations scope enabled. The location must have email sending configured (either GHL’s built-in email or a connected email service).

Key Parameters

type — set to “Email”
contactId — the recipient contact’s ID
subject — email subject line
html — HTML body content
attachments — array of file attachment URLs
emailFrom — custom from address (must be a verified sender)
cc — array of CC recipient email addresses
bcc — array of BCC recipient email addresses
conversationId — send within an existing conversation thread

Important Notes

HTML content is fully supported, so you can send rich, designed emails. However, emails sent via MCP don’t use GHL’s email template builder. You’re providing raw HTML, which means you’re responsible for responsive design and email client compatibility.

The emailFrom address must be a verified sending domain or address in the location’s email configuration. Sending from an unverified address will fail.

Email deliverability depends on your sending domain’s reputation. Use Email Verification to validate recipient addresses before sending, especially for cold or re-engagement emails.

Emails sent via MCP count against GHL’s email sending limits and billing, just like emails sent through campaigns or workflows.

Common Questions

Can I send emails with rich HTML formatting? Yes. The html parameter accepts full HTML. Build your email template externally and pass the rendered HTML to MCP.

Do opens and clicks get tracked? Yes. GHL’s tracking pixels are injected automatically. Open and click data is available through the email details endpoint and in the contact’s activity timeline.

Can I use GHL email templates through MCP? Not directly through the send endpoint. However, you can retrieve template HTML via Email Template CRUD and then use that HTML in your send call.

What’s the maximum attachment size? GHL’s email attachment limits apply. Generally, keep total attachment size under 10MB for reliable delivery.

SMS Operations — Text messaging through the same conversation system
Conversation CRUD — Manage the conversation threads emails live in
Email Template CRUD — Create and retrieve reusable email templates
Email Verification — Validate addresses before sending
Message Manager — Retrieve and manage sent email records