Connect HubSpot to your other systems
A HubSpot integration means marketing, sales and service all work from the same customer data. No more retyping quotes into the accounting system, no separate Excel list of orders. And a salesperson can see on the call whether the last invoice has been paid.
- Contacts and companies goes back and forth with Your other systems
- Deals and pipeline goes back and forth with Your other systems
- Products and quotes goes back and forth with Your other systems
- Invoices and payment status back goes back and forth with Your other systems
Built for clients including Tata Steel, M&G Investments, Digistore24, Toppers in Concert, Bar-le-Duc and Loogman
This is the data organisations most often let flow between systems. Which of it matters to you depends on where work is getting stuck today.
Contacts and companies
The basis of almost every integration. HubSpot recognises a contact by email address and a company by domain name. Agree up front which system is allowed to change an address or phone number, or two systems will overwrite each other.
Deals and pipeline
A won deal is often the trigger for everything else: a customer in the accounting system, an order in the ERP or a project in your planning. The deal stage is then the moment the integration kicks in.
Products and quotes
HubSpot has products, quotes and line items. If your items and prices live in an ERP, pull them from there. That way a salesperson never puts an old price in a quote.
Invoices and payment status back
Invoices are usually created in the accounting system. Send the invoice number and payment status back to HubSpot, and sales can see whether a customer is behind on payments before a new quote goes out.
Orders and tickets
HubSpot has its own objects for orders, carts and tickets. That puts purchase history and service requests next to emails and calls, on the same contact.
For each combination: which data moves back and forth, what the standard integration does and what to watch out for.
- Connect Exact Online to HubSpotConnect Exact Online to HubSpot: which data to exchange, what HubSpot's own app does, and what to watch out for with deals, invoices and payment status.
- Connect Twinfield to HubSpotConnect Twinfield to HubSpot: which data moves between CRM and accounting, which system leads, and where VAT, codes and API limits go wrong in practice.
- Connect AFAS to HubSpotConnect AFAS to HubSpot: a won deal becomes a customer account and order in AFAS, and sales sees in HubSpot which invoices are still outstanding.
- Connect Simplicate to HubSpotConnect Simplicate to HubSpot: what the built-in integration does, how a won deal becomes a project, and which system should lead for your customer data.
- Connect HubSpot to ShopifyConnect HubSpot to Shopify: what HubSpot's own integration syncs, which system leads on what data, and when you need a custom HubSpot Shopify integration.
- Connect ChatGPT to HubSpotConnect ChatGPT to HubSpot with HubSpot's own app: check deal status, prepare for calls and create tasks. What the integration can and can't do.
- Connect Claude to HubSpotConnect Claude to HubSpot with HubSpot's own connector: pipeline, customer history, tickets and marketing content. What it can do, and what to set up first.
Not always. If an existing integration for HubSpot does exactly what you need, we'll tell you.
The HubSpot App Marketplace has integrations for accounting, online stores, telephony and more. With data sync apps, you choose per object whether data goes to HubSpot, to the other package or both ways; HubSpot's own Shopify integration is an example. You log emails from Gmail and Outlook with HubSpot's extension or add-in.
A standard integration is enough when your data lines up neatly: a contact is a customer, a product has the same name in both systems and your process has few exceptions. Note: custom field mappings in data sync require a paid Data Hub subscription.
It gets tight as soon as your process deviates. Think of a customer with three branches that is a single debtor in the accounting system, or an order that may only proceed after a manual check. A standard integration has no setting for that, and the work ends up being done by hand anyway.
- Your accounting system or ERP has no app in the HubSpot Marketplace, or the app is missing fields you need.
- A won deal has to start something in several systems at once: a customer, an order and a project.
- You use custom objects in HubSpot, such as contracts or installations, that also exist in another system.
- Data has to pass a check first, such as a credit check or a valid VAT number, before it moves on.
- You want to merge data from several sources into a single customer view, with fixed agreements on which system wins.
REST API with date-based versions
HubSpot has REST APIs for CRM objects such as contacts, companies, deals, quotes, invoices and orders. New versions have a date in the path, such as 2026-09. Older versions keep working until their end date. If you're building something new, use the latest date-based version.
Access token or OAuth
An integration for a single HubSpot account uses a static access token. If the same app has to work across several accounts, for example through the App Marketplace, OAuth is required. With scopes, you give the app only the permissions it needs, such as writing contacts.
Webhooks
HubSpot sends a POST request to your own endpoint as soon as something happens: a new contact, a changed property, a deleted deal. An app can have up to 1,000 webhook subscriptions. So your integration doesn't have to keep asking whether anything has changed.
Limits per plan
Each app can make 100 requests per 10 seconds on Free and Starter, and 190 on Professional and Enterprise. On top of that there's a daily limit per account of 250,000, 625,000 or 1,000,000 requests, depending on your plan.
Testing without real customer data
You can create up to ten developer test accounts to test an integration without touching your real data. With an Enterprise plan, you can also create a standard sandbox that copies your account's configuration.
An integration moves data. In between, AI can read, sort and prepare a suggestion. Where it matters, a person decides.
What HubSpot can already do
Breeze Assistant, HubSpot's AI assistant, summarises records and conversations and helps with draft emails. Agent Hub, still in beta, has agents for customer service, prospecting and data quality. They run on HubSpot Credits. If everything you need is already in HubSpot, that's often enough.
Where you need an integration first
The built-in AI only sees what's in HubSpot. It misses an outstanding invoice in the accounting system or a complaint in another service system. Connect that data first, and a summary can also say that the customer still has two unpaid invoices.
AI between inbox and CRM
A customer emails in a change. AI reads the email, adds a short summary as a note on the right contact and drafts a reply for the account manager. They adjust it and send it themselves. Pricing agreements and commitments stay with people.
External AI tools with HubSpot data
With HubSpot's MCP server, AI tools can read and update contacts, companies, deals and tickets through OAuth, with the permissions of the user who signs in. Decide up front which changes an AI may make without a check.
Duplicate contacts and companies
HubSpot deduplicates contacts by email address and companies by domain name. If a debtor in the accounting system has no email address, or a Gmail address instead of a company domain, you get duplicates. Choose a fixed key, such as the debtor number in a custom property with unique values.
Two systems overwriting each other
If HubSpot and the accounting system can both change the address, whichever syncs last wins. Decide per field which system is leading. Otherwise a correction made by the finance team is gone again the next day.
Limits on the first sync
At the start, a lot of records go across in one go. Without pauses you hit the per-ten-seconds limit and get errors. Build in retries and spread large imports over time.
Dropdown values that don't match
Deal stage, industry or country are often dropdowns with fixed values in HubSpot. If another system sends NL while HubSpot expects Netherlands, the value doesn't come through properly. Create a mapping table and keep it up to date when someone adds a value.
What goes where
Which data moves, in which direction, and which system wins when two values differ. That is written down before anything gets built. For this integration, that means: Contacts and companies, Deals and pipeline, Products and quotes, Invoices and payment status back, Orders and tickets.
Fields and rules
For every field, how it translates between the systems: statuses, VAT codes, general ledger accounts, item numbers. And what happens with a duplicate or a missing value. For this integration, that means: REST API with date-based versions, Access token or OAuth, Webhooks, Limits per plan, Testing without real customer data.
Testing with real cases
In a sandbox or test administration, with the exceptions you actually run into: credit notes, partial deliveries, changed customer details.
Live, with logging and monitoring
Every sync is logged, and when something fails, someone gets an alert. If a vendor changes its API, we update the integration.

