HubSpot Integrations: Connecting Your Stack to the CRM

By Nikola, founder at ZEROX. We build custom HubSpot integrations, private apps, data sync, and API work, for agencies and B2B teams across the US, UK, and Europe. Last updated July 2026.

Most B2B companies do not have a HubSpot problem. They have a "HubSpot does not know what the rest of the business knows" problem. The website captures a lead, then the CRM sits blind to whether that person ever paid an invoice, placed an order, or churned. HubSpot integrations are how you close that gap, so the website, the CRM, and every other system your company runs finally tell the same story.

There are four ways to build a HubSpot integration, and the mistake we see most often is teams reaching for the hardest one first. This post covers all four, when each is the right call, the integrations B2B teams ask us for most, and how to keep your contact and deal data from turning to mush along the way. It is written for technical-but-busy teams whose website and CRM need to talk to the rest of the stack.

The four ways to run HubSpot integrations

Almost every connection you will ever build falls into one of four buckets, ordered here from least to most effort:

• Native marketplace app, someone already built the connector; you install and authenticate it.
• iPaaS (Zapier, Make, Workato), you wire tools together with no-code automation.
• Operations Hub data sync, HubSpot's own two-way sync between systems.
• Custom API integration, a developer builds exactly what you need against HubSpot's API.

Cost, control, and maintenance all rise as you move down that list. The right answer is usually the highest option that genuinely does the job, not the most powerful one.

Native marketplace apps: try these first

The HubSpot App Marketplace lists well over a thousand connectors, including Salesforce, Stripe, QuickBooks, Slack, Gmail, Shopify, and most tools a B2B company already runs. The flow is usually install, authenticate, map a few fields, done.

Native is the right choice when the tool is popular, the app is officially maintained by the vendor, and your needs match what the connector already does. The one thing to check before you rely on it: read what the app actually syncs. Many marketplace apps move data in a single direction or cover only a subset of objects and fields. The official Shopify app, for example, brings orders and customers into HubSpot, but it will not cover custom metafields or B2B pricing rules on its own. Know the boundaries before you build workflows on top of it.

iPaaS and Operations Hub: automation versus true data sync

These two get conflated constantly, and they do different jobs.

iPaaS (Zapier, Make) is event-driven automation: "when X happens in tool A, do Y in HubSpot." It is excellent for triggers, notifications, and low-volume moves between the long tail of apps that will never justify a custom build. Its weakness is that it fires once per event and never reconciles. If the same record changes on both sides, Zapier has no idea, and you drift into duplicates and stale values.

Operations Hub data sync is HubSpot's own two-way sync. It keeps the same records in continuous agreement across two systems, with field mappings and explicit conflict resolution, so a contact edited in either place matches in both. This is the right tool when data has to stay accurate in HubSpot and another system at once, such as an accounting or support platform, rather than just being copied once. Operations Hub also adds programmable automation and custom-coded workflow actions on its higher tiers.

The rule of thumb: use Zapier or Make when you are triggering an action, and use Operations Hub when you are keeping data in sync.

Custom API integrations: private apps and webhooks

When native apps and iPaaS cannot do the job, a proprietary ERP, a homegrown app, complex logic, high volume, or an integration that has to live inside your own product, you build against HubSpot's API directly.

The modern model is a private app with a scoped access token. HubSpot deprecated the old API keys, so every new custom integration authenticates through a private app (or OAuth for apps you distribute), granted only the scopes it needs. You read and write records through the CRM API, and you use webhooks so HubSpot pushes changes to you the moment they happen instead of you polling on a timer. Done properly, this is real software with rate-limit handling, retries, logging, and error alerting. It is exactly the kind of work our web app development team builds. It is also where a store integration usually ends up: connecting Shopify to HubSpot properly often means going past the native app into custom code.

The integrations B2B teams actually ask us for

• Payments, Stripe, QuickBooks, or your billing system, so a closed deal or paid invoice updates the CRM and triggers onboarding automatically.
• ERP, two-way sync of accounts, orders, and inventory between HubSpot and NetSuite, SAP, or Dynamics. Almost always custom.
• Product data, pushing catalog and pricing into HubSpot line items, quotes, or HubDB so sales quote from live data.
• Shopify, orders and customers into the CRM for lifecycle marketing, native app plus custom work for metafields and B2B pricing.
• Custom apps and portals, a customer portal or internal tool that reads and writes HubSpot through the API so your product and CRM share one source of truth.

Keeping contact and deal data clean

The integration is the easy part. Data governance is where these projects succeed or quietly fail. A few rules we never skip:

• Decide the system of record for each field before you connect anything. Every field gets exactly one owner.
• Match records on a stable unique key. Email addresses change, so use a customer or account ID wherever you can.
• Map, do not dump. Only sync fields someone will actually use.
• Set conflict rules explicitly, so you know which side wins when both change.
• Watch for sync loops and duplicate creation, and test in a sandbox before touching production.

A fast integration that fills the CRM with duplicates and stale values is worse than no integration, because now people distrust the data and work around it.

FAQ

What is the difference between Zapier and Operations Hub data sync?

Zapier fires an action when an event happens, in one direction, one time. Operations Hub keeps records continuously in agreement across both systems, with field mapping and conflict handling. Use Zapier to trigger something; use data sync to keep data matching.

Do I still need API keys for HubSpot integrations?

No. HubSpot deprecated API keys. Custom integrations now authenticate with a private app access token, or OAuth for apps you distribute, scoped to only the data they need.

Can I connect HubSpot to a system that is not in the App Marketplace?

Yes, that is exactly what a custom integration is for. Using the CRM API, private apps, and webhooks, a developer can connect almost any ERP, database, or in-house application, two ways if you need it.

How do I stop an integration from creating duplicate contacts?

Match on a stable unique identifier, define a single system of record per field, and use HubSpot's deduplication settings. Always test in a sandbox before syncing production data.

Tell us what you are trying to connect

If your website and CRM already talk but the rest of the business is still guessing, that gap is usually a few weeks of integration work, not a platform migration. We scope it on a short call, quote it fixed, and you own the code at the end. Custom integration and portal work sits with our web app development team. Tell us what you need connected and we will say honestly which of the four approaches fits.