Skip to contentIntroducing the Integration Factory
Back to Blog
Integration

What Is a Native Salesforce Integration, and Which Kind Should a SaaS Company Ship?

Manjot Singh

A native Salesforce integration, in Salesforce's own vocabulary, is an app that runs inside your customer's Salesforce org as a managed package. Most buyers use the phrase more loosely, to mean any integration your product ships and supports, so the first job is to find out which one a prospect is asking for. For a SaaS company, the managed package earns its cost when customers need your product inside the Salesforce screens they already work in. An API connector from your own product is usually enough when they only need data to move.

The question tends to arrive in an enterprise deal, when a buyer's admin asks whether your integration is "native" and who maintains it. Appnigma works with B2B SaaS teams on that exact decision. Our marketplace apps work puts "your product, inside Salesforce or HubSpot" as a native app with listing preparation and review support. Our done for you delivery builds and maintains the API integrations your customers ask for, with a named integration engineer. If you only need to know whether HubSpot's own connector counts as native, our post on whether HubSpot has a native Salesforce integration answers that.

Updated October 2026. Checked against the Salesforce Developer Limits guide, the Apex Developer Guide, the ISVforce Guide, the packaging guides and the Salesforce connector docs from Fivetran and Airbyte. The earlier version said native integrations scale better by design and keep data inside Salesforce, and that an ETL tool like Airbyte does the same job less well. None of that holds up as written. This update replaces those lines with what Salesforce documents about limits, security review, upgrades and data leaving the org.

Three things buyers mean when they ask for a native integration

The word "native" has three meanings in Salesforce deals, and a prospect's admin, their RevOps lead and your sales team may each mean a different one. Getting this wrong early is how a team ends up quoting a managed package build for a customer who only wanted a sync.

The first meaning is a connector built and supported by the software vendor, switched on in settings, as opposed to a third-party tool the customer wires up. Most "native integrations" pages that rank for the term use this meaning. The second is an integration your engineers build into your own product with Salesforce's APIs, so customers connect their org from your app. The third is Salesforce's meaning. Its go-to-market docs describe a Partner Application as "a native Salesforce managed package license or permission set license (PSL)," per AgentExchange product types. Salesforce's security review also lists a "Salesforce Native Solution" separately from a "Solution with External Web App or Service" and an "API Only" solution, per Required Materials.

A quick way to sort a request is to ask where the customer expects to use your product. If the answer is "on the Opportunity page" or "in a Salesforce tab," they mean the third meaning. If the answer is "I want our deals to show up in your app," they mean the first or second. For what goes into the package itself, see our explainer on what a Salesforce native app is and how one gets built.

How a managed package, an API connector and an ETL tool compare

A SaaS company can give customers a Salesforce integration in four common ways, and they differ less in features than in where the code runs and who pays for each customer's connection. The table compares a managed package, an API connector in your product, a unified API vendor and an ETL tool the customer runs.

RouteWhere your logic runsWhose API allocation it spendsDoes customer data leave SalesforceReview to list on AgentExchange
Managed package (native app)Inside the customer's org, plus your backend if it calls outThe customer org's, for any API calls it makesYes, if the package calls your backendRequired
API connector in your productYour serversThe customer org'sYes, it is read into your serversRequired, as a Salesforce Platform API solution
Unified API vendorThe vendor's cloud, on your accountThe customer org'sYes, through the vendorSame as an API connector
Customer runs an ETL toolThe ETL vendor's cloud, on the customer's accountThe customer org'sYes, into the customer's warehouseNot applicable to you

Two rows surprise most teams. The first is the API column, which is the same for every route. Salesforce states that "API calls made from installed managed packages, count against your org limit," and that limits apply to "the aggregate of all API calls made to the org in a 24-hour period," per API Request Limits and Allocations. The second is the review column. A package isn't the only route that needs one. Salesforce says managed packages and "Salesforce Platform API solutions" must "pass our security review" before distribution, per its security review guidelines.

What the package changes is the work that stays in the org. Apex triggers and flows inside the package read and write records under Apex governor limits instead of API requests. For the ownership side of these routes, including the customer's own iPaaS, our comparison of Salesforce iPaaS or a native app covers who maintains each customer's connection. For named vendors and prices, see Salesforce integration tools compared.

Is a native Salesforce integration more secure and scalable?

Partly. A native app gives you a security review and its own query limits once certified, but it doesn't keep data inside Salesforce if it talks to your backend, and it doesn't get unlimited capacity.

