Gong

Gong brings the conversation side of your customer relationship into Sonora. Call transcripts feed sentiment analysis, eCSAT, and feature-request detection. Meeting summaries surface in customer profiles, chat, and the actions your workflows generate — so when an account suddenly looks at-risk, you can read the call where it started looking that way without leaving Sonora.

What syncs

• Call metadata (date, participants, duration, type)
• Full transcripts with speaker attribution
• Topics and trackers configured in Gong
• Workspaces and users (used to attribute meetings to the right Sonora team members)

The integration is read-only. Recordings stay in Gong; Sonora pulls transcripts and metadata.

Prerequisites

• Gong Technical Administrator role (required to issue API keys)
• The Gong API tier enabled on your account
• Your Gong region’s API endpoint (e.g. https://us-29990.api.gong.io) — visible in Company Settings → Ecosystem → API

Required API scopes

Gong grants scopes when a key is created and they cannot be edited afterward. A key missing any of these authenticates successfully but fails partway through the first import, so check them before you copy the secret.

Scope	Backs	Without it
api:calls:read:basic	Listing calls in the sync window	No calls are found at all
api:calls:read:extensive	Participants, highlights, and call context	Calls are found, then every batch fails
api:calls:read:transcript	Transcripts with speaker attribution	Calls import without transcripts

Also enable the workspace read scope so Sonora can attribute calls to the right Gong workspace.

If your Gong plan doesn’t offer api:calls:read:extensive, no key will carry it — ask your Gong account team which API tier includes it.

Setup

1. Generate a Gong API key

1. Sign in to Gong as a Technical Administrator.
2. Go to Company Settings → Ecosystem → API.
3. Click Create. Name the key “Sonora Integration”.
4. Select the scopes listed above.
5. Copy both the Access Key and the Access Key Secret. The secret is only shown once.

2. Connect in Sonora

1. Settings → Integrations → Gong → Connect.
2. Paste the Access Key, Access Key Secret, and the regional Instance URL from your Gong API page.
3. Click Test connection to confirm the credentials, then save.

The connection test checks that the key and secret are valid and that the key has all three required API scopes.

The first import pulls a configurable lookback window of calls. After that, Sonora pulls new calls incrementally on the schedule you set in the Gong card.

Customer matching

Calls match to Sonora customers via attendee email domains and Gong’s account associations. If a call is attributed to a Gong account that maps to a Sonora customer, the call attaches to that customer. Otherwise it’s stored as an unattached meeting until the relationship is resolved.

Disconnect

From Settings → Integrations, disconnect the Gong card. To revoke from Gong as well, delete the API key in Company Settings → Ecosystem → API.

Troubleshooting

“Invalid credentials” — Confirm the Access Key and Secret are correct and that the Instance URL matches your Gong region (the format is https://<region>-<id>.api.gong.io — check your API settings page).

Import fails with a 401 naming a scope — An import session that failed with a message like:

Gong API POST https://us-29990.api.gong.io/v2/calls/extensive failed with status 401:
{"errors":["You don't have permission to use 'api:calls:read:extensive' in your app."]}

means the key is valid but was created without that scope. Gong fixes scopes at creation time, so create a replacement key with the scopes listed under Required API scopes, paste it into the Gong card, and re-run the sync. Delete the old key once the import succeeds.

If you connected Gong through the OAuth flow rather than an API key, the same error means the Gong app was authorized without that permission — disconnect the Gong card and reconnect to re-consent.

Calls missing from a customer’s profile — Either the attendee emails didn’t match a known contact, or the call wasn’t associated with an account in Gong. Map the missing customer manually from the meetings list, or fix the attribution in Gong and re-sync.

Transcripts not appearing — Gong processes recordings asynchronously; transcripts can take an hour or more after a call ends to become available. Sonora retries automatically.