GoHighLevel + Google Workspace SMTP: Limits and Gotchas

When Google Workspace SMTP Makes Sense

Google Workspace SMTP integration works for:

• Very small volume (under 100 emails/day)
• Personal follow-ups from your own address
• Testing and development environments
• Single-person operations

For higher-volume sending, use a proper SMTP provider instead — see best SMTP for GHL and GHL SMTP setup.

It does NOT work for:

• Marketing campaigns
• Bulk transactional email
• Automation sequences at scale
• Agency client work

Practitioner note: Every few months I get a panicked call from an agency whose GHL emails suddenly stopped. They hit Google's daily limit or got flagged for bulk sending. Google Workspace isn't built for this. Use a real ESP.

Google Workspace Sending Limits

Account Type	Daily Limit	Notes
Google Workspace	2,000/day	Per user account
Personal Gmail	500/day	Per account
Google Workspace (trial)	500/day	Until upgraded

These are hard limits. When you hit them:

• Email stops sending entirely
• No warning until it fails
• Limit resets after 24 hours

Per-Recipient Counts

Google counts recipients, not emails:

• 1 email to 10 people = 10 toward limit
• BCC recipients count separately
• Auto-replies count

A 500-person campaign uses your entire daily allowance.

Setting Up Google Workspace SMTP in GHL

If you understand the limits and want to proceed:

Step 1: Enable 2FA

Google requires 2-factor authentication for SMTP:

1. Go to myaccount.google.com
2. Security > 2-Step Verification
3. Enable and configure

Step 2: Create App Password

You cannot use your regular password for SMTP:

1. Go to myaccount.google.com/apppasswords
2. Select "Mail" and "Windows Computer" (or any device)
3. Click Generate
4. Copy the 16-character password

This is your SMTP password.

Step 3: Configure in GoHighLevel

1. Go to Settings > Email Services
2. Click Add SMTP
3. Enter settings:

Field	Value
SMTP Server	smtp.gmail.com
Port	587
Username	[email protected]
Password	App Password (16 chars, no spaces)
Encryption	TLS/STARTTLS

Alternative: SMTP Relay

For Google Workspace (not personal Gmail), you can use SMTP relay:

Server: smtp-relay.gmail.com Port: 587

This requires configuring the relay in Google Admin Console:

1. Go to admin.google.com
2. Apps > Google Workspace > Gmail > Routing
3. Configure SMTP relay service
4. Add GHL's sending IP if required

Authentication and DNS

SPF Configuration

Add Google to your SPF record:

v=spf1 include:_spf.google.com ~all

If you have existing SPF, add include:_spf.google.com to it.

DKIM

Google Workspace handles DKIM automatically when sending through their servers. Verify in:

1. Admin Console > Apps > Google Workspace > Gmail
2. Authenticate email
3. Generate new DKIM key if needed

DMARC

Add DMARC record:

_dmarc.yourdomain.com. TXT "v=DMARC1; p=none; rua=mailto:[email protected]"

Common Problems

"Username and Password Not Accepted"

Causes:

• Using regular password instead of App Password
• 2FA not enabled
• App Password copied with spaces
• Wrong email address

Fix: Generate new App Password with 2FA enabled.

"Daily User Sending Limit Exceeded"

You hit the 2,000 (or 500) email limit.

Fix: Wait 24 hours or use a real ESP.

"550-5.4.5 Daily SMTP Relay Limit Exceeded"

Relay limit reached.

Fix: Same as above—wait or switch providers.

"Authentication Failed"

Causes:

• "Less secure app access" needed (legacy accounts)
• App Password not generated correctly
• Google security blocking the connection

Fix: Verify 2FA and App Password setup.

"Message Blocked Due to Spam"

Google detected bulk sending patterns.

Causes:

• Sending to large lists
• High bounce rate
• Content triggers
• Recipients marking as spam

Fix: This may result in temporary account restriction. Switch to proper ESP.

Why You Shouldn't Use Google Workspace SMTP

The Real Problems

1. Limits are too low — 2,000/day caps even small marketing
2. No dedicated features — No bounce handling, no analytics, no reputation management
3. Account risk — Google may suspend for bulk patterns
4. No scalability — Can't grow without switching
5. Shared reputation — Gmail infrastructure, not isolated

What Google Says

Google's own documentation states SMTP relay is for:

• "Sending messages from printers and scanners"
• "Application-generated messages"
• "Low-volume business email"

It's explicitly not for marketing or bulk email.

Practitioner note: I've seen Google suspend Workspace accounts for sending 500 marketing emails. They monitor patterns, not just volume. Bulk-looking traffic from an account meant for business email triggers reviews.

The Right Alternative

For any real volume with GHL, use:

Provider	Cost	Daily Limit
Mailgun	~$35/month	50K+
SendGrid	~$20/month	40K
AWS SES	~$0.10/1K	Unlimited

See our best SMTP for GHL guide.

When Google Workspace Actually Works

Keep GWS SMTP for:

• Personal replies: Responding to individuals from your actual inbox
• Testing: Verifying email workflows before going live
• Tiny operations: Under 50 emails/day consistently

For these cases, the simplicity of using your existing email is convenient.

Hybrid Approach

Some agencies use both:

Google Workspace for:

• Manual 1:1 emails
• Personal follow-ups
• Calendar invites

Dedicated ESP for:

• Marketing campaigns
• Automated sequences
• Bulk transactional

This requires managing two SMTP configurations in GHL but matches the right tool to each job.

The Honest Recommendation

Don't use Google Workspace SMTP for GoHighLevel email beyond testing.

The limits are too restrictive, the risk to your Google account is real, and proper ESPs cost $15-35/month while providing:

• 10x-100x the volume
• Real deliverability features
• Dedicated reputation
• Proper analytics

If you're trying to save money by avoiding an ESP, you'll spend more time dealing with problems than the $20/month saves.

If you need help choosing the right email infrastructure for your GHL setup, schedule a consultation. I'll recommend the optimal approach based on your actual volume and use cases.

Sources

• Google: SMTP Relay Service
• Google: Sending Limits
• Google: App Passwords

---

v1.0 · March 2026