Automation

Salesforce Integration: Options, Costs and What Breaks

Steel suspension cables of a modern bridge against an overcast sky One record, every system.

A Salesforce integration connects Salesforce to another system so that accounts, orders and payments move between them without anyone retyping them. You have four routes: an app from the AppExchange, a no-code tool such as Zapier, an integration platform such as MuleSoft, or a custom build on Salesforce’s APIs. The right one depends on your volume, how many systems are involved, and whether data must sync both ways.

Start with the cheapest route that does the job. A listed app or a no-code flow is often enough for a simple connection. A custom build earns its cost when the logic spans several systems, volumes are high or the other side is your own platform. With us, connecting two systems starts from £5,000 (about $6,500), at a fixed price agreed before work starts.

This guide covers what to connect Salesforce to, how to check your edition, how to choose a route, what an API build involves, the limits Salesforce sets, what it costs and what goes wrong. It is a neutral buy-or-build guide, so it will tell you when a ready-made connector is the better answer. If you are still choosing a CRM, our HubSpot vs Salesforce comparison covers that decision.

What can you connect Salesforce to?

Salesforce usually sits at the front of the business, so the useful question is which other system needs its records. Look for an existing connector before you plan a build. The table shows the usual candidates.

System typeExamplesTypical data flow
ERP and financeAccounting software, ERPWon deals and accounts into finance as customers and invoices; payment status back
EcommerceOnline store platformsCustomers and orders into Salesforce; account details back
SupportHelp desk and ticketing toolsTickets and conversations against the right account
Your own platformCustomer portal, internal systemWhatever your data model creates, built against the API

A bespoke platform is different. Nothing on a marketplace knows your data model, so that side is built against the API. A finance link is a common first flow. Our QuickBooks integration guide covers a won deal becoming an invoice, and the same pattern applies to most accounting tools. For larger estates, see our ERP integration guide. The general mechanics of connecting any two systems are in our API integration guide.

Check your edition first

Before you design anything, confirm that your Salesforce plan includes API access. Salesforce’s API request limits page covers Enterprise, Unlimited, Performance and Developer editions, and Professional Edition with API access enabled. Professional does not include it by default.

Salesforce’s US pricing page now names its sales plans Starter Suite, Pro Suite, Core, Advanced and Max. At the time of writing (November 2026), they cost $25, $100, $195, $395 and $550 per user per month. Pro Suite and above are billed annually. The same page shows the Web Services API as not included on Starter Suite, a $25 per user per month add-on on Pro Suite, and included on Core, Advanced and Max.

Salesforce says Core replaces Enterprise Edition and Advanced replaces Unlimited Edition, so those plans map onto the Enterprise and Unlimited rows in the limits documentation. Confirm with Salesforce, or your account executive, in writing which limits apply to your contract.

It can also be negotiated. For SBU, a UK energy broker, we built automation across Salesforce, an LLM and the client’s email. Salesforce API access was agreed on the plan they already had, so no tier upgrade was needed. Accounts, Contacts, Opportunities and Contracts sync from their Salesforce organisation daily, pulling only what has changed since the last run, so the sync stays fast as the pipeline grows.

AppExchange, Zapier, MuleSoft or a custom build?

Work down the table in order and stop at the first row that fits.

RouteWins whenWatch for
AppExchange appA listing moves the records you need in the direction you needIt syncs what its maker chose, in the direction they chose
ZapierBoth sides have connectors and the logic is a simple trigger and actionNeeds a paid plan, usage-based billing and flows that quietly become critical
MuleSoftMany systems, a central team and a need for governanceCost and the skills needed to run it
Custom buildLogic spans systems, volumes are high or the other side is your own platformIt needs a proper build and someone to look after it

AppExchange

Search the AppExchange for the name of the other system. For each listing, check which records it syncs, in which direction, and what it does when a record already exists or a call fails. Test it on a sandbox copy before you commit.

Zapier

Salesforce is a premium app on Zapier. Zapier’s Salesforce guide says you need a paid plan to use it: Professional, Team or Enterprise. That makes it a fair middle step for simple flows, as long as you budget for the subscription.

No-code tools break down in four places:

  • Custom matching rules. Deciding that two records are the same customer takes more than a trigger and an action.
  • High volume. Usage-based pricing climbs, and a flow that retries blindly can eat your Salesforce allocation.
  • Two-way conflicts. When both systems can edit a record, simple flows overwrite each other.
  • Your own platform. There is no connector for software only you run, so the API is the only way in.

