Sales calls often hold the most useful deal context, but that context is easy to lose if it stays trapped in a call intelligence tool. HubSpot gives the pipeline view. Gong gives the conversation view. The integration brings those two together so managers and reps can see the story of a deal without jumping between tools.
That matters because a pipeline stage alone does not tell you much. A real forecast needs call notes, objections, competitor mentions, next steps, and a sense of whether the buyer is actually moving forward. Gong captures a lot of that detail, and HubSpot becomes more useful when that context shows up where the CRM team already works.
For teams that rely heavily on calls, the Gong HubSpot integration and HubSpot and Gong integration are less about convenience and more about better decision-making. The integration connects call intelligence with CRM pipeline data so the team has the full picture in one place.
What the HubSpot Gong Integration Does
The integration syncs call activity, summaries, recordings, notes, and selected conversation insights into HubSpot. That gives sales leaders more context in the CRM and gives reps a better memory of what happened on the call without having to rebuild the story manually.
It also helps make coaching easier. Managers can review how calls are going, identify recurring objections, and check whether reps are updating HubSpot in a way that actually reflects what was said on the call. The value is not just data storage. It is turning conversations into something the team can act on.
When the sync is configured well, HubSpot becomes a stronger operational record of the deal, not just a place where the pipeline stage lives.
Setting Up the HubSpot Gong Integration
Setup usually starts with connecting the accounts, choosing which call events should sync, and deciding how the data should land in HubSpot. The first pass should focus on the basics: call status, participant details, deal association, and the most useful summary fields.
The team should test the integration with a real call and verify that it attaches to the correct contact or deal. That is one of the most important steps because a call summary that lands on the wrong record is more frustrating than having no summary at all.
Once the core sync works, the team can decide whether it wants to bring in deeper metadata such as talk ratios, keywords, or coaching signals.
Using Gong Insights to Improve HubSpot Deal Quality
Gong is especially useful for understanding what is happening underneath the pipeline stage. A deal marked as “proposal sent” may still be at risk if the last call exposed a budget concern or a competitor issue. That call context should be visible in HubSpot so the rep and manager know what to do next.
The integration helps teams spot patterns too. If the same objection keeps appearing across multiple calls, the business can adjust messaging, pricing, or sales enablement instead of treating each bad call as an isolated problem.
That is where the integration starts to pay off beyond simple note-taking. It becomes a feedback loop for the whole sales process.
Gong Forecasting With HubSpot CRM Data
Forecasting is stronger when call intelligence is attached to CRM data. HubSpot shows the expected pipeline movement, while Gong helps reveal whether the buyer actually sounds committed. That combination makes forecast conversations more grounded.
Need Expert Help With Your HubSpot + Gong Integration?
Our certified HubSpot partners handle setup, field mapping, sync optimization, and ongoing support.
The integration can support this by giving managers a better read on call frequency, objection patterns, and whether reps are leaving next steps vague. A strong forecast needs more than stage hygiene. It needs evidence that the deal is moving in the right direction.
In other words, the integration helps leaders judge whether the number in the CRM is supported by real buying behavior.
Advanced Gong + HubSpot Workflows You Can Build After Setup
Teams using Gong Engage can extend the HubSpot integration further: the Gong Engage HubSpot integration connects Gong’s automated outreach sequences to HubSpot contact records, keeping engagement activity visible in the CRM. A common question is whether Highspot and Gong serve the same role — Highspot Gong integration is a separate setup that combines sales enablement content (Highspot) with call intelligence (Gong), and it does not replace or overlap with the HubSpot integration. Coaching summaries, call notes, and next steps from Gong flow into HubSpot regardless of whether Highspot is also in use.
After the basic sync is stable, teams can build workflows around call outcomes. A call with a competitor mention can trigger a follow-up task. A call with no next step can flag the deal for review. A call that shows strong intent can move a contact into a more active sequence.
Managers can also use Gong insights to standardize coaching. If a rep consistently misses key questions or fails to confirm next steps, that pattern can be reviewed directly in the CRM rather than buried inside a separate reporting tool.
The more the workflows reflect real sales behavior, the more helpful the integration becomes.
How to Keep Call Data Useful in HubSpot
One risk with call intelligence is overload. If the sync sends too much data into HubSpot, the CRM becomes harder to scan instead of easier. The goal should be to surface the call context that helps action, not every possible detail from the conversation.
That usually means deciding which call fields are worth storing in the CRM, which are better left in Gong, and which should only appear in a summary or coaching view. The best setup keeps the record readable for reps who need to move quickly.
If users cannot tell what matters at a glance, the integration is probably trying to do too much.
Common Problems and How to Fix Them
Gong calls are not matching to the correct HubSpot deals
This usually means the matching rules are too loose or the deal ownership structure is not consistent. Review the contact, company, and deal association logic so the call lands in the right place.
Accurate matching is more important than broad syncing.
Gong call summaries in HubSpot are too long to be useful
If the summaries are overwhelming, the integration may be sending too much text into the CRM. Trim the fields that are synced or format the summary so it is easier to read during a normal pipeline review.
The CRM should be scannable, not cluttered.
Reps are using Gong but not updating HubSpot after calls
That often means the workflow is not making the CRM entry obvious enough. If Gong insights do not trigger a visible change in HubSpot, the team may still see the CRM update as optional.
The sync works best when the CRM reflects the call outcome in a way the team trusts.
One-way sync creates duplicate records
When the integration cannot reliably match records, it may create new ones instead of updating existing ones. Tighten the match logic and make sure email and deal ownership are being used consistently.
Duplicate records make the integration feel less reliable than it really is.
Field mapping breaks after a platform update
Field names, object structures, and available properties can shift after updates. A small test list makes it much easier to catch those breaks early before they affect the entire team.
Maintenance matters even when the integration is already live.
Automation workflows trigger twice when sync is active
That usually means more than one automation is watching the same call event. Audit related workflows and remove overlapping triggers so the same event does not create two actions.
Clean event design is the simplest fix for duplicate automation.
Gong Engage and HubSpot Integration
Gong Engage is Gong’s sales engagement product — a sequences and outreach layer built directly inside the Gong platform. When teams use Gong Engage alongside HubSpot, the integration means outreach activity from Gong Engage (emails sent, calls made, steps completed) can be written back to HubSpot contact and deal records. This keeps the CRM as the authoritative record of all sales activity, even when outreach is being run from Gong rather than HubSpot Sequences. For teams evaluating whether to run sequences in HubSpot or in Gong Engage, the key consideration is where the team spends most of their working time and which tool’s reporting they rely on for management review.
Gong Forecasting and HubSpot
Gong’s forecasting feature uses conversation signals — call frequency, topic patterns, competitor mentions, engagement levels — to add a predictive layer on top of standard CRM pipeline data. When Gong is integrated with HubSpot, Gong’s forecasting pulls deal stage and value information from HubSpot and overlays its own risk and momentum scoring. The result is a forecast that reflects both pipeline data (from HubSpot) and behavioral signals (from Gong calls). For sales leaders who find standard CRM-based forecasting too optimistic because reps self-report stage movement, Gong forecasting adds an objective layer based on what is actually being said on calls.
How to Prepare Your CRM Before Implementing Gong
Before the HubSpot Gong integration goes live, the CRM should be in good enough shape that Gong can match calls to the right contacts and deals reliably. The most important preparation steps: clean up duplicate contacts (Gong matches calls by email and phone number), ensure active deals have correct ownership and stage data, and verify that the HubSpot account connecting to Gong has admin-level access so the integration can read all pipelines. CRM readiness before implementing Gong determines whether the integration adds clarity or noise from day one.
Frequently Asked Questions
Does Gong replace HubSpot reporting?
No. Gong adds conversation context, but HubSpot still matters for pipeline, ownership, and CRM reporting.
What is the biggest benefit of the integration?
The biggest benefit is seeing call context and deal status together so reps and managers can make better decisions faster.
What should be synced first?
Start with the call summary, deal association, and the fields that help the team understand next steps without cluttering the CRM.
How do I troubleshoot sync errors?
Check matching rules, field mapping, and trigger overlap first. Those are the most common reasons the sync behaves strangely.
Frequently Asked Questions
- Where does Highspot with Gong overlap on coaching, call summaries, and notes?
- Highspot and Gong serve different but complementary roles in a revenue tech stack. Gong captures and transcribes sales calls, generates AI-powered call summaries, scores conversations against best practices, and surfaces deal risk signals from what reps actually say. Highspot is a sales enablement platform focused on content management, playbooks, and onboarding—it helps reps find and use the right content at the right deal stage.
The overlap appears in coaching workflows: Gong’s call recordings and coaching scorecards can be linked within Highspot’s digital sales rooms and training tracks, so managers can tie conversation behavior back to enablement content. Call notes generated by Gong can be referenced in Highspot coaching sessions. However, Gong does not replace Highspot’s content library or guided selling flows, and Highspot does not replace Gong’s conversation intelligence. Teams that use both should define clear ownership: Gong owns call review and deal signals; Highspot owns content delivery and rep readiness.
Connecting Gong with HubSpot and Salesforce for Pipeline Insights
To connect Gong with HubSpot or Salesforce for pipeline insights, the integration works bidirectionally: Gong pulls contact, account, and deal data from the CRM to contextualize call recordings, and pushes call summaries, next steps, and engagement signals back as CRM activities. In HubSpot, Gong activities appear in the contact and deal timeline. In Salesforce, Gong creates Task records associated with the Opportunity. This gives revenue managers a single view of both pipeline stage (in the CRM) and conversation health (via Gong signals) without switching tools.
Does Gong integrate with HubSpot? Yes—Gong (Gong.io) has a native HubSpot integration that syncs contacts, deals, and call data. Setup requires connecting your Gong workspace to HubSpot via Gong’s integration settings and mapping which Gong call outcomes and next steps should write back to HubSpot deal properties.
Highspot and Gong: Avoiding Duplicate Summaries and Notes
When both Highspot and Gong are deployed in the same sales stack, the most common operational issue is duplicate call summaries and AI notes. Gong generates AI-powered call summaries and next steps after every recorded call. Highspot’s Copilot (if AI meeting assistance is enabled) may generate parallel notes. To avoid duplication:
- Designate Gong as the sole call recording and summary tool; disable Highspot’s meeting AI for recorded calls where Gong is the recorder.
- Use Highspot to surface Gong call recordings inside digital sales rooms and playbooks, rather than running parallel AI note-taking.
- Sync Gong’s deal signals into the CRM, and let Highspot pull from the CRM for its Copilot context—so both tools draw from the same source rather than generating independent summaries.
Does Highspot with Gong improve forecast quality more than either alone? Generally yes—when Gong’s conversation risk signals (e.g., competitor mentions, multi-threading gaps, deal velocity drop) are visible to managers in Highspot’s coaching sessions, forecast accuracy improves because coaching interventions happen before deals slip rather than after. The combination works best when the CRM is the shared data layer that both tools read from and write to.
Highspot Meeting Recordings Not Syncing with Teams or Zoom When Gong Is Active
A common issue in stacks where Highspot, Gong, and Microsoft Teams or Zoom are all deployed is that Highspot meeting recordings fail to sync while Gong is the primary recorder. The root cause is usually a recording permission conflict: both Gong and Highspot’s meeting AI attempt to join calls as a bot recorder, and the second bot is either blocked by meeting settings or dropped silently. To resolve this, designate Gong as the sole bot recorder for all sales calls in your Teams or Zoom admin settings. Disable Highspot’s automatic meeting recording for calls where Gong is already recording. Highspot can still surface Gong recordings inside digital sales rooms — it does not need to re-record the call independently to do so. After making this change, verify that Gong call recordings are appearing in both Gong’s call library and the connected HubSpot deal timeline before closing the support ticket.
Additional Questions
How do I get Gong pipeline insights inside HubSpot?
Once Gong is connected to HubSpot, pipeline insights surface in two places: in Gong’s own Deals view (which reads deal data from HubSpot and overlays conversation signals), and in HubSpot deal records (where Gong pushes call summaries, next steps, and engagement alerts as timeline activities). To get the most from Gong’s pipeline intelligence in HubSpot, make sure your HubSpot deal stages, close dates, and deal values are kept current — Gong’s risk alerts and forecast signals are calculated against that deal data. Stale deal records produce inaccurate signals.
What does the Gong HubSpot integration actually sync?
Gong reads: contact records, company records, deal records (stage, close date, value, owner), and associated email addresses from HubSpot. Gong writes back: call summaries, AI-generated next steps, call disposition notes, and engagement alerts — all as activity records on the relevant HubSpot contact and deal. Field-level writeback (pushing Gong data into specific HubSpot deal properties) can also be configured for custom fields like “Last Gong Activity Date” or “Competitor Mentioned.”