On security, the honest claim is about review, not about data staying put. Every outbound call from Apex has to be declared. The Apex Developer Guide says an external site "must be registered in the Remote Site Settings page, or the callout fails." The one exception is a callout that uses a named credential. That gives the customer's admin a visible list of where their data goes. The security review then follows the data. External endpoints are in scope when "Salesforce data is transferred to or from the endpoint," per Test Your Entire Solution. Salesforce adds that it "makes no guarantees regarding the quality or security of any Partner Application," in the same guidelines. The review is a bar you pass, not a warranty your sales team can quote.

On scale, a certified package gets real headroom. "Certified managed packages [...] get their own set of limits for most per-transaction limits," so the package gets its own 100 SOQL queries and 150 DML statements per synchronous transaction, per Execution Governors and Limits. Certified means passed the AppExchange security review. Before that, "namespaces in non-certified packages don't have their own separate governor limits." The catch is CPU time. The same page says the cumulative limit "doesn't affect limits that are shared across all namespaces, such as the limit on maximum CPU time," which is 10,000 milliseconds for synchronous Apex.

That shared CPU limit is the failure mode we see teams miss. Your trigger runs in the same transaction as the customer's own triggers, flows and other installed packages on that object. A package that ran fine in your test org can hit the CPU limit in a customer org with heavy automation on Opportunity. The fix is to move heavy work to asynchronous Apex, where the limit is 60,000 milliseconds. Then test in an org with the customer's level of automation, not a clean one.

What a native integration costs to maintain after install

The old pitch said a native integration evolves without redevelopment as Salesforce updates. In practice the vendor owns every update, and Salesforce's own release schedule creates some of the work.

You ship fixes to installed customers with push upgrades. Salesforce's push upgrade guide lets you "Select one, many, or all customer organizations to upgrade" and schedule the start. The same guide warns that a major upgrade "can impact existing functionality" in the customer's org. Customers may not notice at all. Salesforce says that apart from the new version number, "subscribers aren't notified of push upgrades." Customers can restrict pushes only if you enable customized push upgrades, and "It's not possible to block push upgrades on a patch version of a package," per Restrict Push Upgrades. Salesforce's best practices suggest waiting "3-4 weeks after a major Salesforce release" before pushing a major upgrade.

API versions also expire, for every route that calls Salesforce APIs. Salesforce supports each version "for a minimum of 3 years from the date of first release," per the REST API end-of-life policy. Versions 21.0 through 30.0 were retired in Summer '25. Versions 31.0 through 40.0 are "Deprecated and unsupported from Summer '27" and "Retired from Summer '28." An integration written years ago against an old version will need that update whether it is native or not.

The OAuth side has changed as well. "Starting in the Spring '26 release, you can't create new Connected Apps. Use ECAs instead," per Salesforce's guide to securing connected apps and ECAs. An ECA is an External Client App, the newer OAuth app type. Our comparison of a Connected App vs External Client App covers the migration.

Native integration vs an ETL tool like Airbyte or Fivetran

An ETL tool like Airbyte or Fivetran and a native Salesforce integration do different jobs, so choosing between them on features misses the point. ETL (extract, transform, load) tools copy a customer's Salesforce data into storage the customer runs, usually for analytics. Fivetran describes its connector this way. "We pull all the underlying data from Salesforce (SFDC) into a SQL-enabled environment," per its Salesforce connector docs. Airbyte's Salesforce source "supports reading both Standard Objects and Custom Objects from Salesforce."

Neither one puts your product inside Salesforce. Writing data back is a separate product in both cases. Fivetran Activations "uses reverse ETL (extract, transform, load) to activate data from data storage systems into your business tools," per its Activations overview. Airbyte's Salesforce destination is "available to Enterprise customers at an additional cost."

An ETL tool is the right answer when the request is really "we want your data next to our Salesforce data in Snowflake." In that case you don't build a Salesforce integration at all. You expose your data and let the customer's data team load it. Our guide to moving Salesforce data to BigQuery or Snowflake covers that pipeline.

The two do meet in one place, the customer's API allocation. Here is the arithmetic for one hypothetical customer, using only documented numbers. The daily allocation is "100,000 + (number of licenses x calls per license type)" requests, per API Request Limits and Allocations. Enterprise Edition counts 1,000 calls per Salesforce license. With 50 licenses that is 150,000 requests a day. Fivetran says it will "automatically postpone by one hour whenever 90% of the Salesforce API call quota has been consumed," which is 135,000 requests in that org. Your connector and the customer's ETL tool draw from the same 150,000. If your integration spends heavily, their warehouse sync is the one that pauses, and the ticket comes to you.