MuleSoft

MuleSoft is Salesforce’s own integration platform. Its pricing page says new pricing starts at $2K per month billed yearly, and a pre-commit model has a $50K minimum annual commitment, at the time of writing (November 2026). That fits an organisation with many systems and a team to run the platform. For two or three connections, it is usually more platform than you need.

Custom build

A custom build is code that talks to Salesforce for you, with rules for what to send, when, and what happens when something fails. Choose it when the logic spans systems, the volume is high or nothing listed fits. Our systems integration page takes the same position as this guide: if two of your systems already sync natively, we’ll tell you to switch that on.

What a Salesforce API integration involves

Salesforce offers several ways in, and a good integration uses the right one for each job.

  • REST API for record-level work, such as creating or updating one account or opportunity.
  • Bulk API 2.0 for large loads. Salesforce’s bulk limits page suggests Bulk API 2.0 for operations over 2,000 records.
  • Change events to react to changes. Where your edition supports them, change events let your integration react to a change instead of polling. Check Salesforce’s documentation for what your plan includes.

Reacting to events matters because of the limits covered below. An integration that asks Salesforce every minute whether anything changed spends requests whether or not anything did.

Authentication

Get authentication right early. Since Spring ‘26, creating new connected apps is disabled by default for all Salesforce orgs. Salesforce recommends external client apps for all new integrations. Existing connected apps keep working.

In practice, a new integration should be set up as an external client app. Agree who owns that app and its credentials, because an integration that stops authenticating stops syncing.

The build work

Whichever route you take, the build work has the same shape:

  • Map one flow first. Name the trigger, the fields that move and the direction, such as a won opportunity creating an invoice. Add the next flow only when the first is live.
  • Build the matching rules. Decide how a record in one system is recognised in the other. Store each system’s ID in the other and match on those.
  • Make every call safe to repeat. A retry must never create a second record.
  • Add an error queue. A failed record goes to a queue a named person reviews, so one bad record does not block the rest.
  • Test with messy data. Use real records with missing fields, odd characters in names and duplicates.
  • Produce a reconciliation report. A simple report showing what moved, what failed and what is waiting lets the business trust the sync.
  • Go live in stages. Start with one flow and a short run alongside the manual process, in a sandbox first.

Salesforce API limits

Salesforce limits how many API requests an org can make in 24 hours. The API request limits page sets out the daily allocation:

EditionDaily API request allocation
Enterprise (and Professional with API access)100,000 plus 1,000 per Salesforce licence, plus purchased add-ons
Unlimited and Performance100,000 plus 5,000 per Salesforce licence, plus purchased add-ons
Developer15,000 in total

An Enterprise org with 15 Salesforce licences gets 115,000 requests per 24 hours. The limit is org-wide, not per user, so every connected app, integration and installed managed package draws from the same pool.

Salesforce also limits long-running requests. For requests that take 20 seconds or more, the limit is 25 concurrent requests in production and sandboxes. When you exceed a limit, the call returns a REQUEST_LIMIT_EXCEEDED error. Salesforce allows some overage on paid orgs, but do not design around that.

Bulk work has its own ceilings. Per the bulk limits page, Bulk API and Bulk API 2.0 share 15,000 batches per rolling 24 hours, and ingest can handle up to 150,000,000 records per 24 hours.

A quick illustration shows why polling hurts. An integration that checks one object once a minute makes 1,440 calls a day, whether or not anything changed. Run ten such checks and that is 14,400 calls a day, which is 12.5% of a 115,000 allocation spent before any real work starts. Change events, batching and a queue keep the rest free.

To stay inside the limits, watch usage. Salesforce returns the Sforce-Limit-Info header with API responses, and the /limits call reports what remains. You can also set up API Usage Notifications, which alert you as usage rises.

How much does a Salesforce integration cost?

There are two costs: the Salesforce side you already pay for, and the integration on top. On the Salesforce side, that means licences, a Web Services API add-on at $25 per user per month on Pro Suite, and MuleSoft if you choose it. Prices are in the sections above, and they change, so check Salesforce’s pages before you budget.

For the integration itself, no-code routes cost a tool subscription plus the time to set them up and test them. AppExchange apps are subscriptions priced by their makers.

With us, connecting two systems you already use, such as Salesforce and your finance system, starts from £5,000 (about $6,500) and includes syncing with checks. A business-wide integration across your core tools starts from £10,000 (about $13,000). Each price is fixed and agreed before work starts. After go-live, support starts from £400 (about $520) a month.

