1. Introduction
Ruby (a product of 17404531 Canada Inc, a Canadian Corporation) ("we," "us," or "our") provides an AI-powered sales intelligence platform. The Ruby Gong integration ("the Integration") connects your Gong account to Ruby so that call metadata and Gong-generated text transcripts can be used to generate insights inside Ruby. The Integration does not download, store, or process audio or video files from your Gong recordings. This page explains how to install, configure, use, and remove the Integration.
2. About Ruby
Ruby helps revenue teams turn meeting data into structured insight. Once the Integration is connected:
Calls recorded by Gong appear inside Ruby, linked to account, contact, and deal records
Gong-generated text transcripts are pulled into Ruby once they're ready in your Gong account
Ruby's AI agents summarize calls, extract action items, and score deal health
Insights are surfaced in your Ruby workspace
3. Prerequisites
3.1 Gong Requirements
A Gong account in good standing
Call recording enabled in your Gong workspace settings — Ruby can only retrieve calls that Gong itself has recorded and processed
3.2 Ruby Requirements
An active Ruby account at app.heyruby.io
A Ruby plan that includes the Gong integration
4. OAuth Scopes Requested
The Integration uses Gong's OAuth 2.0 authorization flow. During installation you will be asked to grant the following scopes:
api:calls:read:basic Reads basic call metadata — call ID, start time, duration, and title — so Ruby can identify which calls to bring in. Call metadata is stored in PostgreSQL, encrypted in transit via TLS 1.2+, and retained while the connection is active.
api:calls:read:extensive Reads extended call details, including call participants (name, email address, and whether each participant is internal or external to your organization), so Ruby can attribute transcript segments to the correct speakers and link participants to deal records. Participant data is stored in PostgreSQL, encrypted in transit via TLS 1.2+, and retained while the connection is active.
api:calls:read:transcript Reads the text transcript of a call, broken down by speaker and timing. Audio and video files are never downloaded or stored — only the transcript text. Transcript text is stored in PostgreSQL, encrypted in transit via TLS 1.2+, and retained while the connection is active.
Ruby requests only the minimum scopes needed for the features described in this document, and these scopes are read-only — Ruby cannot create, modify, or delete anything in your Gong account.
Note on OAuth token storage: Gong OAuth tokens are managed by Ruby's OAuth proxy on Ruby's behalf. Gong OAuth tokens are not stored directly by Ruby.
5. Installing the Integration
5.1 From Inside Ruby
Sign in at app.heyruby.io
Open Settings and select the Integrations section
Click "Connect" next to Gong
Sign in to Gong and review the permissions, then approve the connection
You will be returned to Ruby with the connection complete
6. Initial Configuration
Gong does not currently have a separate settings panel inside Ruby beyond Connect and Disconnect. Gong does not notify Ruby in real time when a new call is ready, so new calls are picked up the next time you run a manual sync (see Section 9).
7. Participant Consent and Host Responsibility
The Ruby Gong integration ingests the text transcripts of calls recorded in your Gong account. Ruby does not download, store, or process audio or video files from Gong.
When a call transcript is synced:
You confirm that you are the call owner or have the owner's authorization to bring the transcript into Ruby
You are responsible for obtaining all consents required by applicable law from call participants before recording the call with Gong and before processing the transcript in Ruby. Depending on jurisdiction, this may include all-party or two-party consent for recording, and consents required under Canada's PIPEDA, Quebec Law 25, the EU General Data Protection Regulation, the California Consumer Privacy Act, and other applicable laws
Ruby relies on your representation that you have obtained these consents. Ruby does not independently verify participant consent and is not responsible for any failure to obtain it
If a call participant requests that their information be removed from Ruby, you can request deletion at any time by emailing support@heyruby.io with the subject "Data Deletion — Gong."
8. How the Integration Works
8.1 Data Flow
You authorize the Integration from inside Ruby and complete Gong's consent screen
Gong redirects back to Ruby and the authorization is complete
When you run a manual sync, Ruby asks Gong for your recent calls and identifies any that haven't yet been ingested
Ruby fetches call details, participants, and the transcript for each new call using your authorization
Ruby parses the transcript into speaker-attributed segments and runs AI processing
Insights and meeting records are surfaced in your Ruby workspace
8.2 What Ruby Accesses
Call metadata: call ID, title, start time, and duration
Participant names, email addresses, and internal/external classification
Gong-generated text transcripts, including speaker attribution and timing
8.3 What Ruby Does Not Currently Access
Audio or video files from your Gong recordings — only the text transcript is downloaded
The ability to create, edit, or delete anything in your Gong account
Gong CRM data, email integrations, or user/team administration settings
Calls or transcripts from Gong workspaces you have not connected
If we expand the Integration to access additional data types in the future, this Documentation page and the OAuth scopes presented during installation will be updated before any new access begins.
9. Features
9.1 Meeting Timeline
A view of past Gong calls inside Ruby, linked to deal, account, and contact records.
9.2 AI Meeting Summary
After a transcript is available, Ruby generates a structured summary covering topics discussed, decisions made, objections raised, and action items.
9.3 Deal Intelligence
Call outcomes feed Ruby's deal-level agents — MEDDIC scoring, deal health assessment, champion identification, and objection handling — so your pipeline reflects the latest conversation. Where a call is also captured by another connected source, Ruby uses the Gong version as the primary record, since Gong calls include full participant and speaker detail.
9.4 Manual Sync
Gong does not notify Ruby automatically when new calls are ready. To bring in your latest calls, go to Settings → Integrations → Gong and trigger a manual sync. We recommend doing this regularly, or right after a call you want reflected in Ruby.
10. Disconnecting the Integration
10.1 From Inside Ruby
Sign in at app.heyruby.io
Open Settings and select the Integrations section
Click "Disconnect" next to Gong
Confirm
When you disconnect, Ruby revokes the stored authorization and stops calling the Gong API on your behalf.
10.2 From Gong
To fully revoke Ruby's access from Gong's side in addition to disconnecting in Ruby, check your Gong admin settings for connected apps or API access and remove Ruby's access there as well.
11. Data Deletion After Disconnect
When you disconnect the Integration:
Ruby stops ingesting new Gong data immediately
Existing call metadata, transcripts, and AI insights already in Ruby remain associated with your account so historical context is preserved
To delete previously synced Gong data, email support@heyruby.io with the subject "Data Deletion — Gong"; we will purge or anonymize the requested data within 30 days
12. Troubleshooting
12.1 Authorization Failed
The OAuth flow may have timed out — try connecting again
Confirm that cookies and pop-ups are allowed for app.heyruby.io and Gong's sign-in pages
Confirm your Gong plan and role include API access — some Gong roles or plans restrict this
12.2 Calls Are Not Appearing in Ruby
Confirm call recording is enabled in your Gong workspace settings
Confirm the call has finished processing in Gong itself — check your Gong dashboard
Run a manual sync from Settings → Integrations → Gong — Gong does not push new content to Ruby automatically
12.3 I Removed the Integration but Ruby Is Still Showing My Gong Data
Disconnecting stops new data from being ingested. To delete existing data, email support@heyruby.io with the subject "Data Deletion — Gong."
13. Security and Privacy
For details on how Ruby handles your data, see our Privacy Policy at heyruby.io/privacy.
All data is transmitted using TLS 1.2 or higher. Call metadata, participant information, and transcript text are stored in a PostgreSQL database on AWS RDS.
14. Frequently Asked Questions
14.1 Does Ruby store my Gong recordings?
No. Ruby does not download or store Gong audio or video files. Ruby ingests only the Gong-generated text transcript of calls, along with call metadata and participant details. You can request deletion of stored transcripts at any time by emailing support@heyruby.io.
14.2 Does Ruby use my Gong data to train AI models?
Ruby does not use customer-identifiable Gong data to train shared models that benefit other customers. AI insights generated from your data are for your account only.
14.3 Can my teammates see my calls?
Visibility is controlled by your Ruby workspace settings. By default, calls are visible to the call owner and to team members assigned to the related deal.
14.4 Why don't my Gong calls sync automatically?
Gong does not currently notify Ruby in real time when new calls are ready. Use the manual sync option in Settings → Integrations → Gong to pull in recent calls.
14.5 If a call is captured by both Gong and another tool, which version does Ruby use?
Ruby uses the Gong version as the primary record when the same call is detected from multiple connected sources, since Gong calls include full participant and speaker detail.
14.6 In which regions is Ruby available?
Ruby is currently available to users in North America (United States and Canada). International users may use Ruby subject to applicable laws and regulations in their jurisdiction.
15. Versioning and Changelog
Material changes to scopes, features, or data handling practices are reflected by updating the Effective Date above and revising this page before the changes take effect.
16. Contact Us
17404531 Canada Inc. support@heyruby.io A Canadian Corporation
Disclaimer
This Documentation page describes how to use the Ruby Gong integration and does not modify any executed agreement. Use of the Integration is also governed by our Privacy Policy and Gong's Terms of Service.