Salesforce integrations for the data that doesn't live in Salesforce.
Salesforce holds your pipeline. Orders, invoices, stock, calls and product usage usually live somewhere else. Our Salesforce integration services connect those systems to Salesforce so reps and managers see the whole customer, and the other systems hear about what happens in the CRM.
On this page
What we connect Salesforce to
- ERP and accounting: NetSuite, QuickBooks, Xero and Microsoft Dynamics 365, so a closed deal becomes an order and an invoice without re-keying.
- HubSpot, for companies that run marketing there and sales in Salesforce.
- Online stores such as Shopify, so orders and customers reach the account record.
- Phones and messaging: Twilio, Microsoft Teams and Slack.
- Data warehouses and your own databases.
- Older systems that can only exchange files, through a scheduled, checked file exchange.
Pick the right Salesforce integration tool
Salesforce offers several ways in, and picking the wrong one makes an integration slow or fragile.
| Tool | Good for | Watch out for |
|---|---|---|
| Change Data Capture and Platform Events | Telling other systems the moment a record changes | Events need a subscriber that is running and can catch up after downtime |
| REST and Composite API | Creating and updating individual records | Every call counts against the daily API allowance |
| Bulk API 2.0 | Loading or exporting large volumes, such as a migration or a nightly sync | Jobs run asynchronously, so errors come back later and must be read |
| Salesforce Connect | Showing data from another system inside Salesforce without copying it | Performance depends on the other system's API |
| MuleSoft or another integration platform | Many systems, and an IT team that already runs one | Licensing cost, and logic spread across tools |
We use whichever fits, and often two together: events for changes as they happen, and bulk jobs for history and reconciliation.
The daily API allowance
Salesforce publishes its API allocations. An Enterprise Edition org starts at 100,000 API requests per 24 hours, plus 1,000 for each Salesforce user license. An org with 15 licenses gets 115,000. Every integration and every installed app draws from that same allowance.
An integration that asks Salesforce "has anything changed?" every minute spends that allowance on empty answers, and the calls it wastes can crowd out the app your sales team relies on. We subscribe to change events, write in batches, and show you the API consumption in the runbook, so you can see it before it becomes a support ticket.
Agentforce or a custom AI agent
Salesforce now sells AI agents inside the CRM. Its published prices are $2 per conversation, or Flex Credits at $500 per 100,000 credits, with a standard action using 20 credits (about $0.10) and a voice action 30. Per-user Agentforce add-ons for Sales and Service are listed at $125 per user per month.
Agentforce is a good fit when the work starts and ends in Salesforce and your data can be processed there. A custom agent tends to fit better when the process runs across several systems, when data must stay on your own infrastructure, or when volume makes per-action pricing add up. We compare the options with real numbers in our guide to what AI agent development costs.
How we build a Salesforce integration
- A field ownership map comes first: for every field that moves, which system is the source of truth.
- We build and test in a Salesforce sandbox, and nothing reaches production until the test runs pass.
- Each change is applied once, even if it arrives twice, and failures go to a review queue with the reason attached.
- Logic about Salesforce data can live in Salesforce, in Flow or Apex. Logic that coordinates several systems lives in code you own, in your repository.
- You get a runbook and a named engineer who supports it.
Salesforce work we have done
For a B2B services firm we built an AI calling agent that qualifies inbound leads and handles callbacks, connected to Salesforce, HubSpot, Twilio, Microsoft Teams and Slack, so every qualified lead and callback lands in the CRM. Read the case study.
What it costs
Connecting one system to Salesforce in one direction is a small project. Two-way sync with an ERP, or a migration of several years of history, is a larger one. We fix the price once the field ownership map exists. For market figures, see what custom software development costs. If you are weighing Salesforce against building your own, see what a custom CRM costs.
The Automation Audit
One workflow you name, mapped end to end, with the arithmetic done before anyone writes code.
- Scope
- One workflow you choose, traced end to end, including the steps nobody documented.
- Duration
- Two weeks, fixed.
- Fee
- Fixed, and quoted in full before we start. No hourly drift.
- You get
- A written map: what can be automated, what it would save in hours, what building it would cost, and what we would leave alone.
- You keep it
- The map is yours whether or not you hire us to build anything.
And if the audit shows the automation will not pay for itself inside twelve months, we will tell you, and we will not quote the build.
Questions we get asked about Salesforce integrations
Can you work alongside our Salesforce admin or consultant?
Yes. Your admin or Salesforce consultant keeps the org configuration, and we build and support the integration. We agree who changes what before work starts.
Do you write Apex?
When the logic belongs in Salesforce, yes, along with Flow where a Flow is easier for your admin to maintain. We keep logic that spans several systems outside Salesforce, so it can be tested and changed without a deployment to the org.
Can you migrate us into or out of Salesforce?
Yes. A migration uses the same field map and matching rules as an integration, runs through the Bulk API, and ends with a reconciliation you sign off.
What if we are close to our API limit already?
We measure current consumption before we design anything, and the design is built to fit inside what is left. If the only fix is more API capacity, we tell you before you pay for a build.
