GoHighLevel Gmail & Outlook Email Sync: Setup (2026)
By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 3 October 2026 · 9 min read
Some links below are affiliate links — if you sign up through them, HL Growth Partner may earn a commission at no extra cost to you. It never changes what we recommend.
The GoHighLevel Gmail integration and Outlook email sync let each user connect their own mailbox so one-to-one emails with contacts flow two ways between the inbox and HighLevel Conversations. If you have ever asked how to connect Gmail to HighLevel without breaking your bulk email setup, this is the guide.
We will cover what actually syncs, what does not, how it differs from your LC Email or Mailgun sending domain, the privacy questions Australian businesses should ask before switching it on, and how to fix the usual problems when emails go missing.
Quick Facts
| Where to connect | Settings > My Profile > Email (2-way sync) |
| Providers | Gmail (including Google Workspace accounts) and Outlook (Microsoft) |
| Connection level | Per user, from each user's own profile |
| Inbound capture | Emails from existing contacts only; no cold inbound from unknown senders |
| History | Emails from before the connection are not backfilled |
| Gmail sending cap | Approximately 500 individual emails per day, per HighLevel's Gmail sync article |
| Bulk and workflow email | Still sent through the sub-account's email provider (LC Email, Mailgun or SMTP) |
What GoHighLevel Gmail and Outlook email sync actually does
Two-way sync creates an authorised connection between a user's personal mailbox and the CRM. Emails you send to a contact from Conversations go out through your real Gmail or Outlook account, and appear in your Sent folder as normal.
When that contact replies, the reply lands in your inbox and also in the contact's conversation thread inside HighLevel. Incoming emails from existing contacts are pulled into Conversations automatically, along with subsequent messages in the thread.
The point is a single, complete record of every 1:1 email conversation with a client, without forwarding, BCC tricks or copy-pasting into notes.
What syncs
- Individual emails you send to a contact from Conversations or the contact record.
- Replies to those emails, threaded under the contact.
- New emails that arrive in your inbox from people who already exist as contacts in the sub-account.
What does not sync
- Cold inbound email from senders who are not yet contacts. HighLevel's documentation is explicit that two-way sync captures existing contacts only.
- Historical email. Messages from before you connected the mailbox are not backfilled.
- Emails from contacts who are also users in the sub-account. HighLevel excludes these because they may contain confidential internal information.
- Bulk and workflow email. These still go out through the sub-account's configured provider, not your mailbox.
That last point matters more than most people realise, so let us unpack it.
Two-way sync vs LC Email and Mailgun sending domains
HighLevel effectively runs two email lanes. One is the personal lane (your Gmail or Outlook mailbox), and the other is the sub-account lane (LC Email, Mailgun or a custom SMTP provider) that handles campaigns and automation.
According to HighLevel's Gmail sync help article (2026), individual emails are sent directly from Gmail when 2-way sync is active for that user, while bulk email continues to send from the sub-account level provider. Automated workflow emails are also dispatched from the sub-account provider, not from the synced mailbox.
| Feature | Gmail / Outlook 2-way sync | LC Email / Mailgun / SMTP |
|---|---|---|
| Purpose | 1:1 conversations with contacts | Campaigns, bulk sends, workflow emails |
| Connected by | Each user, in My Profile | Admin, at sub-account level |
| Sends from | The user's real mailbox | Your dedicated sending domain |
| Appears in your Sent folder | Yes | No |
| Daily volume | Bound by the mailbox provider (Gmail approx. 500 per day, per HighLevel) | Bound by your sending provider and domain reputation |
| Inbound replies | Synced for existing contacts | Handled by the provider's inbound setup |
| Deliverability setup | Inherits your Google or Microsoft mailbox setup | Needs SPF, DKIM and DMARC on the sending domain |
Do not treat 2-way sync as a replacement for a proper sending domain. If your newsletters and nurture sequences are not set up correctly, sort that first with our Mailgun and LC Email deliverability setup guide.
HighLevel's sending priority rules also shift once sync is on. When you send a one-off email from the Conversations tab, the From address shows your integrated mailbox instead of your default user email.
How to connect Gmail to HighLevel (and Outlook): setup steps
The connection lives in each user's profile, not in the agency settings. Every team member who handles client email needs to complete these steps themselves while logged in as their own user.
Before you start
- Confirm the user has a HighLevel user account in the right sub-account and can edit their own profile.
- Check the client or prospect already exists as a contact, otherwise their emails will not sync.
- If you use Google Workspace or Microsoft 365, check whether your IT admin restricts third-party app access, as that can block or later revoke the authorisation.
Connection steps
- Log in to the sub-account and open Settings.
- Go to My Profile and scroll to the Email (2-way sync) section.
- Choose Gmail or Outlook and click Connect.
- Sign in with the mailbox you actually use for client email, then review and allow every permission requested.
- Back in HighLevel, send a test email to a contact from Conversations and confirm it appears in your mailbox's Sent folder.
- For testing, use a contact record set to a second mailbox you control, reply from that mailbox and check the reply lands in the HighLevel thread.
HighLevel's Connect Personal Inbox guide walks through the same path with screenshots, and it is worth bookmarking for your team.
If you are connecting calendars at the same time, the authorisation flows are similar but separate. Our Google Calendar and Outlook sync guide covers that side.
Not on HighLevel yet? Start with a free 30-day trial here — long enough to build everything in this guide before you pay a cent.
Email sync privacy for Australian businesses: who can see synced emails
This is the question we get most from Australian clinics, accountants and consultancies. Once an email syncs into Conversations, it is stored against the contact in the CRM, and other users may be able to see it.
How visibility works
Visibility follows user roles and permissions rather than who connected the mailbox. HighLevel's user roles documentation states that admins with full access see all conversations in the sub-account.
Users restricted with the Only Assigned Data setting see conversations only where they are the contact owner or a follower. That is the main lever you have for limiting who reads synced client email.
If you have not reviewed roles in a while, our guide to sub-account permissions and user roles shows how to set this up cleanly before you turn sync on.
Practical privacy checks
- Decide which mailboxes should be synced at all. A director's personal inbox with HR or legal threads is often a poor candidate.
- Tell staff that synced client emails become part of the business record and may be visible to colleagues.
- Update your privacy policy or collection notice if you now store client email content in your CRM, and take advice on your obligations under the Privacy Act 1988 and the Australian Privacy Principles where they apply to you.
- Use Only Assigned Data for contractors, VAs and junior staff who do not need every thread.
- Remember that contact-to-user emails are excluded by design, but email from clients about sensitive matters will still sync.
Our default recommendation: sync shared role inboxes and client-facing staff mailboxes, and keep leadership inboxes out unless there is a clear reason.
Gmail and Outlook sync troubleshooting
Most problems fall into four buckets: permissions, missing contacts, duplicates and expectations about history. Work through them in this order.
"Insufficient Permission for 2-Way Sync" errors and disconnects
HighLevel's insufficient permission troubleshooting article lists the usual causes. They include revoked Google or Microsoft permissions, a changed mailbox password, an organisation security policy invalidating the token, or the provider asking for permissions to be granted again after a security update.
The fix is to click Reconnect in the Email (2-way sync) section, or remove and reconnect the mailbox. Sign in with the correct account and allow every requested permission, because partial permissions stop the sync working.
Emails not showing in Conversations
Nine times out of ten, the sender is not a contact yet. Two-way sync does not create contacts from cold inbound email, so create the contact first, or capture them through a form, and future emails will sync.
If you need unknown senders captured automatically, that is a job for an inbound email setup on your sending domain, combined with the Inbound Email workflow trigger, rather than personal inbox sync.
Emails landing on the wrong contact
When the same email address sits on two contact records, threads can split or attach to the record you did not expect. Clean up with our guide to merging and preventing duplicate contacts, then check the thread again.
Old emails missing
This is expected behaviour. Emails sent or received before the connection are not backfilled, so the record starts from the day the mailbox was connected.
Gmail sends failing late in the day
If one-off emails start failing for a heavy Gmail user, check volume. HighLevel's Gmail sync article (2026) notes that Gmail supports only about 500 emails per day, and emails beyond that will be unsuccessful.
Common mistakes to avoid
- Connecting the wrong mailbox, such as a personal Gmail instead of the Google Workspace address clients actually email.
- Expecting synced inboxes to send workflow or bulk emails, then wondering why nurture emails still come from the sending domain.
- Turning on sync before contacts are imported, so early client emails never appear in Conversations.
- Leaving every user on full access, so the whole team can read every synced client thread.
- Ignoring the Reconnect prompt after a password change, and losing days of client replies from the CRM record.
- Allowing only some of the requested permissions during authorisation, which leaves sync half working.
If you want your team's Gmail or Outlook inboxes, sending domain and user permissions set up properly in one pass, book a strategy call with the HL Growth Partner team.
Or if you just need the software first: grab the 30-day HighLevel trial and book us when you're ready to scale it.
Frequently asked questions
Where do I connect Gmail or Outlook in GoHighLevel?
Go to Settings, then My Profile, and scroll to the Email (2-way sync) section. Choose Gmail or Outlook, click Connect and allow the requested permissions. Each user connects their own mailbox from their own profile.
Does GoHighLevel two-way email sync capture emails from new leads?
No. Two-way sync only captures emails from people who already exist as contacts in the sub-account. Cold inbound email from unknown senders needs a separate inbound email setup on your sending domain.
Will my old emails import into HighLevel when I connect my inbox?
No. Emails from before the connection was made are not backfilled. The synced history starts from the day you connect the mailbox.
Do workflow and bulk emails send from my connected Gmail or Outlook?
No. HighLevel sends bulk and automated workflow emails through the sub-account's email provider, such as LC Email, Mailgun or SMTP. Only individual one-off emails go out through your synced mailbox.
Is there a sending limit when Gmail is connected?
Yes. HighLevel's Gmail sync documentation states Gmail supports only about 500 emails per day, and emails beyond that will fail. This limit applies to individual emails sent through the synced mailbox, not to bulk sends through your sending domain.
Can other team members read emails synced from my inbox?
They can if their role allows it. Admins with full access see all conversations in the sub-account. Users set to Only Assigned Data see conversations only where they are the contact owner or a follower.
Why did my email sync stop working?
The most common cause is lost permissions, for example after a password change, revoked app access or a security policy change in Google Workspace or Microsoft 365. Click Reconnect in the Email (2-way sync) section, sign in with the correct account and allow all requested permissions.
Why are emails between me and a colleague not syncing?
HighLevel deliberately excludes emails from contacts who are also users in the sub-account. This protects internal and potentially confidential conversations from appearing in client records.
Related Articles on HL Growth Partner
Email setup and deliverability
Conversations and contact records
- Two-way SMS in GoHighLevel Conversations
- Contact timeline and activity history
- Internal team notifications in GoHighLevel
