LeadHaste

Gong + HubSpot Integration Guide: Full Setup 2026

Free Pilot →

Gong + HubSpot Integration Guide: Full Setup 2026

Dimitar Petkov
Dimitar Petkov·May 4, 2026·9 min read
Gong + HubSpot Integration Guide: Full Setup 2026

The Gong HubSpot integration is one of the most valuable pairings in a modern B2B sales stack, and one of the most commonly under-configured. Gong captures every customer conversation (calls, demos, emails, video meetings) and turns them into structured intelligence about deal health, buyer signals, and rep performance. HubSpot is the CRM that holds the deal record, the contact and company history, and the workflow automation that drives the sales process. Wired together correctly, the combination gives sales leaders a real-time picture of pipeline health and gives reps automatic call-to-CRM data flow without manual logging.

Wired together poorly, the integration creates duplicate activity records, broken deal-stage automation, and a CRM where every Gong-logged call lives outside the relevant deal. This guide walks through the full setup of the Gong HubSpot integration in 2026, the field mapping decisions that matter, the automation patterns that work, and the operational mistakes we see most often when reviewing client stacks.

What The Gong HubSpot Integration Does

Before the setup, the scope. The Gong HubSpot integration supports four core capabilities:

1. Call and meeting sync. Gong-recorded calls and meetings push into HubSpot as Activities, attached to the right contact, company, and deal records. 2. Email sync. Emails captured by Gong (from Gmail or Outlook integration) push into HubSpot as Email activities. 3. Deal intelligence sync. Gong's deal-level insights (warnings, scores, signals like "no champion identified" or "decreasing engagement") flow into HubSpot as custom properties on the Deal record. 4. CRM-to-Gong sync. HubSpot deal data (stage, amount, close date) flows back into Gong, which lets Gong's analytics segment by HubSpot stage and run forecast modeling.

All four are valuable, but most teams set up only the first two and miss the bigger ROI in the third and fourth. The setup below covers all four.

Step 1: Pre-Setup Decisions

Before clicking through the integration setup, decide:

Which Gong calls and meetings should sync to HubSpot? All recorded conversations, or only those associated with active deals? Most teams want all calls to sync (so demo calls, support calls, and onboarding calls are all in CRM), but some teams have privacy or noise concerns. Pick a default and document it.

How should Gong match calls to HubSpot deals? Gong matches based on attendees and email domain. The match logic is configurable. The choice is between auto-match (Gong attaches the call to whatever deal seems closest) and manual-match (calls land unattached and reps decide). Auto-match is the default and works for most teams.

Which deal intelligence properties do you want in HubSpot? Gong exposes a lot of signals. Pick the 5 to 10 that matter most for your pipeline reviews and forecasting, not all of them. Bloating the Deal property list creates UX friction.

Step 2: Install The Gong HubSpot Integration

From your Gong admin account:

1. Open Gong's web app and navigate to Settings → Integrations. 2. Find HubSpot in the integration directory and click "Connect." 3. Authorize Gong to access your HubSpot portal. This requires a HubSpot account with Super Admin permissions or appropriate scoped permissions. 4. Choose which HubSpot portal to connect (if you have multiple). 5. The integration will run an initial sync. Allow 30 minutes to several hours for the first sync depending on Gong volume.

Use a dedicated integration account or app if your security policy requires it. The default OAuth flow uses the connecting user's credentials.

Step 3: Configure Activity Sync

Once connected, navigate to Gong → Settings → CRM → HubSpot to configure activity sync. The settings to configure:

Sync calls and meetings. Enable. This pushes Gong-recorded conversations as HubSpot Activities (Call or Meeting type).

Activity attribution. Choose whether the activity is attributed to the host (the rep who scheduled the call), the participants (each rep on the call gets attribution), or both. Attribution affects reporting downstream.

Activity title format. Gong defaults to "Call with [Customer Name]." You can customize this. We typically leave it as the default.

Sync historical conversations. Choose how far back to backfill. Gong will sync historical calls for whatever window you specify. Longer windows are higher-value but slower to complete.

