GoHighLevel Email Not Sending: Complete Troubleshooting Guide

Quick Diagnosis: Where Is It Failing?

Before diving deep, identify which type of email isn't sending:

Email Type	Check Location	Common Cause
Manual emails	Conversations	SMTP credentials wrong
Workflow emails	Automation history	Workflow not triggered
Campaign emails	Marketing > Emails	Domain not verified
All emails	Email Services	SMTP connection failed

If your emails are sending but landing in spam instead, see GHL emails going to spam. For setup help, see our SMTP setup guide.

Check 1: SMTP Configuration Status

Go to Settings > Email Services and find your domain.

What to Look For

• Red X marks: DNS records not verified
• Yellow warnings: Partial configuration
• Green checks: Everything configured correctly

If you see red indicators, your DNS records aren't published or propagated. This stops all sending.

Verify Each Record

GHL requires:

• SPF record on your domain
• DKIM record (usually a CNAME or TXT at a subdomain)
• Tracking domain for click/open tracking

Click on each and verify the exact record exists in your DNS.

Practitioner note: DNS propagation takes up to 48 hours, but most providers propagate within 15 minutes. If records still show red after an hour, the values are probably wrong—double-check for typos.

Check 2: SMTP Credentials

If using custom SMTP (Mailgun, SendGrid, AWS SES, etc.), verify your credentials are correct.

Where to Find SMTP Settings

Mailgun:

• SMTP hostname: smtp.mailgun.org
• Port: 587
• Username: Full SMTP username (not API key)
• Password: SMTP password (not API key)

SendGrid:

• SMTP hostname: smtp.sendgrid.net
• Port: 587
• Username: apikey (literal text)
• Password: Your API key

AWS SES:

• SMTP hostname: email-smtp.{region}.amazonaws.com
• Port: 587
• Username: SMTP username from IAM
• Password: SMTP password from IAM

Test Credentials

Send a test email from GHL. If it fails, log into your ESP dashboard and check:

1. Is the account active?
2. Is the domain verified in the ESP?
3. Are there any error logs showing the rejected connection?

Practitioner note: The most common credential issue I see: using API keys where SMTP credentials are needed. SendGrid uses your API key as the password, but Mailgun uses separate SMTP credentials—they're not the same as API keys.

Check 3: Domain Verification in ESP

Your domain must be verified in both GHL and your ESP.

Mailgun Domain Status

1. Log into Mailgun
2. Go to Sending > Domains
3. Click your domain
4. Check DNS verification status

If Mailgun shows "Unverified," emails won't send even if GHL shows green.

SendGrid Domain Status

1. Log into SendGrid
2. Go to Settings > Sender Authentication
3. Check Domain Authentication status

Both SPF and DKIM must show "Verified."

Check 4: Sending Limits

Each ESP has sending limits, and GHL adds its own layer.

ESP Limits

Provider	Default Limit	How to Increase
Mailgun	Sandbox: 300/day	Verify payment method, exit sandbox
SendGrid	Free: 100/day	Upgrade plan
AWS SES	Sandbox: 200/day	Request production access

GHL Limits

• LC Email: Sub-account limits set by agency
• Custom SMTP: Limited by your plan tier
• Workflow emails: May have daily caps in automation settings

Check your ESP dashboard for "limit reached" messages.

Check 5: LC Email Specific Issues

If using GoHighLevel's built-in LC Email:

Sub-Account Email Not Enabled

The agency must enable email for each sub-account:

1. Agency view > Sub-Accounts
2. Select the sub-account
3. Check email service is enabled

LC Email Daily Limits

LC Email has built-in limits based on domain age and reputation:

• New domains: Limited to 50-100/day
• Established domains: Higher limits

These limits aren't clearly documented—watch for "limit reached" errors in logs.

LC Email Service Outages

LC Email has occasional service issues. Check:

• GHL status page
• GHL community forums
• Your agency's support channel

Check 6: Workflow and Automation Issues

If only automated emails aren't sending:

Workflow Not Published

Unpublished workflows don't run. Edit the workflow and check if it says "Draft" or "Published."

Trigger Not Firing

The workflow trigger may not be matching:

• Form submission requires the exact form
• Tag triggers need the exact tag name
• Pipeline triggers need proper stage configuration

Check the contact's activity log—if they don't show entering the workflow, the trigger didn't fire.

Email Action Misconfigured

The email action within the workflow may have issues:

• "From" email not configured
• Template has errors
• Conditional logic blocking send

Click into the email action and verify all fields are complete.

Contact Suppressed

Contacts can be blocked from receiving email:

• Unsubscribed from all email
• Marked as spam/complained
• Hard bounced previously
• Manually suppressed

Check the contact record for suppression status.

Practitioner note: I've seen agencies spend hours debugging workflows when the contact was simply unsubscribed. Always check the contact's email status before diving into workflow logic.

Check 7: Queue Backlogs

GHL queues emails before sending, and large queues can create delays.

Signs of Queue Issues

• Emails show "Queued" for hours
• Bulk campaigns take forever to complete
• Inconsistent send times

What Causes Queue Backlogs

1. Large campaign volumes
2. GHL's internal throttling (documented throttling issues)
3. SMTP connection timeouts
4. Server-side delays

How to Check

There's no direct queue visibility in GHL. Monitor:

• Email logs for "sent" timestamps
• ESP dashboard for received emails
• Gap between "queued" and "delivered" times

The Troubleshooting Checklist

Run through systematically:

1. Email Services shows all green checks
2. SMTP credentials are correct (test in ESP)
3. Domain verified in both GHL and ESP
4. ESP account is active and funded
5. Sending limits not reached
6. Workflow is published (for automated emails)
7. Contact is not suppressed
8. Test email arrives to personal inbox

When Nothing Works

If you've verified everything above and emails still won't send:

Reset SMTP Connection

1. Remove the SMTP configuration in GHL
2. Re-add it with fresh credentials
3. Wait for DNS verification
4. Test again

Try a Different ESP

If one ESP consistently fails, test with another:

• Create free Mailgun account
• Configure in GHL
• Test sending

If the new ESP works, the problem was ESP-specific.

Contact Support

GHL support can see server-side logs you can't:

• Open a support ticket with specific details
• Include affected contact IDs
• Include timestamps of failed sends
• Attach screenshots of your configuration

Preventing Future Issues

Once emails are flowing:

1. Monitor your ESP dashboard — Set up alerts for failures
2. Test regularly — Send weekly test emails to verify the chain works
3. Document your configuration — SMTP credentials, DNS records, ESP account details
4. Watch sending limits — Plan campaigns around your limits

If email deliverability problems are blocking your business and you need expert diagnosis, schedule a consultation. I'll identify exactly where the failure is happening and get your emails flowing.

Sources

• GoHighLevel: Email Services Documentation
• Mailgun: SMTP Credentials
• SendGrid: SMTP Integration
• AWS SES: SMTP Credentials

---

v1.0 · March 2026