Gong integration for Ruby AI
Gong is the highest-fidelity meeting source Ruby AI supports. Ruby reads your Gong calls, pulls the full transcript, and attaches the analysis to the right deal. When the same call is captured by Gong and by anything else, Ruby keeps the Gong version and discards the duplicate.
At a glance
What Ruby AI reads from Gong | What Ruby AI writes to Gong |
Call title, start time, duration and meeting URL | Nothing |
Full transcript, sentence by sentence, with resolved speaker names and start and end times in seconds | Nothing |
Party list with names, emails and Gong's Internal or External affiliation | Nothing |
The native calendar event ID for the call | Nothing |
Why connect Gong to Ruby AI?
Reps who already record everything in Gong get Ruby analysis with zero change to how they run calls.
Attendee emails come through, so Ruby can match a call to an account by domain even when the calendar event is missing.
Duplicate calls are resolved automatically. A meeting captured by Gong and by a notetaker produces one record, not two.
How does Ruby AI use Gong?
Ruby requests three read scopes: api:calls:read:basic, api:calls:read:transcript and api:calls:read:extensive, documented in Gong's public API documentation. On each sync Ruby lists calls since the last sync, with a 24 hour safety lookback, then pulls the party list and the transcript for each one.
Ruby does not read Gong scores, trackers, topics, talk ratios or Gong's own call summaries.
What does Ruby AI put into Gong?
Nothing. The Gong integration is read-only. Ruby creates no calls, posts no notes, and modifies no records in Gong.
How do I connect Gong to Ruby AI?
In Ruby AI, go to Settings → Integrations → Gong.
Approve the three read scopes on Gong's authorization screen: basic call data, transcripts, and extensive call data.
Run a sync from Ruby. Ruby pulls every call since the last sync, with a 24 hour lookback, and starts analyzing the ones already linked to a deal.
What can Ruby AI do with Gong?
Full diarized transcripts with real timestamps. Ruby pulls every sentence with the speaker attached and start and end times in seconds. The analysis agents can tell who said what and when, not just what was said.
Internal and external speakers, labeled by Gong. Gong tags each party as Internal or External. Ruby uses that directly, so the buyer side of the conversation is identified without guessing from email domains.
Perfect meeting matching. Gong is the only source that hands Ruby the native calendar event ID. That gives a 100% confidence match between the call and the calendar meeting, which means the call attaches to the right deal without a rep assigning it.
Analysis starts automatically. If the meeting was already linked to a deal on your calendar, Ruby runs the full chain the moment the transcript lands: meeting analysis, stakeholder tracking, MEDDIC scoring, deal health, and sales strategy. The result appears on the deal and, if a CRM is connected, on the CRM record.
Frequently asked questions
What permissions does Ruby AI need in Gong?
Three read scopes: api:calls:read:basic, api:calls:read:transcript and api:calls:read:extensive. All three are read-only. Ruby cannot create, edit or delete anything in Gong.
Does Ruby AI write anything to Gong?
No. The Gong integration is entirely read-only. Ruby creates no calls, posts no notes and modifies no records.
Does Ruby AI read my Gong scores and trackers?
No. Ruby reads only the call metadata, the party list and the transcript. Gong scores, trackers, topics, talk ratios and Gong's own summaries are not requested.
What happens if the same call is also recorded by another tool?
Ruby keeps one record, not two. Gong ranks highest of the seven meeting sources, so the Gong version survives and the duplicate is discarded, regardless of which arrived first.
How quickly does a Gong call reach Ruby AI?
Gong does not send webhooks, so calls arrive on sync rather than instantly. Each sync pulls everything since the last one, with a 24 hour safety lookback so nothing is missed.
Need help connecting Gong?
View the technical guide: Gong Integration
Open Learn Hub in the Ruby AI app for a step-by-step walkthrough, or use the support widget in the bottom-right corner of the app. You can also email the team at support@heyruby.io.
Related integrations
Google Calendar, which matches each Gong call to the right meeting and deal
HubSpot and Salesforce, where the analysis of those calls lands