HubSpot Integration Providers for SaaS Companies and HubSpot Customers

If HubSpot is one of many CRMs your product must connect to, a unified API such as Merge or an embedded iPaaS such as Paragon or Prismatic is usually the practical HubSpot integration provider, because one build covers many apps. If HubSpot is one of two or three platforms and buyers expect your product inside HubSpot or listed on its Marketplace, a native HubSpot app fits better. Your engineers can build it themselves or on code-first infrastructure such as Nango, or an engineering firm can build it for you. Two costs decide between them. One is the vendor's billing unit at your year-two customer count. The other is who moves the integration to HubSpot's new app architecture before the September 2027 cutoff.

Most pages ranking for this term are agency lists written for companies connecting their own HubSpot. This one starts with the SaaS vendor's decision, where the billing unit, the listing rules and the maintenance plan decide the cost. Appnigma, the author's company, offers done-for-you integration delivery, described on its page as "Build your product. We'll build the integrations," with ongoing maintenance from a named integration engineer. If you are connecting your own company's HubSpot to an ERP or another CRM, skip to the section for HubSpot customers.

Updated October 2026. Checked against HubSpot's developer docs and changelog and each vendor's pricing page on October 23, 2026. Ampersand no longer publishes plan prices and Tray now does. This update adds HubSpot's September 2027 end of support for legacy apps and v1 to v3 APIs, the 25-install cap before listing, and year-two pricing worked out at 50 customers.

Five ways a SaaS company can get a HubSpot integration built

The five options differ less in what they connect than in what you pay for and who writes the HubSpot-specific code. Prices below are the published starting points on each vendor's pricing page, read October 23, 2026. "Quote only" means the vendor publishes no figure.

Merge's pricing page charges $650 a month "for up to 10 total production Linked Accounts" and $65 for each one after that. Paragon prices by Connected Users, defined as "the number of tenants (customer orgs)" using your integrations. Prismatic bills per instance, "a deployment of an integration to a customer," and is "never billed on API calls or executions." Cyclr charges "$100 per Connector per month" on its pay-as-you-go tier with "100,000 API Calls Included." Tray says "Tray starts at $50 a month" without saying whether that covers Tray Embedded. Nango counts a connection as "one authorized user account." Ampersand now measures usage "in Ampersand actions" and prices each plan by proposal. Workato publishes no embedded price.

If your product also has to sync each customer's NetSuite, the vendors above cover it too. Merge and Paragon publish NetSuite pages, and so do Prismatic, Nango and Ampersand. Check the records and sync direction on each before you shortlist.

HubSpot iPaaS vs native integration for a SaaS product

A unified API or embedded iPaaS moves records between your product and each customer's HubSpot. A native HubSpot app can also put your product inside HubSpot, on the record page, through app cards built with UI extensions. If sales teams expect to see your data next to a deal without leaving HubSpot, only an app delivers that, whoever builds it.

Sync timing differs by design too. Merge's HubSpot page says its sync frequency "depends on both your plan and the Common Models you're using," from every 24 hours down to every 5 minutes, with Force Resync and Automatic Webhooks for anything faster. Paragon's HubSpot docs expose record actions and webhook triggers, so updates arrive as events instead of on a schedule. The trade is coverage. Merge normalizes HubSpot into common models shared with other CRMs, which is what lets one integration cover many CRMs. An app or a code-first build reads HubSpot's own objects, including each customer's custom objects, in HubSpot's own shape.

The listing question cuts across all five routes. Every option can end up on the Marketplace, because HubSpot lists apps, not vendors. Paragon's docs say that to list "you must implement the following additional features," including a Redirect Page in your application that completes the OAuth exchange. Merge's HubSpot setup guide has you create your own HubSpot app and enter its credentials in Merge. Either way, the app is yours and HubSpot's listing rules apply to it.

What the bill looks like at 50 customers

A HubSpot integration vendor's bill grows with its billing unit, so price every option at your expected customer count in year two, not at launch. The table works through a product with 50 customers on HubSpot, using each vendor's published rates read October 23, 2026. It is arithmetic, not a quote.

The Cyclr row shows why the unit matters more than the starting price. If your product polls each customer's HubSpot every 15 minutes, 50 customers make 144,000 polls a month. If Cyclr counts each poll as one API call, that passes the 100,000 included calls before any writes. Check how each vendor counts the unit against your own sync design, not against the plan name.

