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 Google Calendar integration ("the Integration") connects your Google Calendar to Ruby so that upcoming meetings can be linked to account, contact, and deal records, and used to generate pre-meeting briefs. This page explains how to install, configure, use, and disconnect the Integration.
2. About Ruby
Ruby helps revenue teams turn meeting data into structured insight. Once the Integration is connected:
Upcoming Google Calendar events appear inside Ruby, linked to account, contact, and deal records
Ruby can generate a pre-meeting brief ahead of scheduled meetings
Calendar events help Ruby match meeting transcripts (from other connected sources) to the correct deal or account
Insights are surfaced in your Ruby workspace
3. Prerequisites
3.1 Google Requirements
A Google account in good standing with access to Google Calendar
The Google account you connect must use the same email address as your Ruby account
3.2 Ruby Requirements
An active Ruby account at app.heyruby.io
A Ruby plan that includes the Google Calendar integration
4. OAuth Scopes Requested
The Integration uses Google OAuth 2.0. During installation you will be asked to grant the following scopes:
calendar.readonly Reads events on your primary Google Calendar — including title, time, location, description, organizer, attendees, and any attached video meeting link — so that Ruby can display upcoming meetings and match them to deal and account records. This scope is read-only; Ruby cannot create, modify, or delete events in your calendar. Calendar event data is stored in PostgreSQL, encrypted in transit via TLS 1.2+, and retained while the connection is active.
email, profile, openid Used to confirm your Google account identity during sign-in. Ruby verifies that the Google account you connect uses the same email address as your Ruby account, and will reject the connection if they do not match.
Ruby requests only the minimum scopes needed for the features described in this document.
Note on OAuth token storage: Google OAuth tokens (access token and refresh token) are stored directly by Ruby in an encrypted database table, scoped to your user account.
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 Google Calendar
Sign in to Google and review the permissions, then click "Allow"
Ruby checks that the Google account you used matches your Ruby account email. If they don't match, the connection is rejected and you'll be asked to try again with the correct account
You will be returned to Ruby with the connection complete
6. Initial Configuration
After connecting, Google Calendar has no separate settings panel — Ruby reads your primary calendar automatically. Per-event options are available from the calendar view inside Ruby (see Section 9).
If you also connect a meeting transcript source (such as Zoom, Microsoft Teams, Fireflies, Fathom, Granola, or Gong), Ruby automatically attempts to match incoming transcripts to your calendar events using meeting time and attendee overlap. No separate configuration is needed for this matching.
7. Participant Consent and Host Responsibility
The Integration reads event details — including attendee names and email addresses — for meetings on your primary calendar. Ruby does not modify your calendar or notify attendees in any way.
You are responsible for ensuring that your use of Ruby, including the storage and processing of calendar event details and attendee information, complies with applicable law. Depending on jurisdiction, this may include obligations 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 your use of the Integration is authorized and lawful
If a calendar attendee 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 — Google Calendar."
8. How the Integration Works
8.1 Data Flow
You authorize the Integration from inside Ruby and confirm your Google identity
Google redirects back to Ruby and the authorization is complete
Ruby fetches events from your primary calendar for the coming week
Event details are stored and linked to deal, account, and contact records where a match can be found
When other connected sources deliver a meeting transcript, Ruby attempts to match it to a calendar event by time and attendee overlap
Ruby can generate a pre-meeting brief from matched account and deal context ahead of the scheduled meeting
8.2 What Ruby Accesses
Event metadata: title, start and end time, location, and description
Organizer and attendee names and email addresses
Video meeting links attached to the event (for example, a Google Meet or Zoom link included in the event)
8.3 What Ruby Does Not Currently Access
Any calendar other than your primary calendar
Events further than approximately one week in the future, or any past events outside that window
The ability to create, edit, or delete calendar events — the connection is read-only
Email, Drive, or any other Google Workspace data outside of Calendar
Meetings where every attendee is internal to your organization (these are filtered out and not synced)
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 Calendar View
A view of upcoming meetings inside Ruby, linked to deal, account, and contact records where a match exists.
9.2 Pre-Meeting Brief
Ahead of a scheduled meeting, Ruby can generate a brief summarizing relevant account and deal context, so you walk into the meeting prepared.
9.3 Event Management
You can discard an event you don't want Ruby to track, restore a previously discarded event, or manually trigger a brief for a specific event from the calendar view inside Ruby.
10. Disconnecting the Integration
Google Calendar does not currently have a dedicated "Disconnect" button. If Ruby's stored access to your calendar stops working — for example, if you revoke Ruby's access from your Google Account permissions page — Ruby will stop being able to fetch new calendar events the next time it tries, and your connection will show as not connected in Settings.
To fully revoke Ruby's access to your Google Calendar from Google's side:
Go to myaccount.google.com/permissions
Find "Ruby" (or "Hey Ruby") in the list of connected apps
Click "Remove Access"
If you'd like Ruby to stop syncing your calendar without going through Google, contact support@heyruby.io and we will disable the connection on our end.
11. Data Deletion After Disconnect
When the connection is removed or stops working:
Ruby stops fetching new calendar events
Existing calendar events, deal links, and any briefs already generated remain associated with your account so historical context is preserved
To delete previously synced calendar data, email support@heyruby.io with the subject "Data Deletion — Google Calendar"; we will purge or anonymize the requested data within 30 days
12. Troubleshooting
12.1 Authorization Failed
Confirm you are signing in to Google with the same email address as your Ruby account — Ruby rejects connections from a different Google account
The OAuth flow may have timed out — try connecting again
Confirm that cookies and pop-ups are allowed for accounts.google.com and app.heyruby.io
12.2 Events Are Not Appearing in Ruby
Confirm the event is on your primary Google Calendar — events on secondary or shared calendars are not synced
Confirm the event is within the next week — Ruby only looks ahead about seven days
If every attendee on the event is from your own organization's domain, the event is filtered out by design
12.3 My Connection Shows as Disconnected Even Though I Didn't Remove It
This can happen if your Google account's permission to Ruby was revoked, your password changed, or the stored access expired. Reconnect from Settings → Integrations to restore the connection.
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. Calendar event data, including attendee information, is stored in a PostgreSQL database on AWS RDS.
14. Frequently Asked Questions
14.1 Can Ruby create or edit events on my calendar?
No. The Integration is read-only. Ruby can only read events from your primary calendar — it cannot create, modify, or delete anything in Google Calendar.
14.2 Does Ruby use my calendar data to train AI models?
Ruby does not use customer-identifiable calendar 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 calendar events in Ruby?
Visibility is controlled by your Ruby workspace settings. By default, calendar events are visible to the event owner and to team members assigned to the related deal.
14.4 Why does Ruby require my Google email to match my Ruby email?
This check prevents accidentally connecting the wrong Google account, or connecting a personal account when you intended to connect a work account.
14.5 Does Ruby automatically assign meetings to a deal?
No. Ruby attempts to match meetings to existing account and contact records using calendar data, but assigning a meeting or transcript to a specific deal is a manual step you take inside Ruby.
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 Google Calendar integration and does not modify any executed agreement. Use of the Integration is also governed by our Privacy Policy and Google's API Services User Data Policy.