Salesforce Integration: Types, Options, Patterns, and Best Practices

Salesforce integration connects Salesforce to the other systems your business runs on. Customer records, emails, meetings, and orders then move between them automatically instead of by copy and paste.

The gap is bigger than most teams think. The average enterprise now runs 957 applications, and only 27% of them are integrated, according to Salesforce's 2026 Connectivity Benchmark Report. That figure comes from a Vanson Bourne survey of 1,050 enterprise IT leaders in nine countries, fielded in October and November 2025.

This integration guide covers how it all works: the types and architectures to choose from, the APIs behind them, and the six official patterns. It ends with the practices that keep a build running long after launch.

What Is Salesforce Integration?

Salesforce integration is the process of connecting Salesforce, your customer relationship management (CRM) platform, with the other applications your teams use. You'll also see it written as "Sales Force integration." It means the same thing.

A typical company keeps customer information in a dozen places: an inbox, a calendar, a finance system, a marketing tool, a support desk. Each one holds a piece of the customer record that never reaches Salesforce. Salesforce integration closes that gap.

Instead of managing siloed tools and copying data by hand, integration ensures that:

• Records update automatically in every connected system
• Sales, marketing, support, and operations work from one shared customer record
• You cut errors, remove double entry, and speed up handoffs

How does it work? One system authenticates to the other, usually with OAuth. It then maps fields between the two, sends or requests data through an API, and handles whatever fails.

Most projects move one of three things: data, a process, or a view of outside information. We'll break those types down below.

Why Salesforce Integration Matters

Disconnected systems cost time before they cost anything else. In the same survey, IT teams reported spending 36% of their time designing, building, and testing custom integrations.

By connecting Salesforce with your email, calendar, marketing tools, or ERP, you unlock cleaner data and a faster path from lead to closed deal. The more your teams use Salesforce, the more that matters.

A well-planned CRM integration pays back in four ways:

• It removes data silos. Every team sees the same current customer record, wherever they work.
• It cuts admin work. Reps stop switching tabs and typing the same update twice.
• It improves decisions. Complete CRM data turns forecasts and reports into actionable insights.
• It supports workflow automation. A new lead, a closed deal, or a support case can trigger the next task on its own.

Here's a common case. A rep schedules a customer meeting in Outlook. Without a connection, that meeting may never reach Salesforce, so the forecast review happens with half the story.

With an inbox tool such as Cirrus Insight, the meeting, the email thread, and the attendees are logged to the right record without manual effort.

Types of Integration in Salesforce

Salesforce's own architects sort projects by two questions: what moves, and when. Those answers decide almost every design choice that follows.

There are three types of Salesforce integration by what moves:

Timing is the second question:

• Synchronous (real-time): The caller waits for an answer. Use it when a user is waiting on screen.
• Asynchronous: The caller sends a message and moves on. Use it when the work can finish in the background.
• Batch: Data moves on a schedule in large sets. Use it for volume that doesn't need to be current to the minute.

Direction matters too. Outbound means Salesforce calls another system. Inbound means another system calls Salesforce. Many projects need both, so treat two-way sync as a design decision with its own conflict rules.

Salesforce Integration Architectures

Your integration architecture defines how your systems connect and communicate with Salesforce. The four models below suit different company sizes and use cases.

Point-to-Point Integration

This is the simplest model. Each system connects directly to Salesforce.

It's quick to build and fine for one or two links, such as a single calendar tool. Five systems that all need to talk to each other can require up to 10 separate connections, and each one needs credentials, monitoring, and upkeep.

Best for: Small teams or a single, well-defined connection.

Hub-and-Spoke Integration

This model adds a central hub, usually middleware, that manages communication between Salesforce and every other system. Each app connects once to the hub.

You get one place to map fields, monitor traffic, and handle errors. Adding a system doesn't touch the others.

You're paying for middleware such as MuleSoft, Boomi, or Zapier, and someone has to run it. The hub is also a single point of failure.

Best for: Mid-size and larger organizations with multiple applications.

Enterprise Service Bus (ESB)

An ESB is a more advanced take on the hub. A message bus routes, transforms, and orchestrates data between systems.

It supports high-volume, two-way exchange and complex transformation rules. It's also the heaviest option to set up and manage. For a company with a handful of SaaS apps, it's overkill.

Best for: Large companies connecting dozens of systems, including on-premise ones.

Event-Driven Architecture

Here, systems communicate through events, such as a lead being created or an opportunity closing. One system publishes the event, and any number of others subscribe to it.

That design gives you real-time updates without constant polling, so you make fewer API calls. It takes more setup, using Platform Events or Change Data Capture. Failures are also harder to trace than in a simple request.

Best for: Real-time automation and loosely coupled services.

