CRM & Sales · Integration
HubSpot
Add HubSpot to your product for your customers, and give your AI agents governed access to it.
An embedded HubSpot integration lets your customers work their own portal from inside your product, covering contacts, companies, deals, tickets and the notes, tasks and emails that make up a timeline. HubSpot's distinctive idea is the association: a contact is linked to a company rather than owned by one, and much of what a user thinks of as context lives in those links instead of on the record. Lifecycle stage drives a great deal of portal automation, which makes writing it a decision rather than a field update. Access comes through OAuth or a private app token, and custom objects exist only on higher tiers, so no portal can be assumed to have them. fastn handles per-portal credentials, refresh and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own portal so your product reads their contacts, companies and deals in place.
Create the associations between records as well as the records themselves, so context is not lost on the timeline.
Write timeline activity from your product, so a call or task your app generated appears where the rep works.
Degrade gracefully on portals without custom objects, making tier differences configuration rather than a support ticket.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a company's associated deals and open tasks before it drafts a follow-up.
An agent moves a lifecycle stage only where it has been permitted to, and the change is attributed.
An agent explains why a deal looks stalled by citing the timeline entries it read.
Example prompt
Show this company's associated deals and the last activity logged on each one.
Set up HubSpot in 4 steps
- 01Enable the HubSpot connector from your fastn dashboard.
- 02Have each customer authorise their own HubSpot account, so calls run under their credentials rather than a shared key.
- 03Decide which accounts, contacts and opportunities your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the HubSpot integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a HubSpot integration without building it. Your customers connect their own HubSpot account inside your product and work their accounts, contacts and opportunities there, with no per-customer code on your side.
- Handle the part that actually costs time: every CRM instance is customised, so standard objects are never the whole story. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a HubSpot update is not your on-call problem.
- One integration serves your product and your agents. The same governed HubSpot connection powers in-product features and gives AI agents scoped, audited access, so you keep customer records aligned between your product and the CRM each customer already runs without wiring it twice.
Used by these teams
Compare with
Salesforce
Pipedrive
KeapOften used alongside
Tools the same teams tend to run next to HubSpot, across other categories.
Slack
Mailchimp
Marketo
Google AdsHubSpot integration FAQ
How do I add a HubSpot integration to my product?
Enable the HubSpot connector in your fastn dashboard, then let each customer authenticate their own HubSpot account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no HubSpot client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own HubSpot account?
Yes. Every connection is scoped to the individual customer, so each authorises their own HubSpot account and only ever sees their own accounts, contacts and opportunities. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this HubSpot integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads a company's associated deals and open tasks before it drafts a follow-up.
Who maintains the HubSpot integration?
fastn does. When HubSpot changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the HubSpot integration support custom fields and custom objects?
Yes. CRM instances are heavily customised, so field and object mapping is configuration rather than code. Each customer maps their own fields during setup, which means onboarding a customer with an unusual HubSpot schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from HubSpot, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in HubSpot do not drift apart.
What can I build with the HubSpot integration?
A common starting point: let each customer connect their own portal so your product reads their contacts, companies and deals in place. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the HubSpot integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding HubSpot does not change your per-connector cost. You can start free with 3 connected accounts.
Add HubSpot to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.