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 Granola integration ("the Integration") connects your Granola account to Ruby so that meeting notes and transcripts captured by Granola can be used to generate insights inside Ruby. 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:
Meetings captured by Granola appear inside Ruby, linked to account, contact, and deal records
Granola meeting notes and transcripts are pulled into Ruby once they're available in your Granola account
Ruby's AI agents summarize meetings, extract action items, and score deal health
Insights are surfaced in your Ruby workspace
3. Prerequisites
3.1 Granola Requirements
A Granola account in good standing
The Granola desktop app installed and actively recording your meetings — Granola only captures meetings that the desktop app is running for
3.2 Ruby Requirements
An active Ruby account at app.heyruby.io
A Ruby plan that includes the Granola integration
4. Access Requested
The Integration uses Granola's OAuth 2.0 authorization flow. During installation you will be asked to review and approve Ruby's access to your Granola account, covering:
Reading your list of meetings, including title, date, and known participant names and email addresses, so Ruby can identify new meetings to bring in. Meeting metadata is stored in PostgreSQL, encrypted in transit via TLS 1.2+, and retained while the connection is active.
Reading the transcript or notes content of a specific meeting once it has been identified. Transcript text is stored in PostgreSQL, encrypted in transit via TLS 1.2+, and retained while the connection is active.
Ruby requests only the access needed for the features described in this document, and does not use this access to create, modify, or delete anything in your Granola account.
Note on OAuth token storage: Granola OAuth tokens are managed by Ruby's OAuth proxy on Ruby's behalf. Granola 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 Granola
Sign in to Granola and review the permissions, then approve the connection
You will be returned to Ruby with the connection complete
Make sure the Granola desktop app is installed and actively recording your meetings — Ruby can only ingest meetings that Granola itself has captured
6. Initial Configuration
Granola does not currently have a separate settings panel inside Ruby beyond Connect and Disconnect. Granola does not notify Ruby in real time when a new meeting is ready, so new meetings and notes are picked up the next time you run a manual sync (see Section 9).
7. Participant Consent and Host Responsibility
The Ruby Granola integration ingests meeting notes and transcript content captured by your Granola account.
When meeting content is synced:
You confirm that you are the meeting host or have the host's authorization to bring the meeting content into Ruby
You are responsible for obtaining all consents required by applicable law from meeting participants before capturing the meeting with Granola and before processing that content in Ruby. Depending on jurisdiction, this may include all-party or two-party consent for recording or note-taking, 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 meeting 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 — Granola."
8. How the Integration Works
8.1 Data Flow
You authorize the Integration from inside Ruby and complete Granola's consent screen
Granola redirects back to Ruby and the authorization is complete
When you run a manual sync, Ruby asks Granola for your recent meetings and identifies any that haven't yet been ingested
Ruby fetches the transcript or notes content for each new meeting using your authorization
Ruby parses the content and runs AI processing
Insights and meeting records are surfaced in your Ruby workspace
8.2 What Ruby Accesses
Meeting metadata: title and date
Known participant names and email addresses, as recorded by Granola
Granola meeting transcript or notes content
8.3 What Ruby Does Not Currently Access
Audio or video — Granola is a notes/transcript-based tool and Ruby only ever receives text content from it
Meeting duration — Granola does not currently provide this to Ruby, so it isn't shown for Granola-sourced meetings
Speaker-by-speaker breakdown or timestamps within the transcript — Granola content is ingested as consolidated notes rather than a timestamped, speaker-attributed transcript
The ability to create, edit, or delete anything in your Granola account
Meetings the Granola desktop app was not running for
If we expand the Integration to access additional data types in the future, this Documentation page will be updated before any new access begins.
9. Features
9.1 Meeting Timeline
A view of past Granola meetings inside Ruby, linked to deal, account, and contact records.
9.2 AI Meeting Summary
After meeting content is available, Ruby generates a structured summary covering topics discussed, decisions made, objections raised, and action items.
9.3 Deal Intelligence
Meeting outcomes feed Ruby's deal-level agents — MEDDIC scoring, deal health assessment, champion identification, and objection handling — so your pipeline reflects the latest conversation.
9.4 Manual Sync
Granola does not notify Ruby automatically when new content is ready. To bring in your latest meetings, go to Settings → Integrations → Granola and trigger a manual sync. We recommend doing this regularly, or right after a meeting 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 Granola
Confirm
When you disconnect, Ruby revokes the stored authorization and stops calling the Granola API on your behalf.
10.2 From Granola
To fully revoke Ruby's access from Granola's side in addition to disconnecting in Ruby, check your Granola account's connected apps or integrations settings and remove Ruby's access there as well.
11. Data Deletion After Disconnect
When you disconnect the Integration:
Ruby stops ingesting new Granola data immediately
Existing meeting metadata, notes, and AI insights already in Ruby remain associated with your account so historical context is preserved
To delete previously synced Granola data, email support@heyruby.io with the subject "Data Deletion — Granola"; 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 Granola's sign-in pages
12.2 Meetings Are Not Appearing in Ruby
Confirm the Granola desktop app was installed and actively recording during the meeting — Granola only captures meetings it was running for
Run a manual sync from Settings → Integrations → Granola — Granola does not push new content to Ruby automatically
Confirm the meeting appears correctly in Granola itself first
12.3 I Removed the Integration but Ruby Is Still Showing My Granola Data
Disconnecting stops new data from being ingested. To delete existing data, email support@heyruby.io with the subject "Data Deletion — Granola."
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. Meeting metadata and transcript content are stored in a PostgreSQL database on AWS RDS.
14. Frequently Asked Questions
14.1 Does Ruby store my Granola recordings?
Granola itself is a notes and transcript tool rather than a recording tool — it does not produce a Ruby-accessible audio or video file. Ruby only ingests the text content Granola provides. You can request deletion of stored content at any time by emailing support@heyruby.io.
14.2 Does Ruby use my Granola data to train AI models?
Ruby does not use customer-identifiable Granola 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 meetings?
Visibility is controlled by your Ruby workspace settings. By default, meetings are visible to the host and to team members assigned to the related deal.
14.4 Why don't my Granola meetings sync automatically?
Granola does not currently notify Ruby in real time when new content is ready. Use the manual sync option in Settings → Integrations → Granola to pull in recent meetings.
14.5 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 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 Granola integration and does not modify any executed agreement. Use of the Integration is also governed by our Privacy Policy and Granola's Terms of Service.