← Back to Home
Gong logo

Gong

Sales Intelligence

Revenue intelligence platform that records, transcribes, and analyzes sales calls.

About Gong

Gong captures the reality of sales conversations — what was actually said, agreed to, and flagged as a risk — and surfaces that as CRM data. But the sync between Gong and Salesforce is notoriously unreliable at scale. Call recordings fail to attach to opportunities, next steps disappear into Gong only, and deal signals exist in a silo that revenue leaders cannot access. Integrating Gong correctly requires understanding its async sync architecture, the API rate limit environment of your Salesforce org, and how Gong's contact-matching logic can silently orphan call records when your CRM data is not clean.

Integration Capabilities

Gong has 7 native integrations in its API directory. This page focuses only on guides we publish and maintain.

How Gong Integrations Usually Work

Start with the implementation model, not the connector. We map each pair by intent so you can decide if native sync is enough or if this workflow needs stronger controls.

Published Guides

6

Focused pages with known intent and use-case data.

Direct Paths

5

Native in at least one direction.

Connector Paths

1

Usually require mapping, retries, or approval gates.

Dominant intent for Gong: Standard setup (All hub tools (Slack, HubSpot, Sheets, Salesforce) integrate with ALL other tools. These are money pages., deal sentiment alerts) .

Common Integration Patterns

  • - Revenue Leadership Visibility: Gong captures the reality of sales conversations and syncs call recordings/insights to Salesforce/HubSpot. Enables revenue leaders to coach on deals and identify patterns without sitting in calls.
  • - Compliance & Audit Trail: Often integrated for governance — call recordings and sentiment signals create a complete record of customer interactions for regulatory/contractual purposes.
  • - Predictive Deal Intelligence: Syncs deal signals (sentiment, next steps, risk flags) back to CRM so forecasting models include conversation-level data, not just pipeline stage.

Integration Challenges

  • - Call Recording Attachment Failures at Scale: Salesforce file size limits (25-50MB) cause 15-20% of recordings to fail attachment. Large enterprise deployments often hit this silently.
  • - Deal Signals Trapped in Gong Only: Native integrations sync recordings but not deal signal insights. Signals remain read-only in CRM and cannot drive automation workflows.
  • - Contact Matching Opacity: Gong matches call participants to CRM contacts. When matching fails, recordings orphan to a contact record with no connection to the opportunity. No user visibility into why match failed.

Before You Integrate

  1. 1. Pre-Integration Data Audit: Ensure Salesforce/HubSpot contacts have standardized email and phone. Case sensitivity and formatting mismatches will break Gong matching.
  2. 2. Determine Recording Storage Strategy: Decide if recordings sync to Salesforce (native) or externally (Make/Relay). Native Salesforce will hit file limits; external storage is more reliable.
  3. 3. Create Deal Signal Properties & Workflows: Manually create CRM properties for sentiment_score, next_step, risk_flag. Native integration does not auto-create these.
  4. 4. Monitor Recording Attachment Rates: Track attachment success weekly. If below 85%, implement Make-based chunking or external storage immediately.
  5. 5. Set Up Escalation for Unmatched Calls: Create a view for calls with no matched opportunity. Assign to RevOps to manually attach or investigate contact data.

Native Integrations from Gong (5)

These guides cover integrations where Gong includes a direct native path.

Connector-Based Integrations (1)

These workflows usually need connector logic. Open each setup guide to confirm scope before choosing a platform. If you need a starting point, use the recommendations in the section above.