The Merge row shows the other side. At 10 customers Merge costs $650 a month, and at 50 it costs five times that. That is fine if HubSpot is one of 20 CRMs you need through one API. If your roadmap is HubSpot plus Salesforce, two native builds are a short list and neither bill grows with each customer you sign. Teams in between can build on integration infrastructure your engineers build on, such as Appnigma's, where the infra handles "app registration and authorization" and monitoring for each customer connection, while your team writes the integration logic.

What HubSpot requires before your app can be listed

HubSpot's App Marketplace listing requirements apply no matter which route builds the app. The app must use OAuth as its sole authorization method and authorize with the single public app ID tied to the listing. It needs at least three active installs. HubSpot counts only production accounts "unaffiliated with your organization" that show successful app activity in the past 30 days. It can't run on an unsupported platform version or use classic CRM cards, which HubSpot says are "no longer supported as of June 16, 2025." AI connector apps must require user-level permissions or be built with HubSpot's MCP Server.

Getting to those three installs has its own path. Before listing, HubSpot's app management docs allow a privately distributed app in "up to 10 allowlisted accounts," and a Marketplace-distributed app is "limited to 25 installs" until the Ecosystem Quality team reviews and lists it. After listing, installs are unlimited. Plan the listing work in parallel with your first customers, because the 26th customer can't install an unlisted app. Our HubSpot partners directory guide covers how listed apps and agencies appear in HubSpot's directories.

Review itself is quick to start and slow to finish. HubSpot says the Ecosystem Quality team "will complete an initial review within 10 business days," that the full process "should take no more than 60 days from the time feedback is shared," and that "you can only submit one app at a time." The pricing in your listing must match the pricing on your website. Appnigma's marketplace apps service covers this stage with a native app plus listing preparation and review support. Its page includes "HubSpot listing review and certification support where eligible."

Certification is a later and higher bar. The certification requirements ask for at least 60 active installs and at least six months listed. The app must also keep "an average success rate above 95% across all activities." Certification is valid "on a rolling basis for two years" and must be renewed. The HubSpot app certification requirements guide walks through the full checklist, and how to become a HubSpot App Partner covers the Technology Partner tiers that follow listing.

Rate limits a two-way sync has to fit inside

HubSpot's usage guidelines limit a Marketplace-distributed OAuth app to 110 requests every 10 seconds for each HubSpot account that installs it, with the CRM Search API counted separately. There is no published daily limit for those apps, and the API limit increase add-on "does not increase the limits" of public apps. Privately distributed apps follow the installing account's tier instead.

Two numbers matter when you design the sync. HubSpot's certification page asks apps to throttle to "100 requests per 10 seconds for each account," so build to 100, not 110. And errors "shouldn't exceed 5% of your total daily requests," so a sync that retries blindly on 429 responses can put a listing at risk even if every retry eventually succeeds. Because the limit is per installing account, one large customer's backfill doesn't slow the others, but it does mean your queue needs a separate budget for each customer.

Who migrates your integration before September 2027?

HubSpot's September 15, 2026 changelog set a September 2027 end of support for v1 to v3 APIs and for legacy public and private apps. Support for v4 APIs ends earlier, on March 30, 2027. For a Marketplace app the consequences are specific. An app still calling v1 to v4 after September 2027 "loses its certification status," and one still on the legacy app architecture "is eligible for delisting." Public apps created before June 23, 2026 are legacy apps, and apps on platform version 2025.2 or older "need to migrate to the current version (2026.09) by March 2027."

HubSpot's versioning page explains the cadence behind this. A new platform version ships every March and September and becomes unsupported 18 months later, and since March 30, 2026 the REST APIs use date-based paths such as /2026-03/. The changelog's advice is to migrate "directly from any legacy version to date-based versioning," without stopping at v3 or v4. One more change arrives with the /2026-09/ APIs, because HubSpot "will enforce admin-configured validation rules on all CRM API write paths." A sync that writes a value a customer's admin has disallowed will start getting errors it never saw before.

Who does that work depends on the route. With an in-house build or code-first infrastructure, your engineers do it. Nango says its catalog actions "are maintained by Nango and update automatically," but a copy you deploy yourself "no longer follows catalog updates."

With a unified API or embedded iPaaS, the vendor updates its connector. Tray says it plainly, "Tray maintains the connectors," on its embedded page. You still own whatever you built on top, including the HubSpot app the listing points to.

With a done-for-you build, the contract decides. Appnigma's done-for-you service includes ongoing maintenance, with fixes delivered "as pull requests for your review." A standalone marketplace app project scopes maintenance separately, so ask any firm which model you are buying before you sign.

No vendor page we checked commits to a date for moving its HubSpot connector to the new date-based paths. Ask for one in writing.

