Connect Gong
Connect Gong so Adduce pulls your recorded sales calls in as transcripts and reads what the people on them actually said.
Adduce pulls your recorded Gong calls in as transcripts, then reads them the way it reads a transcript you upload yourself: one piece of evidence per point a customer made.
Beta
This connector works, but it has not been proven against a real customer account yet, so Adduce badges it Beta wherever it appears. Tell us at hello@adducehq.com if what you see does not match this page.
Before you begin
- Role: project Editor or Lead. A workspace Admin is a lead on every project.
- In Gong: a technical administrator who can create API keys.
- To hand: the API base URL your company uses, an access key, and its secret.
- Time: ten minutes, most of it waiting for your Gong administrator.
What Adduce reads
| Surface | What it becomes |
|---|---|
| Recorded calls | One transcript per call, named after the call and its date, with each speaker marked |
| The words in them | Evidence in the speaker's own words, the same as for an uploaded transcript |
Only calls Gong has already transcribed come across. A call whose transcript is not ready is left alone and picked up on a later sync, rather than landing as an empty file.
Permissions the key needs
| Access to | Why |
|---|---|
| Listing calls | find the calls recorded in the window being read |
| Call details | resolve who was on each call, so the transcript is attributed |
| Call transcripts | read what was said |
Your Gong administrator grants these when the key is created. Nothing is written back: Adduce never edits a call, a note or a deal.
Steps
In Gong, ask a technical administrator to open Company settings → Ecosystem → API and create an access key with the three kinds of read access above. The secret is shown once, when the key is made.
Take the API base URL from that same page. Most companies use https://api.gong.io; some are given a company-specific address instead.
In Adduce, open the project, choose Sources, then Add source, and choose the Gong tile.
On Connection details, name the source, choose the API base URL — or Company-specific URL and paste yours — and enter the access key and its secret.
Choose Continue. Adduce asks Gong for one day of calls with your key, which proves the base URL, the key pair and the read access in a single request.
Back on Sources, the new row shows Connected. Once the first sync has run it reads as a number of calls, and a signal count beside that as soon as the transcripts have been read.
Open the source to see the calls themselves. The list is read-only — calls arrive from Gong, so there is no upload button here.
First sync and cadence
The first sync reads ninety days of calls, up to a hundred in one run; if there are more, the rest arrive on the following runs, oldest first. After that Adduce reads from a week behind its watermark, because Gong finishes transcribing some time after the call ends and that overlap is what catches them. A call already held is recognised and skipped, so the overlap costs nothing.
Adduce syncs once a day at 03:00 UTC, and Sync now runs one immediately. Each transcript is then read on its own, so one call that cannot be processed is marked failed on the source's list and the rest still land.
Disconnect or replace credentials
Delete the source from its page and type its name to confirm. Deleting removes the transcripts it pulled and the evidence they produced. To rotate the key, delete the source and add it again; the next sync backfills ninety days.
If it did not work
Why does it say the access key is too short?
The key or the secret was pasted part-way. Gong shows the secret once, at creation, so if it was not captured then a new key is the only way forward.
Why was the API base URL refused?
Adduce only calls Gong's own hosts: api.gong.io, or the company-specific address Gong assigned you, which ends in api.gong.io. Anything else is refused before a request is made, because that request would carry your key.
Why did calls arrive with no evidence?
Either their transcripts were not ready when the sync ran — they will come across on a later run — or the calls were read and produced nothing quotable. Failed transcripts are listed on the source's page with the reason.