Key takeaways
- Point-to-point API integrations are the fastest way to connect two systems, but they become hard to manage as the number of connections grows.
- Event-driven options such as Platform Events and Change Data Capture reduce polling and keep systems in sync in near real time.
- Middleware and MuleSoft make sense when you have many systems, complex transformations or strict monitoring needs.
- Plan for API limits from the start. Enterprise orgs begin with 100,000 API requests per rolling 24 hours, plus an allocation per license.
Salesforce rarely lives alone. Sales teams need ERP order history, finance needs invoices to sync, marketing needs leads from ad platforms, and support needs billing status. How you connect these systems determines how reliable your data is and how expensive it is to change later.
The building blocks Salesforce gives you
| Option | Direction | Good for |
|---|---|---|
| REST API | Into and out of Salesforce | Real-time create, read, update and delete from other applications |
| SOAP API | Into and out of Salesforce | Legacy enterprise systems that prefer strongly typed WSDL contracts |
| Bulk API 2.0 | Into and out of Salesforce | Large data volumes processed asynchronously |
| Platform Events | Both | Publishing and subscribing to business events in near real time |
| Change Data Capture | Out of Salesforce | Streaming record changes to external systems without polling |
| Apex callouts | Out of Salesforce | Calling external APIs from triggers, flows or scheduled jobs |
| Salesforce Connect | Into Salesforce (virtual) | Viewing external data as external objects without copying it |
Pattern 1: point-to-point
The simplest pattern connects two systems directly. Your billing platform calls the Salesforce REST API to update an account, or an Apex callout sends a closed opportunity to your ERP. Point-to-point integrations are quick to build and perfectly sensible for one or two connections.
The trouble starts when every system talks to every other system. Each new connection adds code to maintain, credentials to rotate and failure points to monitor. If a change in one system requires updates in five integrations, you have outgrown point-to-point.
Pattern 2: event-driven
Instead of systems constantly asking Salesforce whether anything has changed, Salesforce can publish events when something happens. Change Data Capture streams record changes, and Platform Events let you define your own business events, such as Order Approved. Subscribers react when the event arrives. This reduces API consumption and keeps data fresher than scheduled polling.
Pattern 3: middleware or an integration platform
Middleware sits between your systems, handling transformations, routing, retries, queueing and monitoring in one place. Options range from lightweight integration-platform-as-a-service tools to enterprise platforms. MuleSoft, owned by Salesforce, is the best known in the Salesforce world, with its Anypoint Platform for API-led connectivity and MuleSoft Composer for simpler, no-code flows between common applications.
Middleware earns its cost when you have many systems, complex data mapping, strict uptime requirements, or a need to reuse the same APIs across several projects. For a single, simple sync it is usually more platform than you need.
API limits you need to plan for
Salesforce allocates API requests per rolling 24-hour period. Paid editions such as Enterprise start at 100,000 requests, plus an additional allocation per user license, which for full Salesforce licenses is 1,000 requests each. Other license types receive smaller allocations. You can see current consumption on the System Overview page in Setup, and additional capacity can be purchased.
Integrations that poll every minute, update records one at a time, or loop through large data sets can consume this allowance quickly. Use composite and bulk requests, event-driven patterns and sensible schedules to keep usage healthy.
How to choose
- One or two systems, simple data: direct REST integration or Apex callouts, with proper logging.
- Large nightly volumes: Bulk API 2.0 with upserts on external IDs.
- Near real-time sync to several consumers: Change Data Capture or Platform Events.
- Many systems, complex transformations, central monitoring: middleware or MuleSoft.
- Data that should stay in its source system: Salesforce Connect and external objects.
Five things every integration needs, whatever the pattern
- A clear system of record for each data element, so two systems never fight over the same field.
- External IDs for matching records across systems.
- Error handling with retries and a place where failures are logged and visible to someone.
- A dedicated integration user with only the permissions it needs.
- Documentation of what moves, when and why, kept up to date.
Frequently asked questions
Do we need MuleSoft to integrate Salesforce?
No. Many integrations work well with Salesforce’s own APIs and events. MuleSoft and other middleware make sense when the number of systems or the complexity grows.
Which Salesforce editions include API access?
API access is included in the higher editions used by most businesses. Lower tiers may restrict it or offer it as an add-on, so confirm API access before choosing an edition if you plan to integrate.
What is the most common integration mistake?
Unclear ownership of data. When two systems can both update the same field, records drift out of sync and users stop trusting either system.
