n-Intercom and HubSpot Sync Contacts Fine. The Logic Between Them Is Still Yours to Build.
Intercom's native HubSpot integration syncs contact records both ways and surfaces each system's data inside the other, so a support conversation shows HubSpot's lifecycle stage and a HubSpot record shows recent Intercom conversations. It's a genuinely useful starting point for most teams. It stops at syncing data, though, not acting on it, and that's the piece we build when a business needs the two systems to actually respond to each other.
How Intercom and HubSpot connect out of the box
The native integration syncs contact properties in both directions and lets an Intercom conversation display HubSpot context, like lifecycle stage or the owner of the deal, while a HubSpot contact record shows a feed of that person's recent Intercom conversations. Most teams set this up specifically so support agents have marketing and sales context without leaving Intercom, and reps have support context without leaving HubSpot.
It also supports some basic workflow triggers on the HubSpot side, using Intercom conversation events (a new conversation, a tag applied) as a trigger inside a HubSpot workflow. That covers simple cases, like adding a contact to a list when they open a conversation, reasonably well.
Where it stops being enough
The trigger support is real but limited to what Intercom exposes as an event, and HubSpot workflows themselves can enroll and unenroll records against logic someone built, but can't be built or edited through an API call, the same limit that shows up whenever HubSpot workflows are involved in an integration at all. Anything conditional on data that lives outside both systems, or any action that needs to push back into Intercom based on complex HubSpot logic (a lifecycle stage change that should also update a conversation's priority, say), needs custom work against both APIs directly.
What We Built on Top of Intercom and HubSpot
A subscription business running both products had their support team manually checking HubSpot before answering billing questions, since the native sync showed lifecycle stage but not whether an account was actually past due on an invoice, data that lived in their billing system, not HubSpot. We built a Custom Action that pulls real invoice status into the Intercom conversation directly, so Fin or an agent sees the actual payment status instead of a proxy for it. We also built the reverse: a conversation tagged "churn risk" in Intercom now updates a custom property on the HubSpot contact automatically, which feeds a renewal-risk workflow the sales team already relies on. Neither direction existed through the native sync alone, since it only ever moved the two systems' own data between each other, not data from a third system neither one actually owns.
Running Intercom and HubSpot together and still filling the gaps between them manually?
Tell us what should update automatically between the two, especially anything involving data that lives outside both of them, and we'll build it on top of the native sync rather than replacing it. If the real time sink in your business is a different pair of tools entirely, we build that connection just as readily.
Let's talk