For a larger estate, enterprise software integration starts with an integration audit and plan from £4,000 (about $5,200).

What moves the price of a custom build:

  • How many systems and flows. A Salesforce-to-finance flow is one job. A second system adds its own mappings, tests and failure cases.
  • Direction. Sending data one way is simpler than syncing both ways, which needs a rule for when both sides edit a record.
  • Data quality. Duplicates already sitting in Salesforce need cleaning before records can be matched.
  • History. Copying years of past records is a separate job from syncing new ones.
  • Volume. Bulk loads need batching, a queue and back-off.

What goes wrong with Salesforce integrations?

These problems appear after go-live, so settle them at the start.

Retired API versions. Salesforce retires old API versions. It retired versions 21.0 to 30.0 in Summer ‘25, as its API version retirement post announced, and retired REST calls return HTTP 410. Old integrations pinned to retired API versions stop working. Check which version your integration calls, and update it on a schedule.

Hitting the daily limit with chatty polling. An integration that polls constantly can use up the org’s allocation, and then every other connected app fails too. Use change events, batch where you can and alert on usage.

Duplicate records from loose matching. Matching on a name or an email address creates duplicates, because people type “Globex Corp.” and “GLOBEX Corporation” and use more than one email. Store each system’s ID in the other and match on those.

The integration user’s permissions. An integration usually runs as a dedicated user. If that user cannot see a field or record, the integration may read blanks or fail on writes, and the cause is easy to miss. Give the integration user only the access it needs, and test with it, not with an administrator.

Two-way sync conflicts. When both systems can edit a record, they overwrite each other. Decide which system wins for each field and write it down. A common starting split:

RecordUsually owned byWhy
Account, opportunity, stageSalesforceSales works there
Invoice, tax, payment statusFinance systemFinance reports from it
Customer name and addressOne system, chosen up frontTwo editors overwrite each other

Change these where your business differs.

An expired or deleted app credential. If the app or credential behind the integration is removed, rotated or expires, the sync stops. Name an owner for it, record where it is stored and alert on any failed sign-in.

A sensible next step

Name the two systems you want connected and the one flow that costs you the most time, such as a won opportunity becoming an invoice. From that we can tell you whether an AppExchange app, a no-code tool, MuleSoft or a custom build fits, and if an app will do the job, we will say so.

For two systems, start with our systems integration service, from £5,000 (about $6,500). For an ERP and several other systems, our enterprise software integration work begins with an audit and plan from £4,000 (about $5,200).

Frequently asked questions

What are Salesforce integration services?

Salesforce integration services connect Salesforce to your other systems, such as finance, ecommerce, support or your own platform, so records move between them without retyping. A provider scopes the flows, builds them on an app, a no-code tool, an integration platform or Salesforce's APIs, tests them with messy data and usually supports them after go-live.

How much does a Salesforce integration cost?

Salesforce's own costs are licences, a Web Services API add-on at $25 per user per month on Pro Suite and MuleSoft if you use it. With us, connecting two systems starts from £5,000 (about $6,500) and a business-wide integration from £10,000 (about $13,000), at a fixed price agreed upfront. Support starts from £400 (about $520) a month.

What are the Salesforce API limits?

Salesforce sets a daily API request allocation for each org, shared by every connected app. On Enterprise Edition it is 100,000 plus 1,000 per Salesforce licence, so 15 licences give 115,000 requests per 24 hours. Unlimited and Performance editions get 100,000 plus 5,000 per licence. Salesforce allows some overage on paid orgs, but do not rely on it: queue calls and avoid chatty polling.

Can Zapier connect to Salesforce?

Yes. Salesforce is a premium app on Zapier, which means you need a paid Zapier plan (Professional, Team or Enterprise) to use it. Simple flows, such as a new lead creating a task elsewhere, suit it well. Custom matching rules, high volumes and two-way sync are where a custom build starts to pay off.

Do I need MuleSoft to integrate Salesforce?

Usually not. MuleSoft is Salesforce's integration platform and suits large estates with many systems and a team to run it. At the time of writing (November 2026), pricing starts at $2K a month billed yearly. A small or mid-sized business with a few systems is typically better served by an app, a no-code tool or a custom build.

Want to build something like this?

Book a free 30-minute consultation and we'll help you find where automation pays off.

Book a consultation Get a free quote

Keep exploring

Back to all insights

Book a free call with Vivian

COO and co-founder · London

Request a callback

Leave your name and number and we'll call you back.