Gong records and transcribes your customer conversations. Connecting Gong to Databook brings what was actually said on a call into an account's intelligence, alongside your CRM data, third-party data and Databook's own insights.
What it can do
Brings real conversation content into account intelligence: material points from a call, such as deal status, stated requirements, stakeholders, competitive mentions, risks and next steps, are extracted and added to the account timeline.
Requires no manual capture: you do not need to log anything from a call yourself. Attribution runs through the Salesforce records Gong already attaches to the call.
Links calls to the right account without depending on a calendar entry: because linkage runs through Salesforce, a call reaches the timeline even when there is no matching calendar invite.
Feeds Databook's AI layer: timeline events from Gong are queryable, so Databook agents can ground answers in recent conversation activity rather than static data alone.
The Gong integration is designed to support Databook's context graph and GTM Decision System.
How it works
Databook receives new Gong calls and their transcripts as they become available, through Ampersand, the integration platform Databook uses to connect to Gong.
Each call is matched to a Salesforce account, contact or lead, and internal participants are matched to Databook users.
Calls that are private, internal-only, or not linked to a Salesforce record are filtered out (see below).
Material business events are extracted from the remaining calls and attached to the account's timeline.
Where Gong data shows up
Account timelines: events derived from Gong appear on the account timeline tagged with Gong as their source, so you can tell them apart from events sourced from other connected systems.
Databook AI: timeline events are queryable by account, event type and date range, so Databook's AI agents can ground answers in recent conversation activity.
Your own data catalog: the structured Gong tables, including calls, participants and transcripts, sit in your own isolated data catalog. Your Gong data is never pooled with any other customer's data.
What Databook takes in
Access to Gong is read only. Databook does not write, edit or delete anything in Gong.
Data | What it contains |
Calls | Title, start time, duration, direction, and interaction metrics such as talk ratio |
Transcripts | Sentence-level transcript text with speaker attribution and topic |
Participants | Everyone on the call, with their internal, external or unknown affiliation |
Gong users | Name, email, title, manager and active status for your Gong seat holders |
CRM context | The Salesforce records Gong attached to the call, at both call and participant level |
Trackers | Keyword and smart tracker hits recorded on the call |
What's excluded
Not every Gong call reaches Databook. A call has to pass all three of the following checks:
Check | What it excludes |
Not private | Any call you have flagged as private in Gong, and any call Gong scopes as internal |
Not internal-only | Calls where every participant is internal to your company. A call needs at least one internal and one external participant |
Linked to Salesforce | Calls with no attached Salesforce lead, contact, account or opportunity |
Expect the number of calls that reach Databook to be noticeably lower than your total Gong call volume. That is by design, not a sign of missing data: internal standups, one-to-ones and calls with no CRM record all drop out.
What to expect
Gong data is not real time. A call typically finishes processing in Gong within a few hours of ending, and its transcript can take up to 24 hours to become available. In practice, expect a call to surface in Databook the following day rather than shortly after the call ends.
See Connecting Gong to Databook for the full timing breakdown.
Limitations worth knowing
One way and read only. Nothing is written back into Gong.
Both parts of setup matter. Installing the integration in the admin console is not enough on its own. Databook also needs an automation rule configured in Gong; without it, Databook is never told a call exists.
New calls only, by default. The connection covers calls created after setup. Loading historical calls is a separate request, handled with your Databook contact rather than something that happens automatically.
Salesforce is currently the supported CRM for linkage. If you use a different CRM, check with your Databook contact before relying on this integration.
Leave Gong's own filters unfiltered. If you narrow the automation rule in Gong, Databook never sees the excluded calls at all, which makes gaps harder to diagnose later.
Transcript quality depends on Gong. Poor audio or heavy cross-talk on a call will reduce the quality of what Databook can extract from it.
Frequently asked questions
Question | Answer |
Can Databook see our private calls? | No. Calls flagged private in Gong are excluded and never reach the timeline. |
Can Databook see our internal meetings? | No. A call needs at least one internal and one external participant to be eligible. |
Does Databook store our full transcripts? | Yes. Transcripts are stored in your own isolated data catalog and used to extract timeline events. |
Will Databook change anything in Gong? | No. Access is read only. |
Why is a call missing from the timeline? | Usually one of three reasons: it was private, it had no external participant, or Gong did not attach a Salesforce record to it. |
How quickly do calls appear? | Typically the following day. Gong's own processing is the main source of delay. |
Getting access
To connect Gong to Databook, you will need a Gong account with API access and Salesforce connected to Gong. See Connecting Gong to Databook for the full setup steps, or contact your Databook account team to get started.