Integrator for HubSpot
Integrating the HubSpot API into your system
We wire HubSpot into your SaaS: signup creates contact and deal, usage updates the record, churn triggers ticket or workflow. Sales and support see the same truth.
- Senior product team
- CRM connectors in production
- from scoping to monitoring
Why work with a HubSpot integrator and what can be connected to HubSpot?
HubSpot is a CRM and marketing platform. You integrate it so it lives in your product: signup creating contact, company and deal, usage feeding properties, churn launching ticket or workflow, won deal provisioning and billing. Not a silo that sales updates by hand. The work is mapping your business model onto HubSpot objects without duplicates, and sizing the connector to the real plan and quotas.
What HubSpot changes in your platform
Signup creates contact, company and deal
Signup or trial: contact, company and deal created from your internal id. No more record retyped by a rep.
Product usage updates the record
Plan, volume, last sign-in, incidents: properties filterable in a workflow. Follow-up starts from a real signal.
Churn risk triggers ticket and workflow
Inactivity, quota exceeded, trial ending: the product pushes a ticket or a sequence. Sales and CS share the climate.
Won deal provisions and bills
A stage change creates the account, opens access and starts billing. No copy-paste between tools.
What it changes in your product
Engineering in service of a measurable outcome: signup → record, usage → pipeline, one shared truth.
Your sales team sells instead of typing
Contact, company and deal are created straight from your application. The time saved on data entry goes back into prospecting.
One record per customer
Matching uses your internal identifier, not the email address. The database stops filling up with duplicates.
A pipeline you can believe in
Amounts and stages come from the product or billing. Your forecasts become usable again.
A HubSpot bill under control
The marketing contact status is driven by the connector. You do not discover a tier change after a bulk sync.
How we ship your HubSpot connector
Scoping
Where HubSpot enters your product: signup, usage, churn, onboarding. HubSpot plan, objects, custom properties, private or public app. Quota follows the plan.
Mapping
Matching your entities to the HubSpot model, a unique matching property, labelled associations, a precedence rule per field. This is the step that decides success.
Development and testing
Batch writes, exponential backoff on 429, webhook signature verification, a retry queue. Replay on a dedicated developer account.
Monitoring
Alerts on sync failures, a daily quota consumption counter, a health dashboard. You know a flow is broken before your sales team does.
What the API brings to your platform
- CRM objects
- Contacts, companies, deals, tickets, line items and quotes for reading and writing, with batch endpoints of up to 100 records per call.
- Custom properties and objects
- Your business fields live in HubSpot like the standard ones. Truly custom objects, however, require an Enterprise plan.
- Labelled associations
- Links between objects carry a type and a label, with large batch creation. That is what keeps the model readable for your sales team.
- Webhooks, workflows and events
- Real-time notification of creations, updates, deletions, merges and associations, plus workflow management and custom event sending.
The vocabulary of a HubSpot integration
- Private app and public app
- A private app authenticates with a token and sees only one portal. A public OAuth app is essential as soon as you serve several clients, with a quota computed differently.
- Unique property
- A custom field carrying your internal identifier and serving as the matching key. It is what makes an upsert possible instead of a search by email.
- Custom object
- A CRM object shaped to your model, reachable through the same endpoints as the standard ones. It requires an Enterprise plan: without it, you model inside the standard objects.
- Labelled association
- A typed link between two objects, with a readable label. The distinction between HubSpot-defined and user-defined types shapes the whole mapping.
- Marketing contact
- A status that counts towards your billing tier, unlike the non-marketing status. An integration that dumps contacts in bulk without managing it pushes the bill up.
- Date-based versioning
- API paths now carry a date rather than a version number. Breaking changes arrive twice a year, which calls for ongoing watch, not just development.
The real constraints of a HubSpot integration
The quota depends on your plan, and it is shared
A private app runs from 100 requests per 10 seconds and 250,000 a day on entry plans to 190 per 10 seconds and one million a day on Enterprise. The daily cap is shared by every application on the portal.
Custom objects are not a fallback
They require an Enterprise plan. Without one, you model inside the standard objects using custom properties, which changes the design. That is settled before the quote, not during development.
Marketing contacts weigh on your bill
The marketing contact status counts towards the billing tier. A sync pushing tens of thousands of contacts without managing that status is expensive for the client, not for the provider.
Date-based versioning calls for ongoing watch
Paths carry a date, breaking changes arrive twice a year and each version is supported for at least 18 months. A HubSpot connector is maintained, not delivered once and forgotten.
HubSpot or Salesforce, and what it implies
The choice is rarely technical: it depends on the size of your sales organisation and on who administers the CRM day to day.
| Criterion | HubSpotThis page | SalesforceLarge accounts |
|---|---|---|
| Data model | Readable standard objects, simple custom properties | Very rich and highly configurable, with notions of its own |
| Custom objects | Reserved for the Enterprise plan | At the heart of the platform |
| Authentication | Private app token, or OAuth 2.0 for multi-client | Connected app over OAuth 2.0 |
| Rate limit | Documented and readable, varies by plan | Platform and governor limits to watch |
| Real time | Signed webhooks, plus custom events | Event mechanisms specific to the platform |
| Integration effort | Low to medium, excellent documentation | High, with dedicated skills |
| The right case | A SaaS or SME wanting to plug its product into the CRM quickly and cleanly | A complex sales organisation, high volumes, in-house administrators |
We claim no HubSpot certification, no tier badge and no partner status: we build HubSpot integrations and act as the development team, alongside the agency or administrator running your portal.
What we measure on a HubSpot project
The other CRMs we integrate
The choice follows whichever CRM you already run, rarely the technology.
HubSpotIntegrating the HubSpot API into your systemThis page
SalesforceHigh volumes and complex organisations, with rules of its own.
PipedriveSimple and quick to connect, a fit for lean sales teams.
SellsyThe French option, when invoicing and CRM live in the same place.We combine HubSpot with
The stack that surrounds HubSpot on our projects.
HubSpot integration: your questions
We wire it into your product touchpoints: signup, usage, churn, onboarding, billing. First the app mode: private app for a single portal, public OAuth app as soon as you serve several clients. Then the mapping onto HubSpot objects, with your internal id as a unique property for upsert. Finally signed webhooks and batch writes so the quota is not burned. The real difficulty is not the technical call, it is the mapping and the anti-duplicate rule.
It depends on the touchpoints to wire, the direction of the flows and the state of the portal. Pushing usage onto the company record costs far less than a full chain signup → deal → provisioning → billing. Two things weigh as much as the engineering: how clean the properties already created by hand are, and your HubSpot plan (quota and custom objects). We scope the perimeter up front and give a firm estimate.
To roll out HubSpot, pick the plans and train the teams, yes, a certified partner makes sense. To connect HubSpot to a custom application, what counts is connector experience, rigour on the data model and command of the real quotas. We claim no HubSpot certification, no tier badge and no partner status: we build HubSpot integrations, and we are glad to work with the agency or consultant already running your portal, each on their own ground.
A private app is the right choice when the integration only concerns your own portal: token authentication, quick setup, a more generous quota depending on your plan. It has clear limits, though: it sees a single portal, cannot be published on the marketplace, does not handle custom timeline events and cannot change its webhook subscriptions through the API. As soon as your product has to connect to your own customers' portals, you need a public OAuth app. That is an architecture decision, not a setting: it is made during scoping.
They depend on the app mode and on the plan. For a private app, the cap runs from 100 requests per 10 seconds and 250,000 a day on entry plans to 190 requests per 10 seconds and one million a day on Enterprise, with an increase add-on available. For a public OAuth app, the limit is 110 requests every 10 seconds per installing account, and the add-on does not apply. One important point: the daily cap is shared by every application on the portal. That is why we make batch writes and a consumption counter standard practice.
A HubSpot integration project?
Let's talk. 30 minutes to scope where HubSpot enters your platform (signup, usage, churn, onboarding) and tell you honestly what is feasible.
Discuss my HubSpot project