HubSpot Intercom Integration: Workflows & Best Automation Tool
HubSpot is the CRM source of truth; Intercom is the customer messaging surface.
Integrating them matches inbound Intercom conversations to HubSpot contacts, pushes ticket events into the CRM, and keeps properties in sync across both systems. Both apps ship native marketplace integrations — but running them alongside another sync creates duplicate user data, so the iPaaS path matters specifically for workflows the native apps can't cover, like ticket-to-deal lifecycle routing.
What can you automate?
The most common ways teams connect HubSpot and Intercom.
Match-then-sync: find or create HubSpot contact from new Intercom conversation
When a new Intercom conversation starts, search HubSpot for a matching contact by email first and update if found, or create if not.
The search step is what prevents duplicate contacts that naïve flows produce.
Open a HubSpot ticket when an Intercom conversation is tagged
A tag added to an Intercom conversation (billing, churn-risk, bug) fires a HubSpot ticket creation on the matched contact, with conversation link and tag reason in the ticket body.
The native Intercom sync doesn't push tickets — this is the gap.
Two-way contact property sync between HubSpot and Intercom
Bidirectional sync of selected contact properties (name, phone, CSM owner, custom fields).
Updates on either side propagate to the other, keyed on email, with conflict resolution rules for simultaneous writes.
Push closed Intercom conversations as notes on the matched HubSpot deal
When an Intercom conversation closes, post a formatted summary as a note on the matched contact's open HubSpot deal.
Sales sees the support conversation history without leaving the deal record.
Lifecycle sync: HubSpot deal stage change updates Intercom segment
When a HubSpot deal moves to a new stage (negotiation, closed-won, churned), update the matched Intercom user's segment so support and onboarding see lifecycle state without opening the CRM.
Weekly support-to-sales digest: Intercom tags × HubSpot deal creation
On a schedule, pull Intercom conversations tagged as high-intent and cross-reference against HubSpot deals created in the same window.
Post the correlation to a shared sales + support channel so both teams see the funnel together.
Platform Comparison
How each automation tool connects HubSpot and Intercom.
Make visual router + search-first-then-create patterns + conditional filters handle the duplicate-contact avoidance pattern this pair needs. Wins over Zapier on branching-heavy identity reconciliation.
Top triggers
Top actions
Extensive template library (6+ named templates) for contact + ticket sync. Fastest to set up, but linear Zap model glosses over the match-first requirement; use paths/filters carefully to avoid duplicates.
Top triggers
Top actions
Both apps native on Pipedream. Code steps handle match-before-create logic and custom property mapping; good fit when native HubSpot Intercom marketplace app does not cover ticket sync (documented gap).
Top triggers
Top actions
HubSpot is a certified connector; Intercom has a Power Automate integration. Works for Microsoft-first orgs but limited dedicated templates for this pair — expect manual flow building.
Top triggers
Top actions
HubSpot node is native; Intercom node exists with core conversation/user operations. Code node handles custom dedup logic and PII filtering — fits teams with GDPR-sensitive EU customers wanting self-host.
Top triggers
Top actions
What Will This Cost?
Drag the slider to your expected monthly volume.
Each platform counts differently — Zapier: 1 task per trigger. Make: 1 operation per module per record. n8n: 1 execution per run.
Prices shown for annual billing. Based on published pricing as of April 2026.
Estimated ROI
1000
min saved/mo
$583
labor value/mo
Free
no platform cost
Based on ~2 min manual effort per operation at $35/hr fully loaded labor cost.
When this pair isn't the right answer
Honest scenarios where HubSpot + Intercom via an automation platform isn't the best fit.
Native integrations already exist on both sides. HubSpot's Intercom Data Sync app and Intercom's HubSpot app each ship in their respective marketplaces with two-way contact sync. For basic contact mirroring, they are the starting point — iPaaS is only for the known gaps (ticket sync, conditional lifecycle routing, custom property flows).
Dual-app conflicts create duplicate user data. Running the native sync app alongside another integration produces duplicate contacts and reconciliation errors — a failure mode documented across both vendors' community forums. Teams must pick one sync path and commit to it, not layer iPaaS on top of a working native.
PII and compliance routing. Both apps hold customer PII — email, phone, profile, conversation transcripts. Routing that data through a third-party iPaaS adds a data-processor relationship and raises GDPR and data-residency questions for enterprise customers. Keeping sync inside the native marketplace apps simplifies the compliance story for buyers who care.
What breaks at scale
Where HubSpot + Intercom integrations hit ceilings — API rate limits, tier quotas, and per-task economics.
HubSpot API: 650,000 requests/day on Professional, 1 million on Enterprise, with 190-per-10-second burst cap. A 200,000-contact full-reload sync trips the daily cap; moderate two-way flows with property changes generally fit, but burst-heavy operations (nightly reloads, campaign updates) hit the 10-second window first and surface as 429 errors mid-batch.
Intercom API: 10,000 requests/minute per private app, 25,000 per workspace, evenly distributed in 10-second slots. Effective per-slot cap is roughly 1,666 requests — burst-heavy syncs hit the slot ceiling before the per-minute budget. Multiple private apps in the same workspace share the workspace budget; multiple public apps each get separate limits, which changes the architecture decision.
iPaaS per-task economics. A 50,000-contact bidirectional sync with property updates generates 100,000+ tasks per month, which sits in Zapier's $500-plus tiers. Make's operation-based pricing is more efficient at that volume, but above roughly 20,000 monthly events even Make starts pricier than a direct API integration hosted on a single serverless function. The curve matters once enterprise buyers enter the conversation.
Our Recommendation
Make wins this pair because the central failure mode — duplicate contacts when sync logic is naïve — is a branching-search problem that Make's visual scenario builder handles natively with router plus search-first modules.
- Straight-line Zaps on Zapier can implement match-before-create, but the pattern is awkward; Make's routers express it as the default shape.
- Both apps expose mature REST APIs and webhooks, and Make's operation-based pricing handles the 20,000-plus monthly event volumes this pair generates more efficiently than Zapier's per-task meter.
- Both HubSpot and Intercom ship native marketplace apps for basic contact mirroring — so the iPaaS job here is specifically the known gaps (ticket sync, conditional lifecycle routing, multi-tag ticket creation) where Make's scenario model earns its keep over simpler tools.
Analysis
HubSpot is where customer relationships are managed as records; Intercom is where customer conversations happen in real time, and the gap between them is the central tension this integration solves.
A support rep on Intercom needs to know the contact's lifecycle stage, last deal, and CSM assignment without context-switching into HubSpot. A sales rep working a deal in HubSpot needs to see the recent Intercom conversations before the discovery call.
Without integration, both teams ask each other by hand or lose context. Both vendors ship native marketplace apps — HubSpot's Intercom Data Sync and Intercom's HubSpot app — and for basic contact mirroring those are the correct starting point.
The reason iPaaS still matters here is a specific, well-documented set of gaps: the native apps don't sync tickets from Intercom to HubSpot; running both apps simultaneously creates duplicate user data; and custom lifecycle routing (deal stage changes pushing Intercom segment updates, tag-based ticket creation) requires logic the native apps don't express.
Both sides are REST-first with mature APIs and well-defined rate ceilings that define how any sync must be architected.
HubSpot's API limits are 650,000 requests per day on Professional (1 million on Enterprise) with a 190-per-10-second burst cap. Intercom grants private apps 10,000 requests per minute per app and 25,000 per workspace, evenly distributed in 10-second windows.
Both expose webhooks for the high-value events — HubSpot contact property changes, deal stage changes, and form submissions; Intercom conversation events, user updates, and tag additions. The architecturally critical pattern for this pair is match-before-create: search HubSpot for a contact matching the Intercom user before creating anything, because naïve "on new Intercom user, create HubSpot contact" flows without search logic are the documented source of duplicate contact problems. Make's scenario builder expresses this branching pattern natively with router and search modules; simpler linear flows trip over it.
Customer-facing organizations with separate Intercom (support) and HubSpot (sales/marketing) teams — typically 50–500 employees — are the clearest buyers.
The patterns in the wild, drawn from Zapier's deep Intercom × HubSpot template gallery and community threads, cluster around five shapes. First is identification: a new Intercom conversation triggers a HubSpot contact search first, then a create-or-update, avoiding duplicates.
Second is ticket routing: an Intercom conversation tagged with a specific label creates a HubSpot ticket on the matched contact. Third is property sync: changes to HubSpot contact properties (lifecycle stage, CSM owner) reflect in Intercom as user attributes.
Fourth is deal context: a HubSpot deal stage change updates the Intercom user's segment so support sees lifecycle state without opening the CRM. Fifth is reporting: a weekly digest correlates Intercom high-intent conversation tags with HubSpot deal creation rates so sales and support see the funnel together.
The native marketplace apps are the first answer for contact mirroring, not iPaaS, and running both native and iPaaS is actively harmful.
The first limit is that HubSpot's Intercom Data Sync app and Intercom's HubSpot app are both free, both well-supported, and both cover the basic contact-identification pattern. Teams who install iPaaS on top of a working native sync end up with duplicate user records and reconciliation problems — a failure mode documented in both vendors' community forums.
The second limit is PII handling: both apps store customer contact PII (email, phone, conversation transcripts) and routing that data through a third-party iPaaS cloud adds a data-processor relationship that enterprise buyers under GDPR or similar regimes may not want. The third limit is scale: a 50,000-contact CRM with daily two-way sync plus property updates generates 100,000+ tasks per month, well into Zapier's $500-plus tiers, where Make's operation-based pricing or a direct API integration wins decisively.
Use iPaaS for the known gaps — ticket sync, conditional routing, lifecycle logic — not for basic mirroring the natives already do.
Related Guides
Guides involving HubSpot or Intercom.