Google Meet integration for Ruby AI
The Ruby AI Google Meet integration reads Google's own conference transcripts, for teams running Meet without a separate notetaker. Ruby pulls the transcript, the participant list and the meeting link, and attaches the analysis to the right deal.
At a glance
What Ruby AI reads from Google Meet | What Ruby AI writes to Google Meet |
Conference records since the last sync | Nothing |
Transcript entries, formatted with speaker names and timestamps | Nothing |
Participant list, including signed-in, anonymous and dial-in participants | Nothing |
The Meet space URI, normalized to match your calendar event | Nothing |
Why connect Google Meet to Ruby AI?
Nothing new to buy or install. If your org already has Meet transcripts turned on, Ruby reads what is already there.
No bot in the call, no second recording, no change to how reps run meetings.
How does Ruby AI use Google Meet?
On each sync Ruby lists conference records, filters to those since the last sync, and for each one reads the participant list, the transcript metadata, and the transcript entries. The endpoints Ruby uses are documented in Google's Meet API overview.
Google Meet does not expose attendee email addresses through this API, so Ruby relies on the meeting link to match the call to a calendar event and a deal. Connecting Google Calendar is what makes that reliable.
Ruby does not read recordings or Gemini meeting notes.
What does Ruby AI put into Google Meet?
Nothing. The Google Meet integration is read-only.
How do I connect Google Meet to Ruby AI?
In Ruby AI, go to Settings → Integrations → Google Meet.
Approve the connection on Google's authorization screen.
Connect Google Calendar alongside it. Meet supplies no meeting title and no attendee emails, so the calendar is what gives transcripts a title and matches them to a deal.
What can Ruby AI do with Google Meet?
Meet transcripts become deal context. Ruby pulls the conference record, the participant list and the transcript entries, formatted with speaker names and timestamps, and attaches them to the meeting.
Ruby only imports finished transcripts. Google generates the transcript after the call ends. Ruby checks the transcript state and skips anything not yet generated rather than storing an empty record and calling it a meeting.
Meeting titles come from your calendar. The Meet API does not return a meeting title. Ruby recovers it by matching the Meet link against your connected calendar, which is one of several reasons Meet works best with Google Calendar connected.
Analysis starts automatically when the meeting is already linked to a deal on your calendar: meeting analysis, stakeholder tracking, MEDDIC scoring, deal health, sales strategy.
Frequently asked questions
What permissions does Ruby AI need for Google Meet?
Read access to your conference records, participants and transcripts. Ruby cannot start, schedule or modify a Meet call.
Does Ruby AI write anything to Google Meet?
No. The integration is entirely read-only.
Why do I need Google Calendar connected as well?
The Meet API returns no meeting title and no attendee emails. Ruby recovers the title and matches the call to the right deal using the Meet link on your calendar event. Without a calendar, matching falls back to time overlap alone.
Does Ruby AI read my Meet recordings or Gemini notes?
No. Ruby reads the text transcript, the participant list and the meeting link. Recordings and Gemini-generated notes are not requested.
What if a Meet call has no transcript?
Ruby skips it. Google reports whether a transcript file was generated, and Ruby stores nothing rather than filing an empty meeting.
Need help connecting Google Meet?
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 supplies the meeting title and the deal match
Gong if you want higher-fidelity transcripts on the same calls
HubSpot and Salesforce, where the analysis lands