Skip to content
Enterpret Help Center home
InboxAsk a human

Gong Integration

Updated by Vaishnavi

Connect Gong as a feedback source to analyze eligible call transcripts in Enterpret. This is a workspace ingestion integration, separate from authorizing a personal tool connection in Enterpret Agent.

What you can analyze

Use processed call feedback to explore customer themes, product requests, complaints, and sentiment with the analysis tools available in your workspace. Ask focused questions in Agent where available, or the Wisdom experience retained in your workspace, and verify findings against supporting records.

What gets imported

The integration periodically retrieves eligible, non-private Gong calls and their available transcripts for the configured ingestion range. Calls marked private are excluded. Available history depends on the connection's configuration, Gong's data availability, and API access.

Sync runs in the background. Recent calls can wait for Gong processing and the integration's ingestion window; backlog and API limits can also delay processing. A connected status does not mean that every historical call has finished importing. Ask your Enterpret team to confirm the intended history range or investigate missing calls.

Before you connect

  • You need permission to manage integrations in Enterpret. Ask your workspace administrator if + New Integration or the connection action is unavailable.

  • A Gong technical administrator must authorize this shared-access integration. See Gong's shared-access authorization requirements.

  • Confirm the Gong company account and the call data your organization intends to bring into Enterpret. Imported content is governed by your Enterpret workspace access; do not assume it is a live view limited to each reader's personal Gong access.

The current authorization requests read scopes for call metadata, transcripts, media URLs, CRM integration context, and users:

  • api:calls:read:basic and api:calls:read:extensive

  • api:calls:read:transcript and api:calls:read:media-url

  • api:crm:integrations:read and api:users:read

Review the actual authorization screen. Enterpret supplies the integration's application configuration; this setup does not require you to create a custom Gong OAuth app or enter its client secret in Enterpret.

Connect Gong

  1. Open Integrations in Enterpret and choose + New Integration.

  2. Find Gong and choose Continue. Select Feedback Integration if the integration-type choice is shown.

  3. In Gong, sign in with the technical-administrator account for the intended company. Review the requested permissions and complete authorization.

  4. Return to Enterpret and check the Gong integration's connection status and the progress information available in its details.

Authorization and ingestion are separate stages. If a call is missing, check its date, private status, transcript availability, and the configured history range before reconnecting the integration.

Verify quotes and call context

Imported transcript data can include sentence timing and speaker names when Gong supplies matching participant information. A generated quote or citation is not guaranteed to display every one of those details.

Open the supporting Enterpret record and its Gong source link when available. Check the quote against the surrounding transcript and original call, including speaker and timing information where provided. Opening the Gong recording can require your own Gong access.

Generated summaries can be inaccurate or incomplete. If attribution or a source link is missing, treat it as unavailable rather than inferring a speaker or timestamp.

Check status and troubleshoot

Open the Gong entry under Integrations to review the connection health and ingestion progress available in your workspace. The exact fields depend on the interface and connection state.

For authorization errors, confirm the technical-admin account, Gong company account, and granted access. For missing data, provide Enterpret Support with the integration name, call link or ID, and date range. Do not include OAuth codes, tokens, or client secrets.