Salesforce Integration Options: Native Apps, Middleware, or Custom Code

Of the Salesforce integration tools available, most fall into four groups. They differ in who builds the connection and who maintains it.

Salesforce app integration through AppExchange is the fastest route for most teams. Our guide to the best Salesforce apps covers popular picks.

Middleware products are often sold as iPaaS platforms. If you want a Salesforce integration platform from Salesforce itself, that's MuleSoft Anypoint. Low-code options give admins drag-and-drop tools, so not every connection needs a developer.

Choosing the right Salesforce option comes down to three business needs: how many systems are involved, how fresh the data must be, and who will maintain it.

Our rule of thumb is to buy before you build. If a maintained app or prebuilt connector already does the job, a custom build rarely pays back the upkeep. Save custom code for the logic that makes your business different. The best tools are the ones someone on your team can maintain.

Salesforce API Integration: The APIs That Do the Work

Every option above ends in the same place: a Salesforce API. Even a no-code app is making requests on your behalf. The Salesforce Developer Center documents each one in full.

If you're building a custom connection using Salesforce APIs, plan around limits early. Enterprise Edition orgs get 100,000 API requests per 24 hours plus 1,000 for each Salesforce license. An Enterprise org with 50 Salesforce licenses has 150,000 requests a day, and every integration uses part of that pool.

Bulk jobs have their own ceiling of 150 million records per rolling 24 hours. Apex allows 100 callouts per transaction, with a 120-second cumulative timeout.

The API comes standard in Enterprise, Unlimited, Performance, and Developer Editions. Professional Edition needs it as a paid add-on.

Salesforce Integration Patterns

Salesforce documents six integration patterns. They're the common patterns behind almost every build, and knowing them makes vendor conversations faster.

One thing trips people up. The names describe direction from Salesforce's side. In request and reply and in fire and forget, Salesforce makes the call. Remote call-in is the reverse.

Request and Reply

Salesforce calls another system and waits for the answer before continuing. Use it when a user needs the result on screen right away.

Example: A rep opens an account, and Salesforce calls the billing system to show current invoice details.

Trade-off: The two systems are tightly coupled, so a slow billing system means a slow Salesforce page.

Typical tools: External Services, Apex callouts with Named Credentials, or an HTTP Callout action in Flow.

Fire and Forget

Salesforce sends a message to another system and doesn't wait for a reply. Use it when speed matters more than instant confirmation.

Example: An opportunity is marked closed-won, Salesforce publishes a platform event, and the ERP creates the order in the background.

Trade-off: You need your own way to confirm delivery and retry failures.

Typical tools: Platform Events, Change Data Capture, or the Pub/Sub API.

Batch Data Synchronization

Data is collected over time and moved in scheduled sets, in either direction. Use it for large volumes that don't need to be current to the minute.

Example: A nightly import of marketing leads or e-commerce orders into Salesforce.

Trade-off: Data is stale between runs, and two systems can edit the same record in the gap.

Typical tools: Bulk API 2.0, an ETL tool, or Data Loader for one-off jobs.

Remote Call-In

Another system calls Salesforce to create, read, update, or delete records. Use it when the outside system owns the trigger.

Example: A web app checks a Salesforce record to confirm a customer's eligibility before completing a signup.

Trade-off: Every call counts against your daily allocation, so chatty apps need watching.

Typical tools: The REST or SOAP API, or a bulk job for volume.

UI Update Based on Data Changes

The Salesforce screen refreshes on its own when the underlying data changes. Use it when users act on live information, such as a case queue or a payment status.

Example: A payment clears in the finance system, and the open opportunity page shows the new status without a reload.

Trade-off: It only helps users who have the record open.

Typical tools: Platform Events or Change Data Capture.

Data Virtualization

Salesforce reads outside data in real time and displays it without storing a copy. Use it when the data is large, changes often, or has to stay in its home system.

Example: Years of order history stay in the ERP but appear as a related list on the account.

Trade-off: Speed depends on the source system, and some reporting features work differently than they do on native records.

Typical tool: Salesforce Connect.

Common Salesforce Integrations: A List by System

Here's the Salesforce integrations list most teams work through, grouped by the system on the other end. The best Salesforce integrations remove a specific manual step your team repeats every day. Start with the system where that step hurts most.

ERP Systems (NetSuite, SAP, Oracle)

Purpose: Keep customer, order, and billing data in step between sales and finance.

This connection usually runs both ways. Closed deals flow out as orders, and invoice and payment status flow back. Most teams use batch jobs for master data and events for orders.

Salesforce integration with ERP solutions is also where field mapping takes the longest. The two systems rarely define "customer" the same way.

What you get: One customer record that holds the same data across sales and finance, automated order updates, and quote-to-cash visibility.