Email sync. If you use Gong's email capture, enable email sync to HubSpot. This pushes captured emails as HubSpot Email activities.

Step 4: Configure Deal Intelligence Sync

This is where the high-leverage configuration lives. Navigate to Gong → Settings → Integrations → HubSpot → Deal Properties.

Map Gong's deal intelligence to HubSpot custom properties. The most useful Gong signals to surface in HubSpot:

- Gong Deal Score - Gong Risk Warnings (free-text concatenation of active warnings) - Gong Last Customer Engagement Date - Gong Champion Identified (yes/no) - Gong Multi-thread Count (number of unique contacts engaged in the deal) - Gong Activity Trend (increasing/decreasing/flat over the last 14 days) - Gong Mentioned Competitors (which competitors came up in calls) - Gong Pricing Mentioned (yes/no for the deal)

Create custom Deal properties in HubSpot for each of these (with "Gong_" prefix for clarity), then map them in the Gong integration settings.

Sync frequency. Real-time or near-real-time is the right setting. Stale Gong data in HubSpot defeats the value of the integration.

Step 5: Configure CRM-to-Gong Sync

For Gong's analytics and forecasting to work, HubSpot deal data needs to flow back into Gong. Configure:

- Deal Stage → Gong Stage (so Gong knows which deals are at which pipeline stage) - Deal Amount → Gong Deal Amount - Close Date → Gong Expected Close Date - Owner → Gong Owner - Pipeline → Gong Pipeline (if you have multiple HubSpot pipelines)

This enables Gong's forecast model and lets pipeline analytics segment by HubSpot stage. Without it, Gong's deal-level reporting is decoupled from your CRM source of truth.

Step 6: Field Mapping And Custom Properties

Beyond deal intelligence, you may want to sync additional fields. The mapping we recommend for a typical B2B SaaS team:

Gong FieldHubSpot PropertyObjectNotes
Call IDGong_Call_ID__cActivityFor deduplication
Recording URLGong_Recording_URL__cActivityQuick access
Call ScoreGong_Call_Score__cActivityCoaching signal
Trackers (topics mentioned)Gong_Trackers__cActivityWhat was discussed
Deal ScoreGong_Deal_ScoreDealPipeline health
Risk WarningsGong_Risk_WarningsDealHealth flags
Last Customer ActivityGong_Last_Activity_DateDealEngagement freshness
Multi-Thread CountGong_Multi_ThreadDealBuyer involvement

Document the mapping in a shared doc. RevOps and CRM admins change. The next admin needs to understand why the mapping is what it is.

Step 7: Build Workflows On Top Of Gong Signals

This is where the real ROI lives. The Gong HubSpot integration's value is not the activity sync, it is the workflows you build on top of the deal intelligence properties. The patterns we set up for clients:

At-risk deal alerts. When Gong's deal score drops below a threshold or a risk warning is added, trigger a HubSpot workflow that notifies the deal owner and their manager. Add the deal to a "needs review" view.

Stalled-deal automation. When Gong's "Last Customer Engagement Date" is older than [X] days, trigger an internal task and a follow-up email queue.

Multi-threading enforcement. When Gong's "Multi-Thread Count" is 1 or below for a deal at [stage X], trigger an alert. Single-threaded deals at late stages are a major risk.

Competitor mention routing. When Gong detects a competitor mention in a call, trigger a workflow that adds a battlecard link to the deal note and notifies the sales engineering team.

Forecast adjustment. When Gong's deal score and the rep's deal stage diverge significantly (rep is calling commit, Gong score is poor), surface the deal for forecast review.

These workflows are what convert Gong from a "call recording tool" into a "pipeline intelligence layer." Most teams stop at activity sync and miss this entirely.

Step 8: Hygiene And Ongoing Care

The integration needs ongoing care:

- Monthly review of unmatched Gong calls. Calls that did not auto-match to a deal sit unattached. Review the unmatched list and either manually attach or refine the matching logic. - Quarterly review of deal property usage. Are the Gong-prefixed Deal properties actually being used in workflows and reports? If not, consider unmapping them to reduce schema bloat. - Quarterly workflow audit. Are the Gong-driven workflows still firing correctly? Are they producing useful outcomes? Adjust thresholds based on what actually predicts deal outcomes. - Permissions audit. Make sure the Gong-mapped HubSpot properties are visible to the right user roles. Some Gong signals are coaching-sensitive and should be limited to managers.