Mistakes SaaS teams make when they promise a native integration

  • Telling security reviewers data never leaves Salesforce. If the package calls your backend, the endpoint is registered in the customer's org and the review tests it.
  • Assuming a package has its own API allocation. It shares the org pool with every other integration the customer runs.
  • Testing only in a clean org. CPU time is shared with the customer's automation, so test with realistic triggers and flows on the same objects.
  • Pushing a major version right after a Salesforce release. Salesforce suggests waiting 3 to 4 weeks first.
  • Treating the listing as a sales channel. A listing supports discovery, but the review approves public listing and nothing more.
  • Building a package when the customer wanted analytics. If the ask is reporting in their warehouse, an ETL tool on their side may be the whole answer.

Who builds and maintains a native Salesforce integration

A SaaS company has three practical options. It can staff Salesforce developers in-house, hire a consulting partner for the build, or work with a team that builds and maintains the integration as a service. The deciding question is usually who fixes it in year two, when a customer adds a required field or Salesforce retires an API version.

Appnigma does both kinds of work. For the managed package route, marketplace apps covers "a Salesforce managed package or HubSpot app built around your product and customer workflows," with listing preparation and review support. As that page puts it, "Build and review are separate steps," and platform review timing is set by Salesforce. One project example from that page is Warmly's native Salesforce app, built in 2 weeks and launched in 8 weeks including six weeks of security review. That was one project, not a guaranteed schedule. For API integrations, done for you assigns "a named integration engineer" for implementation, testing and ongoing maintenance. Teams whose own engineers want to build can use Appnigma's integration infrastructure, which starts with "default mappings" and adds custom objects and field rules per customer.

Frequently Asked Questions

What is a native Salesforce integration?

In Salesforce's terms it is a managed package that runs inside the customer's org. Buyers often use the phrase for any vendor-built integration, so confirm which one they mean before scoping.

Does a native Salesforce app use the customer's API limits?

Yes, for any API calls it makes. Salesforce says calls from installed managed packages count against the org limit, while Apex triggers and flows inside the org run under governor limits instead.

Does a native integration keep data inside Salesforce?

Only if it never calls out. A package that sends data to your backend must register that endpoint, and the security review tests it.

Is an ETL tool like Fivetran or Airbyte a native integration?

No. Both copy Salesforce data into a destination such as a warehouse, and writing back to Salesforce is a separate product from each vendor.

Can Appnigma build and maintain our native Salesforce integration?

Yes. Appnigma's marketplace apps work builds the managed package with listing and review support, and done for you delivery covers API integrations with ongoing maintenance.

About the author

Sunny Chauhan is the co-founder and CEO of Appnigma AI, which builds and maintains customer integrations and native Salesforce and HubSpot apps for B2B SaaS teams. Before Appnigma, he was on Salesforce's AppExchange team, where he worked with more than 300 SaaS partners. He has spent close to a decade on the Salesforce platform, including work at Zennify, and holds Salesforce certifications including Platform Developer II, Platform App Builder, Administrator, Data Cloud Consultant, and AI Associate.

Sources

  1. Salesforce Developers, Salesforce Developer Limits and Allocations, API Request Limits and Allocations
  2. Salesforce Developers, Apex Developer Guide, Adding Remote Site Settings
  3. Salesforce Developers, Apex Developer Guide, Execution Governors and Limits
  4. Salesforce Developers, ISVforce Guide, Security Review Guidelines
  5. Salesforce Developers, ISVforce Guide, Test Your Entire Solution
  6. Salesforce Developers, ISVforce Guide, Required Materials
  7. Salesforce Developers, ISVforce Guide, Product Types
  8. Salesforce Developers, 1GP Developer Guide, Push Upgrades
  9. Salesforce Developers, 2GP Developer Guide, Enable a Package Subscriber to Restrict Push Upgrades
  10. Salesforce Developers, 2GP Developer Guide, Push Upgrade Best Practices
  11. Salesforce Developers, REST API Developer Guide, API End-of-Life Policy
  12. Salesforce Developers, ISVforce Guide, Secure Your Connected Apps and ECAs
  13. Fivetran Docs, Salesforce Connector
  14. Fivetran Docs, Activations Overview
  15. Airbyte Docs, Salesforce Source
  16. Airbyte Docs, Salesforce Destination

Which integration is your next deal waiting on?

Bring the customer requirements and your current setup. Get a clear scope and delivery timeline to take back to them.