{"slug":"gmail-smtp-shared-agency-email","title":"Gmail SMTP Setup for Shared Agency Email in GHL","tags":["email","smtp","gmail","ghl","infrastructure"],"agent_summary":"How to set up a shared Gmail SMTP email (hello@domain) for agency use in GoHighLevel, bypassing GHL's one-Google-account limitation with aliases.","trigger_phrases":["gmail smtp go high level","shared agency email ghl","ghl email setup smtp","app password gmail ghl","one google account ghl limitation","agency email configuration"],"runnable":true,"markdown":"## Gmail SMTP for Shared Agency Email in GHL\n\n### The Problem\nGoHighLevel only allows ONE Google account natively per location. With multiple team members, you need a workaround.\n\n### The Solution\nUse a shared email (e.g., hello@ironautomations.com) via Gmail SMTP, not GHL's native email.\n\n### Setup Steps\n1. **Create shared Gmail account** (e.g., hello@yourdomain.com)\n2. **Enable 2FA** on the Google account\n3. **Generate App Password:**\n - Go to Google Account → Security → App Passwords\n - Create a new app password\n - Copy the 16-character password\n4. **Configure in GHL:**\n - Go to Settings → Email Services → SMTP\n - SMTP Server: smtp.gmail.com\n - Port: 587 (TLS) or 465 (SSL)\n - Username: hello@yourdomain.com\n - Password: [App Password from step 3]\n5. **Set From Name:** Use brand name (e.g., \"Iron Automations\") or team member name depending on workflow\n6. **Use aliases** for different team members within the same account\n\n### Why This Over GHL Native\n- Bypasses one-Google-account limitation\n- Makes the email \"evergreen\" — not tied to one person\n- Team members can use themselves as aliases per workflow\n- Account uses brand logo, not personal photo\n- Dedicated sending domain for better deliverability\n\n### Common Issues\n- **App passwords disappear:** If you switch accounts or change security settings, app passwords may be deleted. Regenerate them.\n- **From email showing wrong address:** Check workflow email action — the \"from email\" field may be pulling from calendar configuration or staff settings rather than SMTP config\n- **Variables not resolving in test emails:** Custom variables like `{{appointment.user.first_name}}` may not populate in test mode — only resolve with live contacts\n\n### Dedicated Sending Domain\nSet up a dedicated sending domain for your agency email to improve deliverability. This is separate from the SMTP configuration and handled in GHL email settings.\n","html":"

Gmail SMTP for Shared Agency Email in GHL

\n

The Problem

\n

GoHighLevel only allows ONE Google account natively per location. With multiple team members, you need a workaround.

\n

The Solution

\n

Use a shared email (e.g., hello@ironautomations.com) via Gmail SMTP, not GHL's native email.

\n

Setup Steps

\n
    \n
  1. Create shared Gmail account (e.g., hello@yourdomain.com)
    2. \n
  2. Enable 2FA on the Google account
    3. \n
  3. Generate App Password:\n\n
    4. \n
  4. Configure in GHL:\n\n
    5. \n
  5. Set From Name: Use brand name (e.g., \"Iron Automations\") or team member name depending on workflow
    6. \n
  6. Use aliases for different team members within the same account
    7. \n
\n

Why This Over GHL Native

\n\n

Common Issues

\n\n

Dedicated Sending Domain

\n

Set up a dedicated sending domain for your agency email to improve deliverability. This is separate from the SMTP configuration and handled in GHL email settings.

\n"}