Gong
Capture call transcripts and participants from Gong
The Gong integration captures transcripts from your recorded Gong calls and feeds them into Modem for analysis. Each call becomes a conversation that’s grouped into topics, classified by type (bug, feature request, praise, complaint), and linked to the people and companies who spoke on it.
How it works
Modem connects to your Gong account with OAuth, authorized once by a Gong technical admin. During that exchange Gong returns a per-customer API address, and Modem targets it for every request after that.
Every 15 minutes Modem polls Gong for new calls, fetches each call’s transcript, and ingests it as a set of speaker turns threaded into a single conversation. A background job refreshes the connection’s access token before it expires, so the poller normally stays authenticated without any action from you.
Capture is poll-based, so a call shows up in Modem a few minutes after Gong finishes processing it, not instantly. When you connect, Modem also imports a one-time history of calls from the last 90 days, up to 2,000 calls. The import follows the same workspace and call-scope settings as the poller. Anything older isn’t imported.
Prerequisites
- Owner or admin role in your Modem organization, to connect and manage the integration
- A Gong technical administrator to authorize Modem’s API access. The authorization is account-wide and granted once.
- A Modem organization on the Scale plan or above, or an active trial (see the note above)
Setup
Start the connection
Go to Settings → Integrations → Gong in your Modem dashboard and click Connect Gong. Only organization owners and admins can connect.
Authorize Modem in Gong
You’ll be redirected to Gong to sign in and approve the access Modem requests. This step must be done by a Gong technical admin. See Permissions below for the exact scopes.
Choose workspaces
Back in Modem, your Gong workspaces sync automatically. Every workspace is captured by default; toggle off any you don’t want. See Subscribing to Workspaces below.
Choose which calls to capture
New connections capture external calls only. Turn the toggle off to capture internal calls as well. See Capturing Internal Calls below.
Permissions
During authorization, a Gong technical admin approves the following read-only Gong API scopes. Modem reads call content and participant identities; it does not send or modify anything in Gong.
| Scope | Why Modem needs it |
|---|---|
api:calls:read:basic |
Read basic call metadata (title, time, participants) |
api:calls:read:extensive |
List recorded calls to find new ones to ingest |
api:calls:read:transcript |
Read call transcripts |
api:users:read |
Resolve internal speakers to people |
api:workspaces:read |
Discover the workspaces in your account |
Call Access and Permissions
Does Modem authenticate as an individual Gong user?
No. Gong’s API supports authorization only at the technical-admin level, so Modem holds one account-wide credential per Modem organization. It does not act on behalf of the person who clicked Connect, and it does not hold or request per-user Gong tokens.
Whose calls can Modem read?
Every call the account-level authorization can reach, within the workspaces you’ve subscribed. Modem cannot see more than the approved authorization allows, but it also does not narrow that view down to any one user’s permissions.
Are Gong's per-user call permissions enforced inside Modem?
No. Modem does not mirror or re-apply Gong’s per-user access rules. Once a transcript is captured, it is stored against your Modem organization and is readable by every member of that organization through search, topics, and the Modem Agent, regardless of whether that person has access to the same call in Gong. If a call is private or restricted in Gong, treat capturing it in Modem as widening who can read it.
What controls do we have over which calls are captured?
Four, all set on the Modem side:
- Workspace subscriptions: the primary control. Unsubscribed workspaces are dropped before Modem ever requests a transcript, so their content never leaves Gong. See Subscribing to Workspaces.
- External calls only: skips calls where every participant works at your company, also before any transcript is requested. See Capturing Internal Calls.
- Connect time: capture runs forward from when you connect, plus a one-time import of up to 2,000 calls from the 90 days before.
- Disconnecting: stops all future capture immediately.
If certain calls must not be readable organization-wide in Modem, keep them in a Gong workspace you leave unsubscribed.
Who in Modem can connect, disconnect, or change capture settings?
Only Modem organization owners and admins. Regular Modem members can view the integration’s status and its capture settings but cannot change them.
What exactly is stored, and can we remove it?
Transcripts as speaker turns, participant identities, call metadata, the call summary, and a link back to the call in Gong (no audio or video). See What Gets Captured. Disconnecting stops future capture but leaves already-captured data in Modem; contact support@modem.ai to have it deleted.
Subscribing to Workspaces
Gong groups calls into workspaces. After connecting, the Workspaces card in Settings → Integrations → Gong lists each workspace with its own toggle. Modem only ingests calls from subscribed workspaces.
New workspaces are subscribed by default. Toggle one off to stop capturing its calls, which are then dropped before any transcript is fetched. If your account has a single workspace, there’s just one row, subscribed by default, which you can still toggle off to pause capture entirely.
Capturing Internal Calls
The External calls only toggle in Settings → Integrations → Gong controls whether Modem captures your team’s internal calls alongside customer ones. It’s on by default for new connections, and off for connections made before this setting existed, so nothing you were already capturing stopped.
A call is internal only when every participant is marked internal in Gong. If even one participant is external (or is someone Gong doesn’t recognize, which is how most prospects and customers show up), the call is captured. Calls where Gong provides no participant information are captured too, so a gap in Gong’s data never silently drops a customer conversation.
Internal calls are dropped at the same point unsubscribed workspaces are: before Modem requests the transcript, so their content never leaves Gong.
Turn the toggle off if you want internal calls (standups, planning, retros) analyzed alongside customer conversations. Leave it on to keep Modem focused on calls with people outside your company.
What Gets Captured
For each captured call (one in a subscribed workspace that also matches your call scope), Modem captures:
Transcript
The call transcript as ordered speaker turns, threaded into a single conversation per call so it groups into topics like any other source.
Participants
Each speaker’s name and email where Gong provides them, tagged internal or external, and resolved into people and companies.
Where Gong has already linked a participant to a record in your CRM, Modem also stores that link as a reference: the CRM system (for example Salesforce or HubSpot), the object type, and the object ID. Modem does not connect to your CRM or read the records themselves; it only keeps the identifiers Gong attaches to the call.
Call metadata
The call title, start time, duration, and a link back to the call in Gong.
Call summary
Gong’s AI call brief is stored as the conversation’s description. Gong often publishes the brief after the transcript, so a call captured before its brief exists uses the call’s purpose field instead, and keeps it: a brief published later does not replace the purpose. When a call has neither a brief nor a purpose, Modem checks back hourly, for calls up to a year old, and fills in the brief once Gong publishes it.
Analyzing Gong Conversations
Once transcripts are flowing, ask the Modem Agent about them from the web dashboard like any other source.
Troubleshooting
I don't see Gong in Integrations
Gong is available on the Scale plan and above (and during a trial). On other plans the card is locked under Settings → Integrations. Upgrade from Settings → Billing, or email support@modem.ai.
New calls aren't showing up
A call appears a few minutes after Gong finishes processing it, plus up to the 15-minute poll interval, so allow some time. Calls older than the one-time import at connect (the last 90 days, up to 2,000 calls) aren’t backfilled. If a specific call is missing, check that its workspace is subscribed in the Workspaces card.
Authorization was rejected
The person approving the connection must be a Gong technical admin with rights to authorize API access for the account. A regular Gong user can’t grant it.
Connection shows an error
Open Settings → Integrations → Gong to see the connection status. Reconnecting requires a Gong technical admin. If the error persists, contact support@modem.ai.
A workspace's calls aren't captured
Modem only ingests calls from subscribed workspaces. Open the Workspaces card and confirm the workspace is toggled on.
An internal call wasn't captured
With External calls only on, Modem skips calls where every participant is marked internal in Gong. Turn it off to capture internal calls as well. Turning it off picks up previously skipped calls only while they’re still inside the poll’s lookback window (about 48 hours from when the call started); older skipped calls aren’t backfilled. See Capturing Internal Calls.
Disconnecting
To disconnect Gong:
- Go to Settings → Integrations → Gong
- Click Disconnect and confirm
Disconnecting stops Modem from polling Gong for new calls. Historical data remains in Modem after disconnecting.