1. Home
  2. Systems
  3. Salesforce integration

Salesforce integration comes down to five routes, and the API limits decide between them

You can connect Salesforce to an ERP or another system in five ways: your own build on its APIs, MuleSoft, Salesforce Connect, a ready-made connector, or an AI agent. Every route that calls Salesforce's APIs draws on one daily allocation, which Salesforce counts for the whole org, not per tool. We read Salesforce's own guides for version 68.0, Winter '27, on 18 November 2026, and set out the limits that pick the route for you.

Checked 18 November 2026

Five ways to connect Salesforce, and what each suits

Pick the route by how many systems you link, how much data moves and who will run it. Each route below comes from Salesforce’s own documents, or from the connector vendor’s.

Scroll the table sideways to see every column.

Route How it works Suits Watch for
Your own build on Salesforce’s APIs REST API for single records, Bulk API 2.0 for large loads, Change Data Capture and Pub/Sub API for changes One to a few flows with clear rules Every call counts toward the org’s daily allocation
MuleSoft Anypoint Platform Salesforce’s own integration platform, with hundreds of prebuilt connectors Linking several systems through one platform Some connectors, such as SAP’s, need a separate license
Salesforce Connect External objects read data in another system live, through callouts Showing ERP data in Salesforce without a copy Best when users need a little data at a time
A ready-made connector Another vendor’s sync, such as HubSpot’s, Databricks’, Snowflake’s or Power Automate’s A common pairing with standard records Each one has its own gaps and limits
An AI agent Agentforce actions through Flows, Apex and MuleSoft APIs, or a custom agent on the API Jobs that need judgment, such as reading an emailed request A custom agent on the API draws on the same daily allocation

Two routes can work side by side. A ready-made sync covers the standard records. A small custom build or an agent covers the one job the sync cannot do.

Salesforce API limits: how many calls you get a day

Salesforce gives each org one daily pool and counts it for the whole org, not per user. Your ERP link, your marketing sync and your data warehouse feed all draw from that one pool.

Scroll the table sideways to see every column.

Edition or org Daily API calls, per Salesforce’s limits cheat sheet
Enterprise Edition 100,000, plus 1,000 per Salesforce license, plus purchased add-ons
Enterprise, Salesforce’s own example 115,000 for an org with 15 Salesforce licenses
Unlimited and Performance Edition 100,000, plus 5,000 per Salesforce license, plus purchased add-ons
Developer Edition 15,000 per 24 hours
Full sandbox, not made from a template 5,000,000 per 24 hours

One trap: Salesforce renamed its editions. Its Sales Cloud pricing page says Core replaces Enterprise Edition, Advanced replaces Unlimited Edition and Max replaces Agentforce 1 Edition. The limits sheet still uses the old names. Ask Salesforce which line of the sheet your contract maps to.

  • Which calls count. The REST API, SOAP API, Bulk API, Bulk API 2.0 and most Connect REST APIs all count toward the daily allocation.
  • Long calls. A production org can run 25 calls at once that last 20 seconds or more. Calls under 20 seconds have no such cap.
  • Timeouts. A REST or SOAP call times out after 10 minutes, except query calls.
  • The ceiling. Paid orgs in active status can run a little past the daily limit, up to a hard cap. Salesforce says not to rely on it. Trial, Developer Edition and sandbox orgs cannot go past at all.
  • Checking usage. Every REST response carries the count in a header called Sforce-Limit-Info, and a /limits call reports usage on demand.

Which Salesforce API fits which job

Use the smallest API that does the job. The table pairs each job with the API Salesforce’s guides point to, and the numbers that set its size.

Scroll the table sideways to see every column.

Job API Limits Salesforce publishes
Create or update a handful of records REST API, composite requests 25 subrequests per composite request, 500 in a composite graph, 200 records per sObject Collections call
Load or pull large data Bulk API 2.0 Suggested above 2,000 records. One object and one action per job. 15,000 batches per rolling 24 hours, shared with the old Bulk API, up to 150,000,000 records
Hear about changes Change Data Capture over Pub/Sub API Events for create, update, delete and undelete. Change events kept three days
Send your own business events Platform events High-volume events kept 72 hours
Sign in External client app or connected app, with OAuth 2.0 New connected apps are restricted since Spring ’26. All REST traffic runs over HTTPS
Work with typed records from older tools SOAP API The enterprise WSDL is a strongly typed view of your org’s data. Its login() call retires in Summer ’27
Move setup between orgs, such as a Salesforce Connect adapter Metadata API Salesforce says to use it to move metadata between orgs during development