Marketing Platforms (HubSpot, Marketo, Mailchimp)

Purpose: Share campaign and lead data so marketing and sales work the same funnel.

Leads and engagement data flow in. Lifecycle stage and closed revenue flow back for attribution. Decide which system owns lead status before you connect them, because two-way sync without an owner creates update loops.

What you get: Lead scoring within Salesforce, closed-loop campaign reporting, and a faster handoff to sales.

Customer Support Tools (Zendesk, ServiceNow)

Purpose: Give support and sales the same view of each account.

Tickets attach to the account record, so a rep knows about an open escalation before a renewal call.

What you get: Full context for both teams, faster resolution, and cleaner tracking of service-level agreements (SLAs).

Email, Calendar, and Collaboration Tools (Gmail, Outlook, Slack)

Purpose: Capture the daily conversations that never reach the CRM on their own.

This is the connection reps feel most, because it removes manual data entry from every email and meeting. You can start with the native Salesforce options or add a third-party tool for deeper controls. Our guides compare both for Salesforce Outlook integration, Salesforce Gmail integration, and Salesforce Google Calendar integration.

Cirrus Insight is our product in this category. It connects Gmail and Outlook to Salesforce so your team can:

• Log emails, attachments, and meetings to the right lead, contact, or custom object with Salesforce email sync
• View and edit records from the inbox with the Salesforce sidebar
• Keep calendars aligned in both directions, including recurring events
• Reuse proven messages with email templates

E-Commerce and Payment Tools (Shopify, Stripe)

Purpose: Bring order and payment data into Salesforce for follow-up.

Orders and payment status flow in, so sales and success teams can act on real purchase history.

What you get: Upsell and cross-sell based on purchases, automated follow-ups, and order status on the account.

Salesforce Website Integration

Website integration usually starts with Web-to-Lead, a built-in form generator that creates a lead from each submission. It's included and quick to set up.

There's one limit to know: 500 Web-to-Lead requests per day. Past that, extra submissions are emailed to your default lead creator instead of becoming leads. Busier sites use a form tool or marketing system that posts through the API.

Scheduling pages count too. Our Smart Scheduler routes each booking to the right rep's calendar and pushes UTM data to Salesforce.

Salesforce to Salesforce Integration

Companies with more than one org, often after an acquisition, need org-to-org integration: Salesforce on both ends.

The old Salesforce-to-Salesforce feature has reached end of life, according to Salesforce's data integration decision guide. Current options include the native APIs, Change Data Capture, Salesforce Connect with the cross-org adapter, MuleSoft, and Data 360.

Pick by need. Choose Salesforce Connect to view another org's records without copying them. Use events or an API approach when both orgs must store the data.

AI-Driven Salesforce Integration: Agents, MCP, and Data 360

AI agents are the newest reason to integrate, and the newest thing to connect. An agent can only act on data it can reach.

In Salesforce's 2026 survey, 50% of AI agents ran in silos instead of inside a connected multi-agent system. And 82% of IT leaders named data integration as one of their biggest challenges when using AI.

Three developments matter for planning:

• Hosted MCP servers. Salesforce made hosted Model Context Protocol servers generally available on April 29, 2026, for Enterprise Edition and above. They expose your org's data, flows, and Apex actions to AI clients, and every transaction runs with the signed-in user's permissions.
• Agentforce. Salesforce's agent platform works on the same records and automation your connected tools feed. Gaps in Salesforce data become gaps in what an agent knows.
• Data 360. Formerly Data Cloud, it's the layer Salesforce's architects recommend when you need to unify records from many sources.

Our take: AI-powered features don't change the fundamentals. An AI-driven workflow is only as good as the activity data underneath it, so fix the plumbing first.

Salesforce Integration Best Practices

These eight habits apply to any integration solution, from a single app to a multi-system program.

1. Start with the process. Write down what triggers the data flow, which system acts, and who needs the result. An integration strategy built around a tool usually automates the wrong step.
2. Name a source of truth for every shared field. When two systems can edit the same field, one has to win. Decide per field, and set conflict rules before you turn on two-way sync.
3. Give each connection its own user. Salesforce includes five free Salesforce Integration user licenses in Enterprise, Unlimited, and Performance Editions. Most integrations in Salesforce should run through a dedicated user with only the permissions they need.
4. Use current authentication. As of Spring '26, new connected apps can't be created by default. Build new connections on External Client Apps with OAuth, and keep credentials in Named Credentials, never in code.
5. Design for limits and volume. Check your daily allocation before integrating Salesforce with a chatty tool. Salesforce recommends Bulk API 2.0 for any operation above 2,000 records. Prefer events to polling.
6. Plan for failure. Networks drop and systems go down. Log every failed message, retry with a delay, and use external IDs with upsert so a retry can't create duplicates. Our Salesforce data management guide covers duplicate control in depth.
7. Test with real volume in a sandbox. A job that works with 50 test records can fail with 50,000. Load production-size data, and test the failure paths too.
8. Monitor and document. Assign an owner and track error rates. Keep a one-page record of every connection: systems, fields, direction, schedule, and contact. Documented connections are easier to manage when the person who built them moves on.

