GoHighLevel Integrations: Native, Zapier, and API
GoHighLevel sells itself as the agency operating system, so the integration question is really two: what the platform wires up natively, and what you must reach through Zapier or the API. HighLevel publishes no official count of native integrations or marketplace apps, and every figure circulating on affiliate blogs is unverified, so this directory profiles the 25 connections that actually decide whether a sub-account can send, bill and follow up. Zapier reaches roughly 9,000 other apps, and API v2 spans about 40 resource domains with hundreds of operations plus 50+ webhook events, where everything the marketplace misses ends up.
One naming trap governs the whole page: the infrastructure is branded LeadConnector. The API host is services.leadconnectorhq.com, the help centre is help.leadconnectorhq.com, and both the WordPress plugin and the Zapier app are listed as LeadConnector, so searching either directory for “GoHighLevel” returns nothing. Email follows the same pattern: LC Email is the built-in sending stack and it runs on Mailgun, so attaching Mailgun is not a competitor swap but a move one layer down the same pipe.
At a glance
Read those numbers as a hierarchy, not a total. Native connections write into contacts, conversations and pipelines with no glue code; the marketplace, Zapier and Make cover the rest; API v2 is the floor under all of it.
Integrations directory
Twenty-five connections, grouped by the job they do inside a sub-account. Tags mark how each is wired: NATIVE for a first-party connection set up in sub-account settings, API for modules on API v2, ZAPIER for the iPaaS route. The catalogue of installable apps is the HighLevel App Marketplace.
Email and sending (4)
LC Email is the default and bills at $0.675 per 1,000 emails. Any sub-account can switch to its own SMTP provider, but official documentation is explicit that a custom service makes some platform features unavailable, postmaster tool integrations, bounce classification, spam score checking and blacklist monitoring. Nothing errors; the reporting just goes blank.
Powers LC Email on smtp.mailgun.org, and can also be attached directly as a custom SMTP provider.
Sending provider via an app-specific password with 2-step verification; sales mail, not campaign volume.
First-class option in the email service picker; the most common cost-driven replacement for LC Email.
Supported through the “Other” custom SMTP category, for agencies already running their own sending stack.
The reverse direction. SMTP credentials issued by GoHighLevel, exists but is deliberately small: at most five SMTP users per dedicated domain and a cap of 1,500 emails per day, after which credentials are deleted from every dedicated domain rather than throttled. Compare Mailgun or Brevo before pointing a bulk mailer at a CRM relay.
Payments and accounting (4)
Payments are where SaaS Mode economics live: rebilling at cost starts at $297, rebilling with markup requires $497 Agency Pro.
Processor for funnels, invoices and SaaS Mode rebilling; excluded from snapshots, so reconnected per sub-account.
Alternative checkout for funnels and order forms where buyers expect a wallet, not a card field.
Card gateway for sub-accounts whose merchant category or banking relationship rules out Stripe.
Syncs invoices, products and payments to QuickBooks Online so client bookkeeping needs no second export.
Messaging and voice (5)
Carrier behind LC Phone; agencies can bring their own subaccount for direct pricing and compliance registrations.
Routes page messages into the inbox so threads trigger the same workflows as SMS and email.
Brings DMs into the shared inbox, closing the loop between paid social and pipeline follow-up.
Messaging channel inside conversations and workflows; requires Meta approval, so treat onboarding as a dependency.
Pushes workflow notifications and lead alerts into channels, the usual substitute for internal notification email.
Ads, analytics and local (4)
Imports lead form submissions and ad performance straight into pipelines, removing the CSV step.
Reports spend and conversions inside attribution dashboards so client reporting needs no separate BI layer.
Tracks funnel and site traffic alongside platform attribution when the two are separate properties.
Pulls reviews and GBP messaging into the inbox, the connection carrying most local-services retainers.
Calendars and scheduling (3)
Two-way sync for booking availability and appointment writeback.
Calendar sync plus two-way email threading, so replies stay attached to the contact record.
Auto-generates a meeting link when an appointment is booked, removing a manual step from consultation funnels.
Websites and commerce (2)
Syncs customers and orders into contacts so post-purchase automation runs on CRM data, not exports.
Official plugin embedding forms, surveys, the chat widget and booking calendars into an existing site.
Automation and marketplace (3)
Everything not covered above goes through one of these three. Zapier and Make are the no-code routes; the marketplace is where installable OAuth apps and custom payment providers live.
Connects the platform to roughly 9,000 other apps, listed as LeadConnector; searching for “GoHighLevel” finds nothing.
HighLevel modules for scenario automation on API v2, usually authenticated with a Private Integration Token.
Canonical directory of installable agency-level and sub-account-level apps and custom payment providers.
Two structural limits shape every integration plan. First, an API request or MCP session targets a single sub-account at a time, mirroring the locationId constraint in REST; agency-wide operations mean iterating locations, not one bulk call. Second, snapshots do not carry integrations. Stripe connections, third-party connections, phone numbers and DNS or email settings are all excluded, so a cloned build still needs its own sending domain verified and its own payment connection. Plan warm-up per client, not per snapshot. If the requirement is campaign tooling rather than an agency CRM, compare ActiveCampaign, Klaviyo or Mailchimp.
Frequently asked questions
What integrations does GoHighLevel have natively versus through Zapier?
Native connections cover what the platform treats as core: payments (Stripe, PayPal, Authorize.net), messaging (Twilio, Messenger, Instagram, WhatsApp, Slack), Google and Meta ads and analytics, Google and Outlook calendars, Shopify, QuickBooks and the email providers in the email service settings. Everything else goes through the LeadConnector app on Zapier (roughly 9,000 apps), through Make, or through API v2 and its 40 or so resource domains. HighLevel publishes no official count of native integrations, so treat any exact number quoted elsewhere as unverified.
Why can’t I find GoHighLevel on Zapier?
Because it is listed as LeadConnector. The branding split runs through the stack: the API host is services.leadconnectorhq.com, the support site is help.leadconnectorhq.com, and the WordPress plugin is LeadConnector too. Search either directory for LeadConnector and the app appears immediately.
How do I install a marketplace app for one sub-account?
Apps in the HighLevel App Marketplace declare the scope they install at: agency (company) level, sub-account (location) level, or both. From the listing you choose the account to install into, then approve the OAuth scopes requested. Those scopes are the ceiling for everything the app can do afterwards, if capabilities appear missing later, under-selected scopes are the first thing to check.
Do snapshots transfer integrations, Stripe connections and DNS settings?
No. Official documentation states that contacts, appointments, conversations and live account history are not transferred, and the exclusion list explicitly covers Stripe connections, third-party account connections, assigned phone numbers for Voice AI agents, and DNS and email settings including domain configuration. A snapshot rebuilds workflows, funnels, calendars and templates; each new sub-account still needs its own sending domain verified, its own DNS published and its own gateway connected.
How does Stripe work for SaaS Mode rebilling?
Stripe is the processor behind SaaS Mode, where an agency resells platform usage to its clients. Rebilling phone and email at cost starts at the $297 Unlimited tier; rebilling with markup, plus automated sub-account creation, requires $497 Agency Pro. Email is metered at $0.675 per 1,000 sends and a dedicated IP is $59 per month, so the markup on those meters is where agency margin comes from.
What is the difference between an agency-level and a sub-account-level install?
It mirrors the token model in the API. An agency (company) install operates on agency-level resources and can mint a location token to act on one sub-account; a sub-account (location) install is confined to that tenant. The same boundary governs MCP: a session addresses one sub-account, though an agency connection can enumerate and switch locations. One consequence is worth memorising, sending domains created at agency level are not selectable for calendar emails, which require a sub-account-level domain.
This review follows our email infrastructure testing methodology. We disclose affiliate relationships in our editorial independence policy.