Common Setup Mistakes

Skipping deal intelligence sync. The activity sync is table stakes. The deal intelligence sync is where the value lives. Many teams enable only the first.

Mapping every available Gong field. Schema bloat hurts more than it helps. Pick the 8 to 12 fields that actually drive workflows.

No CRM-to-Gong sync. Without HubSpot stage and amount flowing back to Gong, Gong's analytics are decoupled from your source of truth. Forecast accuracy suffers.

No workflows built on top. The integration without workflows is a search index. With workflows, it is a pipeline intelligence layer. The work is in the workflow design.

Letting unmatched calls accumulate. Over months, unmatched calls become impossible to retroactively connect. Run a monthly review.

Where Gong Plus HubSpot Lives In The Outbound Stack

The Gong HubSpot integration sits at the bottom of the funnel, where booked meetings turn into deals. The full outbound stack we run for clients includes:

- A list and enrichment layer for prospect data - A sending and orchestration layer for outbound campaigns - HubSpot as the CRM and pipeline source of truth - Gong as the conversation intelligence layer - A forecasting and reporting layer that combines all of the above

Gong plus HubSpot is the deal intelligence and pipeline layer. The outbound layer that feeds it is what we build for clients.

The teams who get the most out of Gong are not the ones with the best activity sync. They are the ones who built workflows on top of Gong's signals to actually change rep behavior in real time. - Dimitar Petkov, LeadHaste

Ready To Build The Outbound System That Feeds Gong And HubSpot?

The Gong HubSpot integration tells you how your deals are progressing. The outbound system creates the deals in the first place. We build the outbound system, run it end-to-end, and hand you booked meetings that flow into HubSpot, get recorded by Gong, and turn into pipeline.

Book your free pilot →

We design the sequences, build the infrastructure, run the campaigns, and book the meetings. See our case studies for how this looks across different B2B verticals.

Frequently Asked Questions

A modern outbound stack includes: data enrichment (Apollo, Clay, ZoomInfo), email infrastructure (Google Workspace, custom domains), sending tools (Smartlead, Instantly), warm-up services (Warmbox), LinkedIn automation (Expandi, Dripify), CRM integration (HubSpot, Salesforce), and analytics platforms. Most agencies use 15–30 tools orchestrated together.

Building your own stack costs $3K–5K/month in software alone, plus a dedicated person to manage it. With a managed service, you get all the tooling plus the expertise to orchestrate it — often at lower total cost. The key question: can you afford to spend 6–8 weeks setting up instead of generating pipeline?

There's no single 'best' tool — it depends on your volume, budget, and integration needs. Smartlead and Instantly are popular for high-volume sending. Apollo doubles as a data and sequencing platform. The real advantage comes from how tools are orchestrated together, not from any single tool choice.

Look for three things: (1) Do you own the infrastructure they build? (2) Do they guarantee results or just charge a retainer? (3) Can you see transparent metrics and real case studies with specific numbers? Avoid long contracts, vague reporting, and agencies that own your domains.

Data enrichment is the process of taking basic company or contact data and adding layers of detail — job titles, direct emails, phone numbers, technographics, intent signals, company size, funding stage, and more. Enrichment tools like Apollo, Clay, and ZoomInfo pull from multiple data sources to build a complete prospect profile before outreach begins.

gonghubspotintegrationsales-stack
Dimitar Petkov

Dimitar Petkov

Co-Founder of LeadHaste. Builds outbound systems that compound. 4x founder, Smartlead Certified Partner, Clay Solutions Partner.

Newsletter

Get outbound strategies that work — delivered weekly.

Join 500+ B2B leaders getting one actionable outbound insight every week.

No spam. Unsubscribe anytime.

Ready to build outbound that compounds?

We'll build the entire system for your business. $7K+ in services, free — you only cover the infrastructure.

Book my free pilot →