Ruby AI Integrations
Ruby AI is an AI sales assistant that connects to the tools your team already runs on: your calendar, your meeting recorder, and your CRM. Connect them once and Ruby reads what happened, analyzes it, and writes the result back where your reps already work.
Twelve integrations, grouped by what they do.
What can Ruby AI connect to?
CRM
The system of record. Ruby reads deals, companies, contacts and activity out of it, then writes deal intelligence back into it so reps never have to open a second tab to see what Ruby found.
Integration | What connecting it does |
Import companies, deals, contacts and full activity history. Ruby writes four insight fields, per-meeting analysis notes, pre-meeting briefs, and stakeholder contacts with buying-role labels back onto the deal. | |
Import Accounts, Opportunities, Contacts and activity. Ruby writes four insight fields and a meeting summary note onto the Opportunity. |
Calendar and email
The join key. Calendar is what lets Ruby know a transcript belongs to a specific meeting, which belongs to a specific deal, before anyone assigns it by hand. It is also what triggers pre-meeting briefs.
Integration | What connecting it does |
Ruby reads the next 7 days, skips internal-only meetings, and prepares a brief for every external meeting up to 24 hours ahead. Optionally creates the account for a company you have never met before. | |
Same reading and same matching for Microsoft 365 teams. Outlook's join URL is what links a Teams recording to its meeting. |
Video conferencing
Where the conversation happens. Ruby pulls the transcript, runs a five-agent analysis chain on it, and attaches the result to the right deal. Every one of these is read-only for your data: Ruby never posts, edits or deletes a recording, transcript or note in your tool. The only writes are the notification subscriptions Ruby sets up for itself at connect.
Integration | What connecting it does |
Cloud recording transcripts arrive by webhook within minutes of the recording finishing, with participant list and recording links. | |
Transcripts arrive the moment Teams finishes generating them, matched to the meeting by the Outlook join link. | |
Conference transcripts with speaker labels, pulled on sync. |
Conversation intelligence
Integration | What connecting it does |
Highest-fidelity source. Full transcript with speaker names and per-sentence timings, internal and external party labels, and the calendar event ID that matches a call to a meeting exactly. | |
Recordings with attendee emails, plus Fathom's own AI summaries and action items. | |
Transcripts with speakers, timings and attendee emails. Connects with an API key, no OAuth redirect. | |
Note-style meeting records with participant names and emails, for teams that run on Granola rather than a recorder. |
Documents
Integration | What connecting it does |
Import a deck, PDF or doc into org knowledge, deal context, or as a transcript. Export any Ruby document back to Drive. |
Frequently asked questions
What is the minimum set of integrations Ruby AI needs?
One calendar and one meeting source. That is enough to get value on day one: Ruby briefs you before the meeting and analyzes it after. Add a CRM when you want the analysis to land where your pipeline reviews happen.
Does Ruby AI write to every tool it connects to?
No. Only HubSpot and Salesforce receive written content. Every meeting tool and both calendars are read-only for your data. Google Drive receives only files you explicitly asked Ruby to save or export.
Does a bot join my calls?
No. Ruby has no meeting bot and never joins a call. Ruby reads the transcript your recorder already produced, after the meeting ends.
How do I connect an integration?
In Ruby AI, go to Settings → Integrations.
Find the tool and approve the permissions on the vendor's own screen. Eleven of the twelve use OAuth, so Ruby never sees a password. Fireflies uses an API key you paste in.
Run a sync, or wait for the first webhook. Ruby starts reading from that point forward.
Ruby asks for the narrowest permission that does the job. Both calendars are read-only. Google Drive uses the file-picker scope, so Ruby can only touch files you explicitly select. No integration lets Ruby delete anything.
How do I disconnect an integration?
One click in Settings → Integrations. That deletes Ruby's stored token immediately. Salesforce is additionally revoked at Salesforce, and the Microsoft Teams notification subscription is deleted at Microsoft.
Can each rep connect their own account, or does an admin do it once?
Both patterns exist. HubSpot is an org-level install by an admin, and every rep inherits it with their own record visibility. Salesforce, both calendars and Google Drive are per-user. Every rep connects their own.
Need help connecting a tool?
Open Learn Hub in the Ruby AI app for step-by-step walkthroughs of each integration, or use the support widget in the bottom-right corner of the app. You can also email the team at support@heyruby.io.