Skip to main content

Import Gong calls

Quick start​

Connect Gong in NEXT, enable the Teamspace subscription for this import, and let the scheduled sync pull Gong calls into NEXT as Records.

Why integrate with Gong?​

Gong captures some of the highest-value revenue conversations a company has: discovery calls, demos, objections, renewals, and expansion discussions. Importing those calls into NEXT makes it easier to connect what prospects and customers say in the sales process to the rest of the customer signal landscape.

  • It brings revenue-call evidence into the same workspace as support, survey, and review data.
  • It helps product and GTM teams detect recurring objections and unmet needs earlier.
  • It reduces manual effort for getting sales-call context into analysis and automation workflows.

What gets imported​

  • Object in NEXT: Records
  • Source objects: Gong calls
  • Included fields: Call title, recording media or transcript, participants, timing, and available metadata from the Gong call record.

Authentication​

Gong API credentials entered in the integration settings.

Connection notes​

  • Connect Gong in Settings -> Integrations and provide the access credentials issued for your workspace.
  • Enable the Teamspace subscription that should receive Gong call imports.

Configuration notes​

  • You can scope imports with filters so only relevant calls are synced.
  • Sampling is supported for high-volume workspaces where you only want a subset of calls.
  • If Gong calls are linked to Salesforce accounts, NEXT derives the internal account ID from the external Salesforce Account ID plus the Teamspace project. Use the Salesforce Account ID as the stable source ID.

Filtering​

Gong subscriptions support LIQE filters. For the syntax reference, see Use LIQE filters.

Gong filters run against:

  • Every key in the Gong metaData payload, such as id, duration, direction, scope, and started
  • Flattened Gong context fields in the form System.Object.Field, such as Salesforce.Account.Industry
  • A derived boolean field: hasExternalPartyWithTitle

Examples:

  • Salesforce.Account.Segment_RevOps__c:Enterprise
  • Salesforce.Account.Segment_RevOps__c:Enterprise AND (Salesforce.Account.Industry:AI OR Salesforce.Account.Industry:Staffing)
  • duration:>=900
  • hasExternalPartyWithTitle:true

If Gong includes linked Salesforce fields in the call context, you can filter on them with the same Salesforce.Object.FieldName pattern.

Sampling Calls​

When connecting your Gong account, you may find that you have a very large number of calls. Importing all of them can be expensive and often unnecessary, especially if you just want to analyze a representative set. That’s why we offer sampling. Sampling allows you to choose what percentage of your Gong calls to bring into our system - for example, 5%, 20%, or 50%. This way, you can keep costs under control while still working with enough calls to get meaningful insights.

The way sampling works is by selecting calls at random rather than just taking the first calls in the list. This ensures that your imported calls represent the whole range of conversations across days, teams, and topics, rather than being clustered in one period. In the background, each call is given a unique identifier, and we use that to decide whether it falls into the percentage you selected. The end result: if you choose 10%, we will consistently import roughly one out of every ten calls, spread evenly across your Gong data.

One important thing to know: if you change the sampling percentage later and re-run the import from the same time period, you may see different calls appear. For example, lowering from 10% to 7% doesn’t just mean you get fewer calls - it can also mean you get a different set of calls. In most cases, this results in even more calls overall than before. This is not an error but simply how random sampling works. Keep this in mind when adjusting your percentage so you can plan your imports accordingly.

Limitations​

  • Call volume and available metadata depend on the Gong API access granted to the integration.
  • Changing sampling or filters changes which future calls are brought into NEXT.

Troubleshooting​

  • Rotate the Gong credentials if NEXT starts receiving unauthorized responses.
  • If expected calls are missing, review the subscription filter and sampling settings first.

FAQ​

What lands in NEXT?​

Each imported Gong call becomes a Record with the source transcript and call metadata when available.

Can I narrow the import scope?​

Yes. Use the subscription filter and optional sampling controls to reduce the volume. See the Filtering section above for supported Gong fields and examples.

Does NEXT AI use the transcript from Gong or create its own transcript?​

NEXT AI relies on the Gong transcript.

Can we run event-driven imports?​

No, NEXT AI only supports polling.