Two details save rework. REST responses always carry 18-character record IDs, while requests can send 15 or 18. And Bulk API 2.0 query jobs do not use up batches; only ingest jobs do.

Dates that will break old Salesforce integrations

Old integrations fail on dates Salesforce has already set. Check each one against the tools in your org.

  • API versions 31.0 to 40.0 are unsupported from Summer ’27 and retired from Summer ’28.
  • Versions 21.0 to 30.0 were retired as of Summer ’25. A call to a retired version gets the 410:GONE error.
  • SOAP login() retires in Summer ’27. It is already off by default for orgs created in Winter ’26 or later, and works only in API version 64.0 and earlier.
  • The older Bulk API signs in with a session ID from that same login() call. Bulk API 2.0 uses a bearer token instead. So an old bulk job is a double risk.

Salesforce says it supports each API version for at least 3 years, and gives at least 1 year of notice before support ends. The current version is 68.0, in the Winter ’27 release.

Salesforce Connect shows ERP data without copying it

Salesforce Connect brings outside records into Salesforce as external objects. Salesforce’s Object Reference says the data stays outside your org, and external objects always show its current state. Nothing needs to be kept in sync.

It has an adapter for each kind of source:

  • OData 2.0 and 4.0. These read any system that publishes an OData service. Salesforce’s own example names SAP, Microsoft and Oracle.
  • Cross-org. This reads other Salesforce orgs through the REST API.
  • Custom. You write it with the Apex Connector Framework when no other adapter fits.

Salesforce says external objects suit large data you cannot or do not want to store, when users need only a little at a time. Its own example is data stored on premises in an ERP system.

In the API, their names end in __x, as in ExtraLogInfo__x. They need API version 32.0 or later.

MuleSoft: when a platform beats a direct build

MuleSoft is Salesforce’s integration platform. MuleSoft says Anypoint Platform offers hundreds of prebuilt connectors, and links AI agents, SaaS apps, legacy systems and partners through one platform. It adds AI policies and agent discovery to govern how agents reach your data and APIs.

It pays off when you run many links and have people to own them. Agentforce Builder can call MuleSoft APIs, so the same platform serves agents too. For one or two flows, a direct build may be enough. Check connector licensing early: MuleSoft says its SAP Connector needs a separate license.

Ready-made Salesforce connectors each leave a gap, from hard deletes to trial orgs

Read a vendor’s connector limits before you rely on it. Here is one gap from each.

  • HubSpot’s Salesforce sync can use up to four Salesforce API calls for one contact record. See HubSpot and Salesforce integration.
  • Databricks’ Salesforce connector pulls data into Databricks, with up to 250 objects per pipeline. Hard deletes in Salesforce need a full refresh of the table.
  • Snowflake’s Salesforce Bulk API connector copies data on a schedule you set, and does not carry hard deletes into Snowflake.
  • Microsoft’s Power Automate connector works with Salesforce objects, but Salesforce trial accounts have no API access, so it cannot use them.

These are the Salesforce objects an ERP link reads or writes. The middle column is Salesforce’s own definition.

Scroll the table sideways to see every column.

Salesforce object What it is Usual ERP match
Account An organization or person involved with your business Customer
Product2 A product your company sells Item
PricebookEntry Joins a product to a price book Price list line
Opportunity A sale or pending deal Becomes a sales order when won
OpportunityLineItem A product on an opportunity Sales order line
Quote A record of proposed prices, since API version 18.0 Sales quotation
Order and OrderItem An order tied to an account or contract, and its products Sales order and lines
Case A customer issue or problem Service ticket or return

To start a flow when a deal changes, your code listens on the channel /data/OpportunityChangeEvent. Salesforce’s Revenue Cloud also says its product catalog links to PIM, PLM and ERP systems, if you run it.

