Salesforce Integration Patterns for Growing Companies

TL;DR: Salesforce documents six core integration patterns, from request and reply to data virtualization, and a growing company rarely needs all of them on day one. Start with a few well-governed API integrations, move record changes onto events as volume rises, and put an API or agent layer in front of Salesforce once many systems and AI agents need the same data.

Most guides list the patterns and stop. The harder question for a scaling team is sequencing: which pattern to adopt at which stage, and what to retire before it breaks. That is what this guide covers, including the new agent layer Salesforce opened with Headless 360.

What are Salesforce integration patterns?

An integration pattern is a reusable answer to a recurring question: how data or a process should move between Salesforce and another system, and how fast. Salesforce's Integration Patterns and Practices guide names six:

• Request and reply: Salesforce calls a remote system and waits for the answer.
• Fire and forget: Salesforce sends a message and carries on without waiting.
• Batch data synchronization: large record sets move on a schedule.
• Remote call-in: an external system creates, reads or updates Salesforce data.
• UI update based on data changes: the screen refreshes when the underlying records change.
• Data virtualization: external data is shown in Salesforce without being stored there.

Which integration pattern fits which job?

• A credit check or price quote before a user can continue: request and reply.
• An order is placed and the ERP needs to know: fire and forget, ideally through events.
• A nightly finance or warehouse load: batch synchronization with Bulk API 2.0, which Salesforce's architects describe as well suited to extracting thousands of records efficiently.
• A web store or portal writing leads and cases: remote call-in through the REST API.
• Large external tables users only need to read: data virtualization with Salesforce Connect, so nothing is replicated.

For ERP-heavy estates, our guide to Salesforce and SAP integration patterns for manufacturers walks through these choices with order, pricing and inventory flows.

Point-to-point, hub or API-led: which architecture should a growing company choose?

Let the number of systems and consumers drive the architecture, not the size of the ambition.

1. A handful of systems: direct point-to-point integrations are fine, as long as each has an owner, a dedicated integration user and logging.
2. The same data needed in several places: introduce a hub or middleware, so one change does not ripple through every connection.
3. Several teams consuming the same data: move to API-led connectivity, where system, process and experience APIs separate concerns and get reused.

We cover the scaling logic in more depth in Salesforce integration architecture patterns that actually scale.

When should you move to event-driven integration?

Move when polling and chained callouts start to hurt: duplicate updates, timeouts, or downstream systems that always lag behind. Salesforce's event-driven architecture decision guide is clear on the tools:

• Change Data Capture publishes record creates, updates, deletes and undeletes to other systems.
• Platform Events carry custom payloads you define, published from APIs, Apex or Flow.
• Pub/Sub API is the recommended choice for any new publish and subscribe integration.
• Events can be replayed for three days, and each payload is capped at 1 MB.

The same guidance steers new work away from outbound messages and PushTopic. If you still run them, plan the migration before volume forces it.

What is headless MCP, and what does Headless 360 change?

Headless MCP means reaching Salesforce data, logic and workflows through APIs and Model Context Protocol servers instead of the browser UI. Salesforce announced Headless 360 at TDX on April 15, 2026, exposing platform capabilities as APIs, MCP tools and CLI commands, with more than 60 new MCP tools at launch. In August 2026 it expanded the program with a Headless 360 MCP Server and a Data 360 MCP Server that agents on Agentforce, Claude, ChatGPT and Cursor can use.

For integration teams this adds a new consumer: AI agents that discover and call capabilities at runtime. They need the same discipline as any integration, with least-privilege users, audited actions and clear ownership. Our guide to connecting AI agents to Salesforce safely with MCP covers the controls. Tekunda is first and only in headless CRM plus MCP, and first to run agent-to-agent (A2A) and SWARM orchestration in production, so this is work we already run for clients.

What do growing companies get wrong?

• Replicating everything. Salesforce's data integration decision guide says to avoid unnecessary replication. Virtualize or call APIs where data can stay put.
• Sharing a human login. Use a dedicated API-only integration user and External Client Applications for authentication.
• Treating admin tools as strategy. Data Loader and the Salesforce CLI are for data stewardship, not a base for integrations.
• No change control on integration metadata. Named credentials, event definitions and field mappings drift fast. Treat them like code, as covered in metadata governance for growing orgs and teams.

How does Tekunda help growing companies integrate Salesforce?

Tekunda is a certified Salesforce SI, ISV, PDO and Agentforce partner, and an Anthropic (Claude) partner. We design an integration roadmap that fits your current stage, then extend Salesforce with event-driven flows, reusable APIs and MCP-connected agents as you grow. See how we approach Salesforce integration, or start from the Tekunda homepage.

FAQ

What is the simplest Salesforce integration pattern to start with?

Request and reply, where Salesforce calls another system and waits for the response. It suits low-volume lookups but should not carry bulk loads.

Do I need MuleSoft to integrate Salesforce?

No. Native APIs, events and Salesforce Connect cover many needs. Middleware such as MuleSoft pays off when many systems and teams share integrations, and it needs its own license.

What is the Headless 360 MCP Server?

It is a Salesforce MCP server that lets authorized AI agents discover and invoke Salesforce capabilities through the open Model Context Protocol. Check Salesforce's documentation for its current release status.

Should new integrations use outbound messages?

No. Salesforce recommends the Pub/Sub API for new publish and subscribe work and does not plan further investment in outbound messaging.