If you run both HubSpot and Salesforce, the single most important factor in your integration design is not field mappings or sync direction. It is the Salesforce API call limit. Every record that syncs, every property you map, and every bulk import consumes a finite pool of daily API requests. Design without that number in mind, and your sync will eventually slow down, queue up, or stall.
This guide explains how Salesforce API limits work, how the native HubSpot-Salesforce connector consumes them, and the practical design decisions that keep your integration fast and reliable. It is written for operations, RevOps, and admin teams running both platforms at any company size.
This is part of our HubSpot-Salesforce integration series. For the broader setup picture, see our guide to connecting the two systems and our overview of common integration limitations.
HubSpot-Salesforce API limits are the daily cap on how many API requests Salesforce will accept across all connected applications. The native HubSpot connector draws from that same shared pool, so every sync, import, and field update spends calls. This matters for anyone running both CRMs because hitting the limit pauses syncs and delays data. The decision this article supports is what to sync, how much, and when — so you stay inside the limit by design rather than by accident. Vantage Point designs and tunes these integrations for mid-market teams running HubSpot and Salesforce together.
Salesforce API limits are the maximum number of API requests an org will process in a rolling 24-hour period. The native HubSpot-Salesforce connector is an API client like any other, so it consumes calls from the same allocation your other integrations use.
The allocation is based on your Salesforce edition and the number of user licenses. According to Salesforce's official API Request Limits and Allocations documentation, Enterprise Edition starts at a base of 100,000 requests per 24 hours plus 1,000 requests per Salesforce license. For example, an Enterprise org with 15 licenses gets 115,000 requests (100,000 + 15 × 1,000). Developer Edition is capped at 15,000 requests per org. Higher editions carry larger per-license allocations — always confirm the current numbers for your edition in the official cheatsheet.
Two limits matter most for integration design:
The API call limit is shared by every application integrated with Salesforce — not just HubSpot. Your portfolio tools, document systems, data warehouse connectors, marketing platforms, and custom scripts all draw from the same daily pool. HubSpot is one tenant in a shared budget.
That changes how you should think about the integration. The question is not "can we sync this?" — almost anything can sync. The real question is "is this worth the API calls?" Because the budget is finite, every sync decision is a spending decision.
Common actions that consume Salesforce API calls through the connector include:
A single contact can trigger multiple API calls per sync cycle as different properties update. Multiply that across tens of thousands of records and several connected systems, and the daily budget disappears faster than most teams expect.
The native connector gives you controls to manage consumption directly. Use them deliberately.
| Control | Where it lives | What it does |
|---|---|---|
| Allocated to HubSpot | Salesforce Sync Health → API call use | Caps the maximum daily calls the connector may use, protecting other apps |
| Inclusion lists (selective sync) | HubSpot connector settings | Limits which contacts sync from HubSpot to Salesforce |
| Field/property mappings | Sync settings | Each mapped, changing field can generate calls; fewer mappings means fewer calls |
| Sync direction | Per-object settings | One-way sync (e.g., Salesforce → HubSpot only) avoids return-trip calls |
A few important behaviors, per HubSpot's official Salesforce integration settings documentation:
Use this sequence when planning or auditing a HubSpot-Salesforce integration.
| Symptom | Likely cause | Fix |
|---|---|---|
| Syncs delayed by hours | Daily limit reached; records queued | Reduce sync scope; raise Salesforce allocation if licenses allow |
| Sudden sync backlog after a campaign | New lead intake channel flooding the sync | Tighten inclusion list criteria — do not delete contacts |
| Large backfill stalls midway | Bulk property map exceeded limit in one burst | Stage the sync gradually over multiple windows |
| Other integrations failing | HubSpot consuming too much of the shared pool | Lower "Allocated to HubSpot" to protect other apps |
The fixes are almost always about scope and pacing, not capacity. Disconnecting and reconnecting the integration does not resolve a limit problem — it usually triggers a fresh, expensive resync.
The native connector is the right tool for most HubSpot-Salesforce relationships. But high-volume or complex needs sometimes justify middleware such as Workato.
| Factor | Native Connector | Middleware (e.g., Workato) |
|---|---|---|
| Cost | Included with HubSpot | Additional platform license |
| Setup complexity | Lower | Higher |
| Sync logic | Standard objects, field mappings | Custom logic, transformations, multi-system flows |
| API efficiency | Good with inclusion lists | Finer control over batching and call volume |
| Best for | Standard contact/company/deal sync | High volume, complex routing, many connected systems |
Choose the native connector if your sync is mostly standard objects and you can stay inside API limits with inclusion lists and scoping. Choose middleware if you need custom transformation logic, are connecting many systems to the same shared API pool, or routinely brush against the limit during normal operations.
If your team is evaluating which approach fits your volume and architecture, Vantage Point can assess your current consumption and recommend a practical path. Explore our HubSpot-Salesforce integration services to see how we approach this.
Vantage Point is a mid-market specialist with senior-only, US-based consultants and an employee-owned model. As a HubSpot Gold Partner, Salesforce partner, and Workato partner, we design HubSpot-Salesforce integrations around the constraint that matters most: your shared API budget.
We help teams:
For ongoing tuning and monitoring, see our managed services and ongoing support, and for build and migration work, our system integration and data migration services.
If your team runs both HubSpot and Salesforce and wants an integration architecture or health assessment, Vantage Point can help you map the right next step.
Yes. The daily API request limit is a single pool shared by every application connected to your Salesforce org, including the native HubSpot connector, data warehouse tools, and custom integrations. Because the budget is shared, you should audit total consumption across the whole stack, not just HubSpot.
Syncs pause and queue until the rolling 24-hour window resets. Data is not lost — queued records catch up once capacity is available — but updates can be delayed by hours, which affects reporting and timely follow-up. Reducing sync scope is the most reliable fix.
Because every synced object, field update, and import consumes API calls from a finite daily pool. Syncing data that no workflow or report uses wastes that budget and brings you closer to the limit. Sync only what drives a decision in the receiving system.
Lower the connector's allocated calls, refine or tighten inclusion lists, set sync direction to one-way where possible, and stage large backfills gradually. Disconnecting the integration does not help and usually triggers an expensive full resync. Adjust scope and pacing instead.
Sync it gradually rather than all at once. A large initial backfill can consume your entire daily allocation in a single burst, pausing all other syncs. Stage the load across multiple 24-hour windows, or use middleware with finer batching control for very large datasets.
Salesforce reports API usage in Setup under company information and system overview, and the HubSpot connector shows consumption on its Sync Health tab. Monitor both regularly, and especially before and during migrations or bulk imports, so you can catch a spike before it stalls your sync.
Use middleware when you need custom transformation logic, are connecting many systems to the same shared API pool, or routinely approach the API limit during normal operations. The native connector is the better choice for standard object sync that fits inside the limit with inclusion lists and scoping.
No. When the limit is reached, records queue and sync once the 24-hour window resets. The risk is delay, not loss — but delayed data can still disrupt reporting, lead routing, and timely outreach, so designing within the limit remains important.