Agentforce reaches outside Salesforce through MCP servers and A2A

Agentforce can now reach other systems through open standards. Salesforce says Agentforce keeps a central registry for MCP servers, including servers from other orgs. MCP, short for Model Context Protocol, is a standard way for AI tools to use other software. Salesforce also says you can deploy an MCP server from AgentExchange with no code, and that A2A lets Agentforce work with other vendors’ agents.

For developers, Salesforce publishes an open source DX MCP Server that lets language models work with Salesforce orgs. Its Headless Toolkit brings Salesforce into any AI, agent or app.

Our team has built Salesforce agents in Agentforce and as custom agents through Salesforce’s API, for six jobs from lead qualification to quote to cash. See Salesforce AI agents and our comparison of Agentforce, Joule, Breeze or a custom agent.

Where your Salesforce data lives

Salesforce says Hyperforce, its infrastructure, is built for the public cloud. You can pick regions in the U.S., the U.K., Germany, India, Japan and more. Data is generally stored in the country where your org sits, if the services run there.

Salesforce’s Infrastructure and Sub-processors document names the hosts. For Sales Cloud, Service Cloud and the other Salesforce Services, an org runs on AWS, Google Cloud or Salesforce’s own infrastructure, in a region chosen when the org is first created. Hyperforce costs nothing extra, Salesforce says, except Hyperforce EU OZ, which is a paid offering.

Pages for each Salesforce pairing

Each pairing has its own page, with that pair’s records and limits:

How we work on Salesforce integration

Our team takes Salesforce implementation end to end: the org set up, data moved in, the team trained. So the link can be part of a new org’s setup or come later. On a project, we count your daily API use first, then pick the route. The first call is free.

Questions

Does Salesforce have API limits?

Yes. Salesforce gives each org a daily allocation of API calls and counts it for the whole org, not per user. Enterprise Edition gets 100,000 calls a day, plus more per license, plus any you buy. Its own example: 15 licenses gives 115,000 calls. A Developer Edition org gets 15,000. Long calls are capped too: 25 at once in a production org if each runs 20 seconds or more.

Is Salesforce on AWS or Azure?

AWS or Google Cloud, not Azure, for Sales Cloud and Service Cloud. Salesforce's Infrastructure and Sub-processors document, published 17 November 2026, says such an org is hosted on AWS, Google Cloud or Salesforce's own infrastructure. The region is chosen when the org is first created. Salesforce says data is generally stored in the country where your org sits.

What are REST APIs, and which one does Salesforce use?

A REST API is a way for software to read and write records over the web, one request at a time. Salesforce's REST API handles single records, and the current guide covers version 68.0. All its traffic runs over HTTPS. For loads over 2,000 records, Salesforce points to Bulk API 2.0, which takes records as CSV files instead.

Do we need MuleSoft to integrate Salesforce with our ERP?

No. MuleSoft is Salesforce's own integration platform, and it is one of five routes. Your own build on the REST and Bulk APIs, Salesforce Connect or a vendor's connector can also link an ERP. Check MuleSoft's connector licenses early: MuleSoft says its SAP Connector needs a separate license on top of the platform.

Will our Salesforce integration break when old API versions retire?

It will if it calls an old version. Salesforce says API versions 31.0 to 40.0 are unsupported from Summer '27 and retired from Summer '28. A call to a retired version gets a 410 error. Separately, the SOAP login() call retires in Summer '27. The older Bulk API signs in that way, so check every tool that uses it.

Do we need an official Salesforce partner to do this?

Not for this work. What decides an integration or an agent is a team that knows Salesforce from the inside and builds on Salesforce's published APIs. Our team has set up Salesforce end to end, moved data in, trained teams, and built agents in Agentforce and through the API. You license Salesforce from Salesforce or its reseller, and we take the build from there.

Sources

Every source behind a figure or a vendor fact on this page, with the day we read it.

Pages in this section

  • HubSpot and SalesforceHubSpot's own Salesforce connector syncs contacts, companies, deals and tickets both ways. Its API use, limits and gaps, from HubSpot's help center.

Talk to us about your Salesforce integration

Bring your edition, your ERP and the records that must move. The first call is free.

Book a Salesforce integration call