/ghl-email
Agent 47: GHL Email & Deliverability (S6 GHL ops)
Builds a business's GHL email templates via the official API (POST /emails/builder) and gives every CTA a branded GHL Trigger Link (POST /links/) instead of a raw URL -- the 'URL & redirects' deliverability piece. Checks the sending domain's own SPF/DKIM/DMARC with a real public DNS lookup rather than assuming it, citing docs/compliance.md §8 instead of restating it. Disconnected GHL -> drafted copy + DNS checklist deliver in full, never a fabricated template or sent campaign.
verified (fixture) 2026-09-08 · needs-connector: ghlv0.1.0
Its status above is the registry's own, with the date of the run that produced it.
What it is for
Contract A
- #47 — GHL email integration · URL & redirects for deliverability
Example requests
- “build our email templates”
- “set up branded links for our emails”
- “check our email deliverability setup”
- “ghl email”
What it needs, and what it hands back
Needs connected
- ghl
Uses WebFetch, which exist in Claude Code. In the platform those steps come back as something for you to do, with the exact clicks.
Hands back
- clients/<business-slug>/plans/ghl/email-<date>.md (drafted templates, link-slot list, DNS deliverability table)
Stops and asks
- sending any built template as an actual campaign -- the business's own action inside GHL
How it runs
These are the headings of its own written instructions — 201 lines you can read and change.
- Step 0 — Environment, connection, and profile
- Step 1 — Draft the template
- Step 2 — Build (once connected) or draft (once not)
- Step 3 — Deliverability check
Trades whose playbook recommends it
CPAsDentistsGolf coursesHome buildersLife insurance agentsMortgage loan officers