Skip to main content
GHL MCP Guide
ETM

Email Template CRUD

Content & Email · Intermediate · Updated March 2026

Create, update, retrieve, and delete email templates with HTML content, drag-and-drop builder data, or imported designs for campaigns and automations.

Email templates are the building blocks of email marketing. Every campaign, every drip sequence, every automated email uses a template. Managing templates through MCP means you can build template libraries programmatically, deploy branded templates across client locations during onboarding, and update template content from external design systems.

What This MCP Tool Does

Full CRUD on email templates. Create new templates with HTML content, list all templates in a location, update template content and settings, and delete templates no longer in use.

Endpoint Reference

Create a template: POST /marketing/emails/templates List templates: GET /marketing/emails/templates Update a template: PUT /marketing/emails/templates/{templateId} Delete a template: DELETE /marketing/emails/templates/{templateId}

Authentication

Requires a Private Integration Token (PIT) with the marketing scope enabled.

Key Parameters

  • name — template display name
  • type — template type (html, builder)
  • html — HTML content for html-type templates
  • builderVersion — for drag-and-drop builder templates

Important Notes

HTML templates give you full design control. You provide the complete HTML including responsive design, inline styles, and email client compatibility. This is the approach for programmatic template management.

Builder templates are created through GHL’s drag-and-drop editor and stored in a proprietary format. You can read them via MCP but creating new builder-format templates programmatically is complex. Stick to HTML templates for MCP-based workflows.

Template variables (personalization tokens like {{contact.first_name}}) work in HTML templates. Include them in your HTML and they’ll be replaced with actual values when the email is sent.

Templates deployed via MCP are available to campaigns, workflows, and individual sends across the location. They appear in the same template library as UI-created templates.

Common Questions

Can I deploy the same template across multiple client locations? Yes. This is an excellent agency use case. Create a branded template and deploy it to each client sub-account via MCP during onboarding.

Do templates support personalization tokens? Yes. Standard GHL merge fields work in HTML templates created through MCP.

Can I import templates from external email builders? Yes, as long as you can export the HTML. Take the HTML output from your design tool and create a template via MCP.

How do I use a template in an email send? Retrieve the template HTML via this tool, then use that HTML in your Email Send call.

Back to GHL MCP Guide