Skip to main content

​
Overview

The Gong connection allows Qontext to read your recorded sales calls from Gong and sync their content into the context repository. Qontext syncs a structured summary of each call, not the raw transcript, so your AI clients get the substance of a conversation without the noise.
Only calls that the connected Gong account can access will be synced into your context repository.
Supported data types: Each call file includes:
  • Call details — title, date and time, duration, direction, scope, media type, language, purpose, and a link back to the call in Gong.
  • Participants — each participant’s name, email, phone number, and whether they are internal or external.
  • Associated CRM records — the deals, contacts, and other records Gong has linked to the call from your connected CRM (such as Salesforce, HubSpot, or Microsoft Dynamics).
  • Call outline — Gong’s structured, timestamped summary of what was discussed.
Unsupported:
Gong connects with an API key (an access key and its secret) rather than a personal login. Use a key generated for Qontext specifically, so the connection stays stable when individual employee accounts change.
Have a Gong administrator generate a dedicated API key for Qontext. Because the key inherits the permissions of your Gong API, this keeps access consistent and easy to revoke without affecting anyone’s personal account.

​
Setting up the connection

You generate an API key in Gong, then add it to Qontext and set how often it should sync. The steps below walk you through the full flow.
Generating a Gong API key requires a Gong user with Technical Administrator permissions. If you don’t have them, ask your Gong administrator to complete the first step.
1

Generate a Gong API key

Open Gong’s API settings page and click Create under Public API Access.Gong generates two values: an Access Key and an Access Key Secret. You need both. The secret is masked on the page; use Show or Copy to clipboard to retrieve it.
2

Open Sources in your workspace

In the Qontext app, open your workspace, go to the Sources tab, and click + Connect data source.
3

Select Gong as the data source

Choose Gong from the list of available data sources, and give the credential a name (for example, Sales Gong recordings). The name is only used to identify the connection inside Qontext.
4

Enter your access key and secret

Paste the value from Gong into Access key, and the matching secret into Access key secret, then confirm. Both fields are required.Qontext verifies the credential against Gong before saving it. If verification fails, the message names the reason: a rejected credential, missing permissions, a rate limit, or Gong being unreachable.
5

Choose a time window

New connections sync calls from the previous 12 months by default. Choose a different start date, or clear the time window to sync all available call history.Changing the time window later affects future syncs. Calls already stored in the context repository are not removed.
6

Set sync frequency

Choose how often Qontext should refresh data from Gong (e.g. daily, weekly, monthly). More frequent syncs keep the context repository up to date but use more resources.
7

Review and create connection

Review your choices and confirm to create the connection. Qontext starts the initial sync shortly after.

​
Managing permissions

Qontext uses your Gong API key to read calls only; it never creates, edits, or deletes anything in Gong. The connection can access exactly the calls your Gong API is permitted to see, no more.
  • Use a single, dedicated API key for Qontext so access is easy to audit and revoke.
  • To revoke access, delete or rotate the key on Gong’s API settings page. The connection stops syncing as soon as the key is invalid.

​
Sync latency

The initial sync time depends on how many calls are in scope. Large call histories can take up to 6 hours to fully sync.
Subsequent syncs are incremental and also check for calls that arrived in Gong after their original call date, so they complete much faster than the initial sync without missing late additions.

​
FAQ

Anyone in your Qontext workspace can add the connection, but generating the API key in Gong requires a Gong user with Technical Administrator permissions. In practice, a Gong administrator generates the key and hands it to whoever sets up the source in Qontext.
Qontext syncs calls that the Gong API key can access and that fall within the selected time window. Each call becomes one record containing its details, participants, associated CRM records, and Gong’s call outline.
No. Qontext syncs Gong’s structured call outline rather than the raw word-for-word transcript. This keeps the context focused on what was discussed, decided, and agreed.
Yes. You can create multiple Gong connections from the Sources tab in your Qontext workspace, each with its own API key.
Disconnecting stops further syncs. Content already synced from Gong remains in your context repository. For data removal, contact support@qontext.ai.
Check that the key is still valid on Gong’s API settings page and hasn’t been rotated or revoked. If it has, generate a new key and reconnect the source in Qontext with the new access key and secret. If the issue persists, contact support@qontext.ai.