What is the Gong Integration?
The Gong integration allows Fluint to pull your call recordings, transcripts, and participant data directly from Gong into your deal workspaces. Once connected, Fluint uses that data to build deal context, populate AI-generated meeting prep, and give Olli the call history it needs to answer questions about your accounts.
The integration is read-only. Fluint ingests data from Gong but never writes anything back.
Surface | What it does |
Deal context | Call transcripts and participant data populate deal workspaces so Olli has full call history for each account |
Meeting prep | Ingested calls feed Fluint's AI-generated meeting prep and account summaries |
Olli | Ask Olli about specific calls, quotes, objections, or anything discussed in a synced recording |
Authentication & Authorization
The integration uses standard OAuth 2.0. When your admin connects Gong, they're redirected to Gong's own authorization page, approve Fluint's access, and are sent back to Fluint. No Gong credentials are stored in Fluint. The OAuth token is held by a third-party authorization layer and exchanged for scoped API access on Fluint's behalf.
What Data Flows In
Only Gong → Fluint. Nothing flows back.
From each call, Fluint ingests:
Call metadata — title, date/time, duration, direction (inbound/outbound), platform, language, privacy flag, and a link to the Gong recording
Participants — name, email, job title, phone, affiliation (internal vs. external), attendance method (invitee vs. attendee)
Full transcript — speaker-attributed text with sentence-level timestamps
CRM context — if Gong has a Salesforce Opportunity/Account or HubSpot Deal/Company linked to the call, Fluint ingests those object IDs and uses them to associate the call with the relevant deal workspace
Recording URLs — audio and video links are pulled when available (note: these expire 8 hours after generation on Gong's side)
Note: Fluint stores transcripts and metadata in its own database. It does not download or re-host Gong recordings — only the transcript and associated metadata are retained.
Sync Frequency
After the initial backfill (configurable, default 90 days), Fluint polls Gong every 2 hours for new calls. Only calls where at least one participant is a Fluint user from your organization are ingested.
Manual import and backfill tooling is also available for historical data beyond the default window. Contact [email protected] for help with a custom backfill.
What Fluint Does with Your Gong Data
Ingested call transcripts and participant data feed two main surfaces in Fluint:
Deal context — calls are mapped to the relevant deal workspace using the CRM IDs Gong has linked, or via participant email matching. Once mapped, the full call history is available inside that deal.
AI meeting prep & account summaries — Olli uses the transcripts to generate pre-meeting briefs, executive summaries, follow-up drafts, and answers to questions about your accounts.
Only users within your Fluint workspace can access the ingested calls.
Data Retention
Call metadata and transcripts are retained in Fluint indefinitely unless your account is deleted. There is no automatic expiry policy on Fluint's side.
Recording URLs pulled from Gong are time-limited by Gong (8-hour expiry). After that window, the link will no longer be valid, but the transcript and metadata remain fully accessible in Fluint.
Revoking Access
You can disconnect the Gong integration at any time from Settings → Integrations. Disconnecting stops all future syncs immediately. Previously ingested transcripts and metadata remain in Fluint until explicitly deleted — disconnecting the integration does not automatically remove existing data.
Troubleshooting
Calls aren't appearing in Fluint
Fluint only ingests calls where at least one participant is a recognized Fluint user in your organization. Confirm the participants on those calls have active Fluint accounts.
Check that the Gong integration is still connected under Settings → Integrations. A disconnected or expired OAuth token will stop syncs.
New calls sync on a 2-hour polling interval — give it a couple of hours before following up.
Calls aren't mapping to the right deal
Call-to-deal mapping relies on Gong having your CRM opportunity linked to the call. If Gong doesn't have the CRM association, Fluint falls back to participant email matching — make sure your deal contacts have accurate work emails attached.
If a call still isn't mapped correctly, you can manually assign it to the right deal from within Fluint.
I need calls older than 90 days
The default backfill is 90 days per user, but manual backfill tooling is available. Reach out to [email protected] with the scope of what you need.
The recording link is expired
Gong generates time-limited recording URLs (8-hour expiry). Fluint doesn't re-host recordings, so once the URL expires, you'll need to access the recording directly in Gong. The transcript and all metadata in Fluint remain fully accessible.