No account manager. You talk to someone who builds integrations themselves, and who will tell you when a standard integration is enough.
- Office on the Duivendrechtsekade in Amsterdam
- ISO 9001 and ISO 27001, certified by Kiwa
- 500 projects delivered
- 4.8 from 127 reviews
Can I connect HubSpot to my accounting software?
Yes. For some packages there's an app in the HubSpot App Marketplace; otherwise you build an integration using both systems' APIs. Usually customer data and won deals go to the accounting system, and the invoice number and payment status come back. Agree up front which system leads on customer data, so a correction isn't overwritten.
Does HubSpot have an API?
Yes, HubSpot has REST APIs for contacts, companies, deals, quotes, invoices and orders, among others. You authenticate with OAuth or, for a single-account integration, a static access token. With webhooks, HubSpot tells your integration straight away that something has changed.
Does my HubSpot plan matter for an integration?
Yes, in two ways. The API request limit is higher on Professional and Enterprise than on Free and Starter. And not every API is available on every plan; HubSpot keeps an overview by product and tier.
How do I test a HubSpot integration without touching my customer data?
Create a developer test account; you can have up to ten. On Enterprise, you can also use a sandbox that copies your real account's configuration. Test the edge cases there too, such as a contact without an email address or an unknown deal stage.
Is a marketplace app enough, or do I need a custom integration?
Start with a standard integration if your process is simple and the fields match in both systems. You need a custom integration if you use custom objects, want to apply rules before data moves on, or if there's no app for your package. We can connect HubSpot to any system, even when there's no standard integration.
Sources
The technical facts on this page come from the vendors' official documentation, checked on 19 September 2026. Vendors change their APIs and limits; when we build an integration, we always check the current state.
- HubSpot: API usage guidelines and limits
- HubSpot: API overview and date-based versions
- HubSpot: Authentication overview
- HubSpot: Configure a webhook subscription
- HubSpot: Account types (test accounts and sandboxes)
- HubSpot: APIs by tier
- HubSpot Knowledge Base: Connect and use HubSpot data sync
- HubSpot Knowledge Base: Deduplicate records
- HubSpot Knowledge Base: Log your sent and received emails
- HubSpot Knowledge Base: Use Breeze Assistant
- HubSpot Knowledge Base: Understand Agent Hub
- HubSpot: Using the HubSpot MCP server





