Home/HighLevel/Features/Email/How to set up inbound email with Mailgun in HighLevel

Conversations and Inbox

How to set up inbound email with Mailgun in HighLevel

In short

Inbound email using Mailgun lets you receive messages sent to a domain, then forward, route or log them inside HighLevel workflows. The feature requires a dedicated subdomain, because a domain can have only one MX record set, and Mailgun does not provide a mailbox. Follow the guide to configure Mailgun, bind it to a single subaccount, and test the flow.

AreaEmail · MailGun
Used forMarketing agency, SaaS startup, Real estate brokerage
Setup steps10 steps in 3 tasks
Last updatedNovember 16, 2026

01Who this is for

  • Agencies that manage multiple client domains need separate subdomains to keep inbound routing isolated for each client.
  • SaaS Founders who send transactional emails from their own domain and want replies captured in HighLevel without disturbing a corporate inbox.
  • Consultants running cold email campaigns who require a subdomain for inbound routing while keeping their primary email with Google Workspace.

02Mailgun inbound email, explained

The inbound email feature captures messages addressed to a domain that is set up in Mailgun. Once received, Mailgun can forward the mail to another address, push it to a webhook, or log it for workflow automation inside HighLevel. Because a domain can hold only one MX record set, the feature works best when a dedicated subdomain, such as mg.yourdomain.com, is used for Mailgun while the root domain stays linked to an existing inbox provider.

Configuration lives in the HighLevel UI under Agency View > Settings > Email Services > Location Settings. From there you map a Mailgun domain or subdomain to a single HighLevel subaccount, ensuring that all inbound messages are routed to the correct account. After mapping, you can test receipt by sending an email to an address on the configured domain or subdomain and confirming it appears in the Conversation tab.

03How businesses use Mailgun inbound email

  • Marketing agency. Create a unique Mailgun subdomain for each client, map it to the client’s subaccount in HighLevel, and let inbound replies feed directly into the client’s conversation history.
  • SaaS startup. Set up mg.startup.com in Mailgun, bind it to the startup’s HighLevel subaccount, and capture user replies to support emails without affecting the primary corporate inbox.
  • Real estate brokerage. Use a subdomain like mg.brokerage.com for inbound leads, map it to the brokerage’s subaccount, and have reply emails appear in HighLevel so agents can follow up in the same system.

04How to set up and use Mailgun inbound email in HighLevel

Set up Mailgun

  1. Create or select a Mailgun account and add the desired domain or subdomain, such as agency.com or mg.agency.com.
  2. Add the required DNS records provided by Mailgun to the domain’s DNS host.
  3. Verify the domain in Mailgun to confirm that DNS changes are correct and the domain is active.

Map Mailgun domain to one subaccount only

  1. Open Agency View, go to Settings, then Email Services, and select Location Settings.
  2. Choose the Mailgun domain or subdomain you just verified and assign it to a single HighLevel subaccount.
  3. Confirm that the same domain is not listed under the Domain Services tab for another subaccount.
  4. If a deleted subaccount previously used the same Mailgun domain, contact support to clear the lingering mapping.

Test inbound email

  1. Send a test message to an address on the configured domain (for example, testing@agency.com) or subdomain (for example, anything@mg.agency.com).
  2. Open the Conversation tab in HighLevel and verify that the inbound email appears.
  3. If the message does not show, double check the MX record pointing to Mailgun and the subaccount mapping.

05What it looks like in HighLevel

06Settings that matter

  • Location Settings. Determines which HighLevel subaccount a Mailgun domain or subdomain is linked to, ensuring inbound emails route to the correct account.

07Things to know before you rely on it

  • A domain can hold only one set of MX records, so you cannot use Mailgun and another email provider for inbound on the same domain.
  • Mailgun does not provide a mailbox; it only routes, forwards, or processes incoming messages.
  • Using the root domain for Mailgun will disable any existing inbox (for example, Gmail or Outlook) because MX records are redirected to Mailgun.

08How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

Most people add Mailgun MX records to their root domain and end up losing their Gmail or Outlook inbox. The conflict between MX records means inbound mail stops arriving where they expect it.

I would create a dedicated subdomain for Mailgun, point the MX records only there, and leave the root domain tied to the existing inbox. That keeps sending via Mailgun while preserving normal email flow.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 16, 2026

Common questions

Common questions about Mailgun inbound email.

Can I use Mailgun and Gmail on the same domain?

No. A domain can only have one MX record set, so if MX records point to Gmail, Mailgun cannot receive emails for that domain, and vice versa.

Why does adding Mailgun MX records to my root domain not work?

Root domains usually already have MX records for providers like Google Workspace. Adding Mailgun MX records without removing the existing ones causes delivery failures because email systems cannot split inbound handling across providers.

Can I still send emails from my root domain using Mailgun?

Yes. Sending emails does not depend on MX records, so you can send through Mailgun while the root domain remains connected to another inbox provider.

Does Mailgun provide an inbox for received messages?

No. Mailgun only routes, forwards, or processes inbound emails via routes or webhooks; it does not offer a mailbox interface.

What is the recommended setup for cold email campaigns and replies?

Use a subdomain for Mailgun (for example, mg.yourdomain.com) and keep the root domain linked to your regular inbox provider. This avoids MX conflicts and keeps inbound routing reliable.

Can I use the root domain with Mailgun for inbound emails?

Yes, but you must point the root domain’s MX records to Mailgun, which will disable any existing inbox service and route all incoming mail through Mailgun routes.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.