Salesforce Integration Services: When to Bring In a Partner

You don't always need outside help. A single AppExchange app or a simple flow is within reach for most admins.

Integration partners earn their fee on harder projects. Think of a finance system rollout, several systems with shared data, a large migration, or a regulated industry such as financial services.

A Salesforce system integrator (SI) typically handles discovery, data mapping, architecture, the build, testing, and handover. Good Salesforce experts also tell you what to leave out.

Cost depends on scope more than on any list price. The main drivers are the number of systems, data volume and quality, real-time versus batch needs, middleware licenses, and ongoing support. Ask any partner for references on the specific system you're connecting, and for a design that will scale with your business.

Make Salesforce Integration Work Smarter With Cirrus Insight

Not every project needs middleware or code. If you mostly want to streamline how sales activity reaches the CRM, start in the inbox and calendar.

Cirrus Insight connects Gmail or Outlook directly to Salesforce. Your team can:

• Manage pipeline from the inbox with the Salesforce sidebar, on desktop and mobile
• Log emails, attachments, calendar events, and tasks to Salesforce automatically
• Match activity to custom objects with rule-based controls
• Book meetings and route leads without switching tabs
• Prepare for calls with Meeting AI, which delivers attendee and account research each morning
• Capture and transcribe calls with Conversation Intelligence

Where it stops: Cirrus Insight isn't an integration platform. It won't connect your finance system, billing tool, or data warehouse to Salesforce. For those, use the options above.

If you want Salesforce to be the place where every customer conversation lives, see how our Salesforce integration works.

Frequently Asked Questions About Salesforce Integration

What Systems Does Salesforce Integrate With?

You can connect Salesforce to almost any system that has an API. The most common are finance and ERP tools (NetSuite, SAP, QuickBooks), marketing platforms (HubSpot, Marketo), and support desks (Zendesk, ServiceNow).

Salesforce CRM also connects to email and calendar (Gmail, Outlook), collaboration tools (Slack, Microsoft Teams), and e-commerce and payment systems (Shopify, Stripe).

What Are Some Examples of Salesforce Integrations?

Three everyday examples: emails and meetings logged from Outlook to the right contact, closed-won opportunities creating orders in NetSuite, and web form submissions creating leads.

Others include support tickets appearing on account records and reports feeding a Salesforce to Google Sheets integration.

How Much Does It Cost to Integrate Salesforce?

There's no single price. Salesforce's own APIs are included in Enterprise Edition and above, and five integration user licenses are free.

Costs come from what you add: app subscriptions, middleware licenses, developer or partner time, and ongoing maintenance. A prebuilt app for one job costs far less than a custom multi-system build.

Which Salesforce Editions Include API Access?

Enterprise, Unlimited, Performance, and Developer Editions include it by default. Professional Edition can add it as a paid add-on.

Any app integrating with Salesforce needs that access, so check your edition before you buy a tool.

Do I Need MuleSoft to Integrate Salesforce?

No. MuleSoft is Salesforce's own middleware and suits large, multi-system programs.

Many teams connect their tools with Salesforce through AppExchange apps, Flow, or direct API calls. Others pick automation tools like Zapier or Workato. Choose MuleSoft when you need central governance across many systems.

What Is the Difference Between REST API and SOAP API in Salesforce?

Both read and write Salesforce records synchronously. REST uses standard HTTP methods and is the usual choice for web, mobile, and SaaS apps.

SOAP uses XML with a strongly typed contract and is common in older enterprise systems. For large data loads, use a bulk job instead of either.

Is Coding Required to Connect Salesforce to Other Apps?

No. AppExchange apps install with clicks, and Flow-based tools let admins build without code.

You'll need a developer for custom logic, unusual data models, or very high volume.

How Do I Keep an Integration Secure?

Give each connection a dedicated user with the minimum permissions it needs. Authenticate with OAuth through an External Client App, and store secrets in Named Credentials.

Review that access on a schedule, and remove any connection nobody owns.

What Is the Best Salesforce Integration for Sales Teams?

The best one is whichever removes your team's most repeated manual step. For most sales teams, that's email and calendar, because unlogged activity weakens every forecast and report.

We make a tool in that category. Test it against Salesforce's native options, and pick the one your reps will actually use.