Integrations
Gong
Connect Gong and your recorded customer calls arrive on the right deal as call notes — readable by your team, and read by Marvin when it analyses the deal.
Gong records, transcribes and summarises your sales calls. OppFlow does not duplicate any of that. It takes the summary Gong already produced, files it against the opportunity the call belongs to, and makes it part of the deal's record — so the next person to open that deal sees what the customer actually said, without opening a second tool.
What arrives, and where
Once Gong is connected, OppFlow checks it hourly and writes one call note per eligible call. Eligible means a customer call OppFlow can match to a deal or an account: a call the host marked private in Gong is always skipped, internal calls are skipped unless you turn them on, and a call that matches nothing is not written at all. The note carries Gong's own analysis of the conversation: the brief, the key points, the highlights, the call outcome, who attended, and the topics and tracker hits it detected — plus a link straight back to the call in Gong.
Call notes sit alongside your own notes, on the deal and on the Notes page. They are dated by when the call happened, not by when they were imported, so a first sync that reaches back a month files everything in the right order rather than stacking a hundred calls on today.
What a call note looks like
**Discovery call** · 2026-08-21 · 34 min · [Open in Gong](…)
Dana walked through their current review process and the two
approvals that add a week to every renewal…
## Key points
- Budget is approved for Q4; procurement is the long pole
- Security review must complete before signature
## Highlights
### Pricing
- Asked whether the per-seat price holds at 400 seats
## Next steps
- Send SOC 2 report and the DPA
- Intro call with their security lead
## Participants
- Dana Reyes — VP Engineering, Acme (external)
- Sam Ortiz — Account Executive, OppFlow
## Topics
Pricing (4:20) · Security review (6:05)How a call finds its deal
Gong is already connected to your CRM, so it usually knows which opportunity a call belongs to, and OppFlow simply uses that. When it does not, the rules get deliberately more cautious the less Gong knows:
| What Gong knows about the call | Where the note lands |
|---|---|
| The opportunity | That deal |
| The account, and it has one open deal | That deal |
| The account, and it has several open deals | The account only — never a guess between them |
| Nothing, but an attendee is a known contact | That contact's account, and its deal if there is only one |
| Nothing at all | No note is written |
Putting a call on the wrong deal is worse than leaving it off: it puts one customer's words into another customer's record, and every later analysis reads it as evidence. If a call is landing in the wrong place, fix the link in Gong or in your CRM — the next sync follows it.
OppFlow uses the CRM link that exists now, not the one that existed on the day of the call. So re-linking a call in Gong moves its note on the next sync — provided the call is still inside the sync window, which reaches back 48 hours. A re-link on an older call is not picked up, because nothing revisits calls that far back.
Connect Gong
Gong grants API access at the company level — there is no per-user Gong login. So one admin connects it once for the whole organisation, in App Settings › Calls, and it covers everybody.
You need: the Technical Administrator role in Gong, and admin in OppFlow.
- In Gong, open Company Settings › Ecosystem › API.
- Create an API key. Copy the access key and the access key secret.
- Copy the base URL from that same page. It is specific to your Gong region — something like
https://us-12345.api.gong.io, not a single global address. - In OppFlow, go to App Settings › Calls, paste all three, and connect.
A perfectly valid key sent to the wrong Gong region is rejected as invalid, which looks exactly like a bad key. Copy the base URL from the same settings page as the key — do not type it from memory. Your credentials are verified against Gong before they are saved, so a mistake fails at the moment you connect rather than showing “Connected” and quietly importing nothing for a day.
If your deployment has a registered Gong app, Connect with Gong (OAuth) appears as well and skips the key handling entirely; Gong returns the region base URL itself. Everything below applies to both modes.
Settings
| Setting | Default | What it does |
|---|---|---|
| Backfill window | 30 days | How far back the first sync reaches, capped at a year. It is read once, on that first sync — every later run starts from where the previous one finished, so raising it afterwards does not pull in older calls. |
| Include transcripts | Off | Appends the full transcript under each summary. Useful for finding exact words; it makes notes very long, and long notes crowd out everything else on the deal. |
| Include internal calls | Off | A pipeline review is not a customer conversation. Filing one as a call note puts your own words into the record of what the customer said. |
| Sync interval | Hourly | How often OppFlow checks Gong. |
Sync now pulls immediately instead of waiting for the next hourly check. The settings page also shows the last sync time, how many calls and notes it produced, and the last error if there was one.
Timing: why a call is not there yet
Gong's AI summary is not ready the moment a call ends — the brief and key points appear minutes to hours later. Two things follow, and both are deliberate:
- A call recorded minutes ago may arrive before Gong has finished analysing it. The note says so, and fills itself in on a later sync rather than sitting there empty or silently never appearing.
- Every sync re-reads the last 48 hours, not just what is new since the last run. That is the only way to pick up a summary Gong generated after we first saw the call. Re-reading is free: a note whose content has not changed is not rewritten.
Call notes are read-only
A call note belongs to Gong, so nobody can edit it in OppFlow — the next sync would overwrite the change, and a product should not offer an edit it intends to discard. Open it to read it, or follow the link to hear the recording in Gong. Your own notes on the same deal are unaffected.
A call note is bylined with its Gong host where Gong tells us who that was, and Gong otherwise.
Deal analysis
Call notes are not just something to read. On any deal, Deal analysis reads the picture at once — the deal record, its most recent call summaries and notes, recent activity, and product-usage health — and comes back with where the deal stands, what the customer actually said, the risks, and what to do next. It reads the most recent evidence rather than the entire history: a deal with a year of calls would otherwise be summarised mostly out of material that no longer matters.
The result is cached on the deal and stamped with the date it was produced, so the deal page and Marvin read the same analysis and neither re-runs it for nothing. Opening a deal shows the cached analysis and never bills you for a model call. When the evidence moves on — a new call note, a new activity, a stage or amount change — the cached analysis is marked out of date; Analyze or Re-analyze then produces a fresh one. Nothing recomputes until someone asks for it.
Every analysis states what it was based on. One built on six recorded calls and one built on none are not the same claim, and the card tells you which one you are reading. Marvin will do the same from chat: ask how a deal is going, or what happened on the calls.
Security and privacy
- No audio, ever. OppFlow does not request Gong's recording-URL permission, so no audio or video link is stored here. A call note links back to Gong, where your existing Gong permissions still apply — someone who cannot hear a call in Gong cannot hear it through us.
- Read-only. The permissions requested are call metadata, call content, transcripts and the user directory. Nothing OppFlow does writes back to Gong.
- Credentials are encrypted at rest and never shown back once saved. To change a key, connect again with the new one.
- Transcripts stay off unless you turn them on, per organisation.
Troubleshooting
| Symptom | Almost always |
|---|---|
| Connecting fails with an authentication error | The base URL is for a different Gong region, or the key was created without Technical Administrator. Re-copy both from Company Settings › Ecosystem › API. |
| Connected, but no notes | The calls in the window are internal (and internal calls are off), or Gong has not linked them to a CRM record and no attendee matches a known contact. |
| A note exists but the summary is thin | Gong had not finished analysing the call when we read it. It fills in on a later sync. |
| The note is on the wrong deal | Fix the CRM link on the call in Gong. The next sync follows it. |
| Older calls are missing | They pre-date the backfill window, which applies only to the first sync. Raising it afterwards does not reach back — later syncs run from where the last one finished. Ask support if you need a historical re-import. |
| Sync reports a rate-limit error | Gong caps API use per company per day, shared with anything else using the same key. It resolves itself on the next run. |
Disconnecting
Disconnecting stops new call notes arriving and keeps the ones already imported. They are the record of conversations that really happened, and your deal timelines and past analyses are built on them. Reconnecting resumes from the backfill window.
Marvin can answer most of this from inside the product, and Support in the left nav files a ticket with the OppFlow team. If a sync is failing, quote the error shown in App Settings › Calls — it names the cause.