Mistakes that cost SaaS teams time with a HubSpot provider

• Pricing at launch volume. The billing unit decides year-two cost. Model 24 months at your expected customer count before you compare.
• Shipping a legacy public app in 2026. An app created before June 23, 2026 on the old architecture faces delisting risk after September 2027. Start new builds on platform version 2026.09.
• Building on a legacy private app. HubSpot disables legacy private app creation for existing accounts on October 26, 2026, per its changelog, and points teams to Service Keys instead. Private apps can't be listed anyway.
• Counting the wrong installs. Test accounts and accounts affiliated with your company don't count toward the three installs for listing or the 60 for certification.
• Asking for broad scopes. Request only the scopes your app uses. Our HubSpot OAuth scopes guide shows which scopes each object needs.
• Leaving code ownership vague. Get in writing which code lands in your repository, which runs on the vendor's platform, and what happens to both if you leave.

If you are connecting your own HubSpot instead

A company connecting its own HubSpot to an ERP or another CRM needs a different kind of provider than a SaaS vendor does. It should start with a HubSpot-built connector and then the Marketplace, which showed more than 2,400 apps on its all-apps page on October 23, 2026. After that comes an iPaaS such as Zapier or Celigo, and last a custom build by a Solutions Partner. Marketplace apps are free to install, and each app's vendor bills for its own product.

HubSpot's own connectors have tier rules. Its Salesforce integration needs a Professional or Enterprise subscription to one of HubSpot's hubs or Smart CRM. On the Salesforce side it needs "a Salesforce edition with API access" or Salesforce Professional Edition. Its NetSuite integration is available on "All products and plans," supports one-way or two-way sync, and needs a Data Hub subscription only "to create any custom field mappings." Data Hub Professional starts at $800 a month and Enterprise at $2,000 a month on HubSpot's product page. Our guide to what HubSpot's Salesforce connector syncs covers the field mapping.

When no connector fits, these providers come up most often. Each is described in its own words.

You can check an agency's claims against HubSpot's own records. HubSpot's Custom Integration accreditation is "for partners who custom-build integration solutions for customers using HubSpot developer tools." Only partners at the platinum tier or above can apply for it and keep it. The Solutions Directory shows each partner's tier and accreditations, and lets you filter by country.

Frequently Asked Questions

Is Merge an embedded iPaaS or a unified API?

Merge is a unified API. It exposes HubSpot through normalized Common Models shared with other CRMs, while embedded iPaaS vendors such as Paragon and Prismatic run workflows you configure per connector.

Can an app built on an embedded iPaaS be listed on the HubSpot Marketplace?

Yes, if it runs through your own HubSpot app. That app must use OAuth only, authorize with the listing's public app ID, and have three active installs from unaffiliated accounts.

Do existing HubSpot apps have to migrate by 2027?

Yes, if they are legacy apps or call v1 to v4 APIs. After September 2027, HubSpot says those apps lose certification or become eligible for delisting, and v4 support ends on March 30, 2027.

Are integrations like HubSpot included or billed separately by software vendors?

It depends on the vendor. HubSpot Marketplace apps are free to install, and each app's vendor decides whether its HubSpot integration is included in a plan or sold as an add-on.

Can Appnigma build our HubSpot integration?

Yes. Appnigma's done-for-you service builds and maintains customer-facing integrations, and its marketplace apps service delivers a native HubSpot app with listing preparation and review support. HubSpot controls listing approval and timing.

Related Articles

• HubSpot integrations explained
• How to build a HubSpot app
• HubSpot Marketplace complete guide
• HubSpot partner programs explained
• HubSpot custom integration build guide

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. App Marketplace listing requirements, HubSpot Developers
2. Certification requirements, HubSpot Developers
3. Manage apps in HubSpot, HubSpot Developers
4. API usage guidelines and limits, HubSpot Developers
5. Developer platform versioning, HubSpot Developers
6. Legacy APIs and legacy apps, what's going unsupported and when, HubSpot Developer Changelog
7. Legacy private app creation sunset, HubSpot Developer Changelog
8. Use HubSpot's integration with NetSuite, HubSpot Knowledge Base
9. Install the HubSpot Salesforce integration, HubSpot Knowledge Base
10. Solutions Partner accreditations, HubSpot
11. Data Hub, HubSpot
12. Merge pricing and Paragon pricing, read October 23, 2026
13. Prismatic pricing and Cyclr pricing, read October 23, 2026
14. Tray pricing and Nango pricing, read October 23, 2026
15. Ampersand pricing and Workato pricing, read October 23, 2026