By Alpit Patel and the aibrevo team · October 15, 2026 · 8 min read
Does GoHighLevel Integrate With Salesforce or HubSpot?
Quick answer
HubSpot, partly. HighLevel has a native HubSpot app in Workflow Builder with one trigger (New Contact Created) and contact actions, but no managed two-way sync. Salesforce has no native connector we could find. Zapier, Make, webhooks or the API fill the gaps, and two-way sync is something you build.
Part of the guide: GoHighLevel setup guide
Key takeaways
- HubSpot: HighLevel has a native HubSpot app inside Workflow Builder (Automation, Apps, HubSpot) with a New Contact Created trigger and contact actions such as Create Contact and Find Contact. It is not a continuous two-way sync.
- Salesforce: we found no native connector on HighLevel's integrations page or in its help-center search. The integrations page shows a Salesforce step only as an example workflow.
- For anything beyond that, the documented routes are Zapier, Make, HighLevel webhooks and the v2 API. Zapier's LeadConnector listing offers HubSpot and Salesforce templates, and Zapier tags the Salesforce app Premium.
- Two-way sync is a build, not a switch: you decide the system of record per field, map custom fields, and handle duplicates and loops yourself.
- Polling triggers on Zapier's Free plan check for new data every 15 minutes. Instant triggers start a Zap immediately.
- HubSpot allows 190 requests per 10 seconds per app on Professional and Enterprise (100 on Free and Starter). Salesforce Enterprise Edition allows 1,000 API calls per license per 24 hours, and Unlimited allows 5,000.
Partly. Checked on October 15, 2026: HighLevel has a native HubSpot app inside Workflow Builder, but it is a workflow connector, not a managed two-way sync. For Salesforce we found no built-in connector on HighLevel’s integrations page or in its help-center search. Zapier, Make, webhooks and the v2 API cover everything else, and that works well for pushing leads one way. A true two-way sync is something you design and maintain.
The problem this page solves: you run HubSpot or Salesforce, or you are about to add HighLevel, and you need to know whether the two can share contacts, and whether you should connect them at all.
What does HighLevel’s own documentation say?
HubSpot. HighLevel’s help article How to use HubSpot workflow actions and triggers describes a native HubSpot app in Workflow Builder. You connect it from Automation, open or create a workflow, click Add New Trigger or Add Action, choose Apps, pick HubSpot, click Connect and authorize your HubSpot account. What it gives you:
| Piece | What the article lists |
|---|---|
| Trigger | New Contact Created (starts a HighLevel workflow when a contact is created in the connected HubSpot account) |
| Actions | Create Contact, Find Contact, Get Contact by ID, Search Contact by Email, Create Association |
| Field mapping | Standard fields such as name, email, phone, company, lifecycle stage and lead source, plus custom HubSpot properties |
| Typical use | Form submitted in HighLevel, search HubSpot by email, create the contact if none is found |
Two cautions. The article itself carries an internal review note saying the supported action list needs confirming against production, so open the action picker in your account to see what is really there. And the only trigger it documents is a new contact, not “contact updated” or “deal changed”, so it does not keep records in step over time.
Salesforce. HighLevel’s integrations page is a marketing page, and its only Salesforce mention is a sample workflow ending in “Contact is added to Salesforce.” A help-center search for Salesforce returned a migration guide and a Voice AI custom actions article, not a connector. The App Marketplace changes often, so search it inside your account before you build: a marketplace app, if one exists, would be the first thing to try.
Also HubSpot, but for moving house. HighLevel has a HubSpot importer for migrations. It imports contacts, deals as opportunities, companies, custom properties as custom fields, pipelines and stages, emails, notes and tasks. It is a one-time import, not a sync. HighLevel also supports a HubSpot MCP connector for its Managed Agents and Ask AI, which lets an AI agent create contacts or update deals in HubSpot; see does GoHighLevel have an MCP server for the other direction.
The rest is plumbing HighLevel documents: workflow webhooks, the v2 API and OAuth, and an official LeadConnector app on Zapier. Our Zapier vs native integrations post lists what is genuinely native, and the API integration guide covers auth and HighLevel’s own rate limits.
What are the ways to connect GoHighLevel to HubSpot or Salesforce?
| Route | What it does | Cost and effort | Watch out for |
|---|---|---|---|
| Native HubSpot app (HubSpot only) | New Contact Created trigger and contact actions inside HighLevel workflows | Included in the platform per HighLevel’s article | One trigger only. No Salesforce equivalent found. |
| Zapier | Ready templates for both CRMs through the LeadConnector app | Billed per Zapier task. Salesforce is tagged Premium. | Polling triggers on the Free plan check every 15 minutes. LeadConnector’s own triggers are limited (see below). |
| Make | HighLevel is listed with HubSpot CRM and Salesforce among its apps | Billed on Make usage | You build each scenario and its mapping. |
| HighLevel webhook to the CRM’s API | A workflow fires a webhook that creates or updates a record | Developer time, no per-event fee on the standard Webhook action per our Zapier post | You handle errors, retries and rate limits. |
| Direct API in both directions | Full control over fields and timing | Highest build effort | Both sides have call limits (below). |
| A marketplace app, if one exists | Whatever the app does | Per the app | Read what it syncs and in which direction. |
On Zapier, the LeadConnector and HubSpot page shows templates in both directions: create or update HighLevel contacts from new or updated HubSpot contacts and form submissions, add HubSpot contacts to HighLevel campaigns, create HubSpot contacts from HighLevel pipeline stage changes, and update HubSpot contacts from HighLevel changes. The Salesforce page lists templates such as add or update HighLevel contacts from Salesforce records, create Salesforce leads from new HighLevel entries, create HighLevel opportunities from Salesforce records and create HighLevel tasks for new Salesforce records. Zapier marks those Salesforce templates Premium.
One caveat from our own research: Zapier’s official LeadConnector app has a short trigger list (one trigger and five actions as of October 7, 2026, per our Zapier vs native post), so events such as form submitted or appointment booked usually go through a HighLevel workflow webhook into a Zapier Catch Hook. Check the current listing before you design around it.
Which setup do I need: one-way push, two-way sync, or migration?
| Your situation | Best fit | Why |
|---|---|---|
| HighLevel captures leads, sales lives in Salesforce or HubSpot | One-way push (HighLevel to CRM). For HubSpot, the native Create Contact action with Find Contact first. For Salesforce, Zapier, Make or a webhook. | One system of record, simple mapping, few failure modes. Zap or webhook on lead created. |
| Marketing in HubSpot, texting and follow-up in HighLevel | One-way push each way for a few fields only | Keep owners clear: HubSpot owns contact and lifecycle, HighLevel owns messaging status. |
| Both teams edit the same contacts daily | Two-way sync, built and tested | Needs field mapping, a rule for which system wins a conflict, and loop protection. Expect ongoing maintenance. |
| You pay for both CRMs but one does the real work | Migrate | A clean move can cost less than a sync you maintain. See the migration guides below. |
| Short transition while moving off one CRM | Temporary sync, then retire it | Keeps the sales team working during cutover. |
Two-way sync is the choice that goes wrong most often. Each side’s update triggers the other, so without a guard you can loop, and duplicates appear when the match key (usually email) is blank or differs. Decide the system of record for each field before you build anything.
What API limits matter when syncing with HubSpot or Salesforce?
Sync jobs fail at the edges of these numbers, especially an initial backfill.
| System | Published limit | Source note |
|---|---|---|
| HubSpot, Free and Starter, private apps | 100 requests per 10 seconds per app, 250,000 per day per account | HubSpot usage guidelines |
| HubSpot, Professional | 190 per 10 seconds per app, 625,000 per day per account | HubSpot usage guidelines |
| HubSpot, Enterprise | 190 per 10 seconds per app, 1,000,000 per day per account | HubSpot usage guidelines |
| HubSpot API Limit Increase add-on | 250 per 10 seconds per app, up to two purchases | HubSpot usage guidelines |
| Salesforce, Enterprise Edition | 1,000 API calls per Salesforce license per 24 hours (plus other license types) | Salesforce limits cheat sheet |
| Salesforce, Unlimited and Performance | 5,000 per Salesforce license per 24 hours | Salesforce limits cheat sheet |
| Salesforce, Developer Edition | 15,000 total per 24 hours | Salesforce limits cheat sheet |
| Salesforce, concurrent long-running requests | 25 in production and sandboxes, 5 in Developer and Trial orgs | Salesforce limits cheat sheet |
| HighLevel v2 API | 100 per 10 seconds and 200,000 per day, per app per resource | Our API guide |
HubSpot’s daily limit is shared across all apps in the account, and its burst limit applies per app. Salesforce’s allocation is counted across the whole org, not per user, and managed packages count against it. Both vendors return errors when you exceed limits: HubSpot answers with a 429 and Salesforce with REQUEST_LIMIT_EXCEEDED for concurrency. We did not verify field-count limits for either CRM, so check the current docs for custom field and property caps before you map dozens of fields.
Should I run both CRMs or migrate to GoHighLevel?
Run both when each system has a distinct job and a distinct owner. A common split: Salesforce holds enterprise accounts and complex sales process, while HighLevel handles text and email follow-up, booking and review requests for a local or agency business. Keep the sync narrow, a few fields and one direction at a time.
Migrate when the sync is a patch over a tool nobody wants. Signs: you maintain the connection more than you use the data, the same contact is edited in two places, or you are paying per-seat for a CRM your team barely opens. The trade-off runs the other way too: HighLevel is not built to replace Salesforce’s custom objects, forecasting and enterprise permissions, so a complex Salesforce org may be a poor fit for a move. Start with the comparisons, GoHighLevel vs HubSpot and GoHighLevel vs Salesforce, then the step-by-step guides, HubSpot to GoHighLevel and Salesforce to GoHighLevel.
Need a Salesforce or HubSpot integration built?
aibrevo’s own team builds Salesforce and HubSpot integrations and can tell you whether a sync or a migration fits. See our Salesforce services or contact us.
Sources
- HighLevel, Integrations page: Salesforce appears only in a sample workflow. Checked October 15, 2026.
- HighLevel Support, How to use HubSpot workflow actions and triggers in HighLevel: native HubSpot trigger, actions and setup path, plus the article’s own review note. Undated, checked October 15, 2026.
- HighLevel Support, Import data from HubSpot: HubSpot importer scope. Checked October 15, 2026.
- HighLevel Support, MCP connectors for Managed Agents: HubSpot MCP connector. Checked October 15, 2026.
- HighLevel Support, help-center searches for hubspot and salesforce: no native Salesforce connector article in the results. Checked October 15, 2026.
- Zapier, LeadConnector and HubSpot: template list, polling note (15 minutes on Free plan). Checked October 15, 2026.
- Zapier, LeadConnector and Salesforce: template list and Premium tag. Checked October 15, 2026.
- Make, HighLevel integrations: HubSpot CRM and Salesforce listed among apps. Checked October 15, 2026.
- HubSpot, API usage guidelines and limits: burst and daily limits by tier, 429 behavior. Checked October 15, 2026.
- Salesforce, API Request Limits and Allocations: daily allocations, concurrency limits. Checked October 15, 2026.
- aibrevo, GoHighLevel Zapier vs native integrations and API integration guide: LeadConnector trigger and action list, webhook costs, HighLevel API limits, cited there from Zapier and HighLevel sources.