TL;DR: Gong’s native HubSpot integration is two-way and available on any Gong plan: it imports companies, deals, and contacts for context, and exports calls as a meeting, call, or note on the matched record — with the AI brief, highlights, and action items, but not the transcript. Budget for up to 6 hours of export latency and know that there’s no historical backfill.
Gong’s HubSpot integration is genuinely good — better documented and simpler than its Salesforce sibling (which we’ve covered in depth). But three of its design decisions surprise almost every team that turns it on. Here’s the whole picture, verified against Gong’s current docs.
What actually syncs
Into Gong: companies, deals, and contacts (standard plus selected custom fields), used to enrich and filter conversations and power deal boards. Deals not associated with a company are skipped.
Into HubSpot: each recorded call or meeting becomes a meeting, call, or note object (your choice; default is meeting) associated with the matched company, contact, or deal. The exported object carries the call name and participants, a link to the call in Gong, the “call spotlight” (AI brief, highlights, outline), AI action items, and metadata. Telephony calls — including attempts and short calls — can export too.
Not into HubSpot: the transcript. Like the Salesforce version, the full conversation text stays in Gong; HubSpot gets the summary layer and a link.
Setup in five minutes
Gong Admin center → Settings → CRM → HubSpot, then OAuth in as a user with read/write on the HubSpot contacts scope (it reads contacts, companies, deals, pipelines, owners, and engagements). Gong stores the token, not credentials. Same advice as every CRM integration: connect as a dedicated integration user, not a human who might leave.
The three surprises
1️⃣ Export latency is up to 6 hours. Gong’s own FAQ says so. If your workflow expects the call on the deal record within minutes of hanging up, this isn’t that.
2️⃣ No historical backfill. Only calls processed after you enable the integration export. Your last two years of calls stay Gong-only.
3️⃣ Deleting a call in Gong deletes the HubSpot record — including deletions by Gong retention policies. Your HubSpot activity history is only as durable as your Gong retention settings.
Also worth knowing: if Google Calendar sync is on in HubSpot, exported meetings can duplicate (the documented workaround is exporting as call or note instead), and meetings and calls must export to the same HubSpot object type — you can’t split them.
Where it stops
Configured well, HubSpot now shows that calls happened and what the AI brief said. What it still can’t tell you: how this call connects to the support tickets from the same account, the email thread that preceded it, or the commitments made two calls ago — the summary objects pile up on the timeline, but nothing reads them together. That cross-tool joining is what Noded adds on top: Gong and HubSpot both feed the Customer Context Graph, which maintains one living account story and acts on it — briefs, follow-ups, signals — wherever you work. If per-call logging into HubSpot is all you need, Gong’s native integration does it well and you should simply use it.
FAQ
Does Gong sync transcripts to HubSpot?
No — the export includes the AI brief, highlights, action items, and a link to the call; the transcript stays in Gong.
How fast do calls appear in HubSpot?
Up to 6 hours after the call is processed, per Gong’s documentation.
Can I backfill old calls?
No — the integration exports only calls processed after it’s enabled.