What we do
Tools
Industries
Department
How we workLet's talk →
Home/Salesforce
Salesforce integration

Salesforce Integration: Pick the Route Before You Pick the Tool

Most Salesforce integration projects stall on a question nobody asked at the start: should the other system's data be copied into Salesforce, or only shown there? Settle that, then choose between an AppExchange app, an integration platform, or a build against Salesforce's own APIs.

Where Salesforce stops

Reps export reports to Excel to line them up against invoices, inventory and shipping data that lives in other systems.

Stuck on Salesforce? Let's solve it →
Three routes in

An AppExchange app from the other vendor. Quickest when one exists and its field mapping matches the way you work. Look there first.

An integration platform such as Zapier, Make or MuleSoft. Fine for event handoffs between a few systems, as long as the logic stays simple or someone owns it.

A custom integration against the REST, Bulk and event APIs. Right when the rules are yours: who gets the lead, when an order may sync, what counts as the same customer.

Which route suits the job in front of you

What Salesforce needs to do Usually the right route Check this first
Turn won opportunities into invoices in QuickBooks or NetSuite The vendor's connector if your products map one to one. Custom if you sell bundles, tiered prices or terms that don't fit a single product line. Whether the connector creates a new customer in the books when the account name is spelled slightly differently.
Show live stock, account balance and tracking on the account A lookup panel that asks the ERP or shipping system each time, not a nightly copy. How fresh the number has to be. Stock that is a day old gets promised to a customer who then waits.
Give reps the ticket history from Zendesk or Freshdesk The help desk's own Salesforce app, usually. Whether reps see open tickets on the account itself, or only a link out to the help desk.
Land web or Shopify orders as accounts and opportunities An integration platform at low volume. Custom once matching rules start to matter. What happens when an existing customer orders with a new email address.
Pass marketing leads from HubSpot HubSpot's own Salesforce connector. Which system wins when the same field gets edited in both on the same day.

Copy the data into Salesforce, or show it live?

Copy

Synced into Salesforce fields

  • Usable in reports, list views and Flow.
  • Still there when the other system is down.
  • Can go stale between sync runs.
  • Costs storage and API calls on every run.
Show

Looked up live on the record

  • Always the current number, with nothing to reconcile.
  • Can't drive reports or automation unless it's also stored.
  • Depends on the other system answering quickly.
  • Salesforce Connect, a paid add-on, is Salesforce's own way to do this. A custom panel is the other.

Good builds usually do both. Copy the handful of fields automation needs, such as payment status or last order date, and show the rest live. Copying last order date and contract end date is also what lets Salesforce flag a customer who has stopped ordering, or a renewal coming up, without anyone checking the ERP.

Where Salesforce integrations go wrong after launch

Two accounts for one customer

How you'll know: A "Drake Corp" created by the web shop and another created by a rep, each with half the history.

Fix: Match on a stable ID held in an external ID field on both sides, never on the company name.

Fields that flip back and forth

How you'll know: A phone number or address changes, then changes back an hour later.

Fix: Decide which system owns each field. The other side reads it and never writes it.

The daily API limit runs out

How you'll know: The integration stops in the afternoon with REQUEST_LIMIT_EXCEEDED and catches up overnight.

Fix: React to changes instead of polling every few minutes, and move big loads to the Bulk API.

Connected as one employee's login

How you'll know: Everything breaks the week that person leaves or resets their password.

Fix: Run it as a dedicated integration user with only the permissions it needs.

Failures nobody hears about

How you'll know: Someone notices in a pipeline meeting that orders stopped arriving on Tuesday.

Fix: Log every failed record, retry it, and alert a named person when retries give up.

A building materials distributor answering a contractor in one screen

15 sales reps on Salesforce, with NetSuite for ERP and accounting.

Before

A contractor calls: 200 units of product X to the downtown site by Friday, what's the balance on the account, and did the last shipment arrive?

The rep puts them on hold, checks stock in one NetSuite screen, the balance in another, tracking in the shipping portal, then comes back to Salesforce to log the call. Five minutes for a one-minute conversation.

After

The account in Salesforce shows a panel with stock and delivery date for product X, the outstanding balance and last payment, and the last shipment signed for on site.

The rep places the order from that screen. It syncs to NetSuite, the invoice is created, the label is made in ShipStation, and the contractor gets a confirmation email.

One tab, about a minute, and nothing left to retype afterwards.

Once reps have it, customers usually ask for it too

The data that ends up on a Salesforce account is the same data customers phone in to ask about. After the sales side works, the next step is often a portal where they check orders, invoices and tickets themselves. How we build self-service portals →

The same connections can put sales context in front of support agents, and can take orders online without a rep in the middle. Support with the full account picture → · Selling online from the same data →

Questions people ask

What is a Salesforce connected app, and do we need one?

A connected app is how an outside system signs in to Salesforce through OAuth instead of a shared password. Salesforce now turns off creating new connected apps by default and points new integrations to External Client Apps, which do the same job. Connected apps you already have keep working. Any integration we build authenticates through one of the two, never a person's login.

Is Zapier enough to connect Salesforce to our other tools?

For a few simple, low-volume triggers, it can be. Once there's real logic, like routing a lead by deal size or holding a sync until an order is approved, it's usually better built against Salesforce's API directly, with logging and retries. That's the kind of Salesforce integration n-frames builds.

How do I connect Salesforce to QuickBooks or NetSuite?

Start with the connectors listed on AppExchange and check them against your products and pricing. If every product maps to one item in the books, a connector is often enough. Bundles, custom pricing and partial shipments are where a custom sync earns its keep. See Salesforce and NetSuite for the details on that pair.

What are Salesforce API limits, and will an integration hit them?

Salesforce caps API requests per org in a rolling 24 hours, and the cap depends on your edition and number of licenses. You can see current usage in Setup under Company Information. An integration that polls every minute can burn through it. One that reacts to changes and uses the Bulk API for large loads rarely does.

Does HubSpot integrate with Salesforce?

Yes. HubSpot has its own Salesforce connector that syncs contacts, companies and deals both ways. Most teams running both use it for the marketing-to-sales handoff. If you're picking one over the other instead, see HubSpot vs Salesforce.

Let's talk

Make Salesforce the one screen your reps need

n-frames builds Salesforce integrations for sales teams that run on more than a CRM: live stock and balances on the account, closed opportunities that create the order and invoice, and syncs that log and retry instead of failing quietly. If the bottleneck turns out to sit outside Salesforce, we work on that instead.

Put my ERP on the account record →

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.