Skip to main content

Import Gong calls

Connecting your Gong account to NEXT enables you to import call recordings directly, so your team can analyze with highlights and tags.

Ronny avatar
Written by Ronny
Updated this week

Automatically import calls into NEXT

Once your Gong account is connected, NEXT can automatically import new Gong calls into one of your teamspaces.

When setting up Auto-import, you can define a filter so only calls matching specific criteria are imported. This is useful for bringing in only certain segments, industries, regions, or opportunities.

Using filters

The filter is a single text field that lets you describe which calls to import using Gong and Salesforce call data. You can filter on any field from Gong call metadata or linked Salesforce data (e.g., Account, Opportunity).
Examples of field names you might use:

  • duration

  • direction

  • Salesforce.Account.Segment_RevOps__c

  • Salesforce.Account.Industry

  • Salesforce.Opportunity.StageName

  • Salesforce.Opportunity.ARR__c

Basic examples

  • Only import calls for Enterprise accounts

    Salesforce.Account.Segment_RevOps__c:Enterprise
  • Import calls for Enterprise accounts in AI, Staffing, or NGO industries

    Salesforce.Account.Segment_RevOps__c:Enterprise AND (Salesforce.Account.Industry:AI OR Salesforce.Account.Industry:Staffing)
  • Import calls longer than 15 minutes

    duration:>=900
  • Import calls with ARR over 100k and stage is Evaluation or Pre-Qualification

    Salesforce.Opportunity.ARR__c:>100000 AND (Salesforce.Opportunity.StageName:Evaluation OR Salesforce.Opportunity.StageName:"Pre-Qualification")

Tips for writing filters

  • Field names must match exactly what appears in your Gong/Salesforce data

  • AND narrows results (both conditions must match)

  • OR broadens results (either condition can match)

  • Use parentheses to group conditions:

    (condition1 AND condition2) OR condition3
  • Use > >= < <= for numbers and dates

  • Use * as a wildcard:

    Salesforce.Account.RevOps_Territory_Name__c:EMEA*

For the full search syntax, see the Lucene Query Syntax documentation.

Did this answer your question?