Granola integration for Ruby AI
The Ruby AI Granola integration reads your Granola meeting notes as deal context, for teams whose record of a meeting is what someone wrote during it rather than a recording.
At a glance
What Ruby AI reads from Granola | What Ruby AI writes to Granola |
Meeting title and date | Nothing |
The transcript or notes for each meeting | Nothing |
Participant list with names and email addresses | Nothing |
Nothing else. Granola supplies no meeting link, duration or per-speaker timestamps | Nothing |
Why connect Granola to Ruby AI?
Not every team records calls. Granola is the path for teams whose record of a meeting is the notes someone took during it.
Notes carry less signal than a full transcript, and Ruby treats them that way. If the same meeting also arrives from a recorder, Ruby keeps the recorder's version.
How does Ruby AI use Granola?
Ruby lists your meetings, filters to those since the last sync, and reads the meeting title, date, participant list and transcript text for each one. Granola is documented at granola.ai.
Granola does not supply a meeting link, a calendar event ID, per-speaker timestamps or a call duration, so Ruby matches Granola meetings to calendar events using attendee emails and time overlap. Connecting a calendar is what makes that reliable.
What does Ruby AI put into Granola?
Nothing. The Granola integration is read-only.
How do I connect Granola to Ruby AI?
In Ruby AI, go to Settings → Integrations → Granola.
Approve the connection on Granola's authorization screen.
Run a sync from Ruby. Ruby pulls your meetings since the last sync with their notes and participant lists.
What can Ruby AI do with Granola?
Granola meetings become Ruby meetings. On each sync Ruby lists your meetings, reads the transcript or notes for each one, and pulls the participant list with names and email addresses.
Attendee emails let Ruby find the deal. Granola supplies participant emails, so Ruby can match a meeting to an account by domain and to a calendar event by attendee overlap.
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 in Granola?
Read access to your meetings, their notes or transcripts, and their participant lists. Ruby cannot create or edit anything in Granola.
Does Ruby AI write anything to Granola?
No. The integration is entirely read-only.
Is Granola as good a source as a call recorder?
No, and Ruby treats it that way. Notes carry less signal than a full transcript. Granola ranks lowest of the seven meeting sources, so if the same meeting also arrives from a recorder, Ruby keeps the recorder's version and discards the duplicate.
How does Ruby AI match a Granola meeting to a deal?
By participant emails and time overlap. Granola supplies no meeting link and no calendar event ID, so a connected calendar is what makes matching reliable.
Does Ruby AI get meeting duration from Granola?
No. Granola does not supply a duration or per-speaker timestamps, so Ruby stores the notes, the title, the date and the participants.
Need help connecting Granola?
View the technical guide: Granola 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 and Outlook Calendar, which make the deal match reliable
HubSpot and Salesforce, where the analysis lands