Fathom integration for Ruby AI
The Ruby AI Fathom integration reads your Fathom recordings along with the summaries and action items Fathom already produced, and attaches the analysis to the right deal.
At a glance
What Ruby AI reads from Fathom | What Ruby AI writes to Fathom |
Meeting title, scheduled start, and recording start and end times | Nothing |
The transcript for each recording, with speaker names inline | Nothing |
Fathom's own AI summaries and action items | Nothing |
Calendar invitees and participants, with email addresses | Nothing |
The underlying Zoom or Meet link | Nothing |
Why connect Fathom to Ruby AI?
Reps keep using Fathom exactly as they do now. Ruby reads what Fathom recorded.
Ruby uses the scheduled start time rather than the recording start time, because reps often hit record before the meeting begins. That keeps calls lined up with the calendar.
The underlying Zoom or Meet link comes through, so Fathom recordings match to the calendar event they belong to.
How does Ruby AI use Fathom?
Ruby lists your recent meetings with summaries and action items included, then fetches the transcript for each recording, using the endpoints in Fathom's public API documentation. Ruby reads the title, the scheduled start, the recording start and end times for duration, the meeting URL, and the attendee list.
Ruby does not download the recording video or audio.
What does Ruby AI put into Fathom?
Nothing. The Fathom integration is read-only. Ruby creates no recordings, edits no summaries, and changes nothing in your Fathom workspace.
How do I connect Fathom to Ruby AI?
In Ruby AI, go to Settings → Integrations → Fathom.
Approve the connection on Fathom's authorization screen.
Run a sync from Ruby. Ruby pulls your recent recordings with their transcripts, summaries and action items.
What can Ruby AI do with Fathom?
Recordings become deal context. On each sync Ruby pulls your recent Fathom meetings, the transcript for each one, and the attendee list. Speaker names stay attached to what they said.
Fathom's own AI output comes with it. Ruby requests summaries and action items alongside the transcript, so what Fathom already generated is stored with the meeting rather than thrown away.
Attendee emails, which matter more than they sound. Fathom returns calendar invitees with email addresses. That lets Ruby match a call to an account by domain even when no calendar event lines up, and it lets Ruby recognize when the same meeting was also captured somewhere else.
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 Fathom?
Read access to your meetings, their transcripts, and the summaries and action items Fathom generated. Ruby cannot create or change anything in Fathom.
Does Ruby AI write anything to Fathom?
No. The integration is entirely read-only.
Does Ruby AI keep Fathom's own summaries?
Yes. Ruby requests summaries and action items alongside the transcript and stores them with the meeting rather than discarding them.
Does Ruby AI download my Fathom recordings?
No. Ruby reads the transcript text and the metadata. The video and audio files are never downloaded.
Why does Ruby AI use the scheduled start time rather than when I hit record?
Reps often start recording several minutes before a meeting begins. Using the scheduled start keeps the call aligned with the calendar event, which is how Ruby matches it to a deal.
Need help connecting Fathom?
View the technical guide: Fathom 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 match each recording to the right deal
Gong if you want per-sentence timings on the same calls
HubSpot and Salesforce, where the analysis lands