Zoom integration for Ruby AI

The Ruby AI Zoom integration is a read-only connection to your cloud recordings. Ruby picks up the transcript automatically, within minutes of the recording finishing, and attaches the analysis to the right deal.

At a glance

Why connect Zoom to Ruby AI?

• No bot joins your calls. Ruby reads the recording Zoom already made.

• Only recording.completed is processed. Every other Zoom event is ignored, so connecting Zoom does not put Ruby in the path of anything else.

• Zoom ranks second only to Gong for transcript quality, so a Zoom call captured by a notetaker as well resolves to the Zoom version.

How does Ruby AI use Zoom?

On a completed recording Ruby reads the meeting record, the recordings list, the audio transcript file, and the past-meeting participant list. Ruby uses Zoom's own short-lived download token to fetch the transcript, so the file never sits behind a permanent link. Zoom's OAuth model is documented in Zoom's developer reference.

Ruby reads the topic as the meeting title, the start time, the duration, and the join URL, which is what links the call to the calendar meeting when Zoom does not supply an event ID.

Ruby does not read chat, Zoom AI Companion summaries, or the video files.

What does Ruby AI put into Zoom?

Nothing to your data. Ruby creates no meetings, posts nothing, and changes no settings in your Zoom account. The only write is the cloud-recording notification Ruby registers at connect.

How do I connect Zoom to Ruby AI?

1. In Ruby AI, go to Settings → Integrations → Zoom.

2. Approve the connection on Zoom's authorization screen.

3. Ruby registers a cloud-recording notification during connect. The first cloud recording you make after that arrives in Ruby on its own.

What can Ruby AI do with Zoom?

Transcripts arrive without anyone fetching them. Zoom notifies Ruby when a cloud recording completes. Ruby downloads the transcript, splits it by speaker, and attaches it to the right meeting.

Ruby waits for the transcript instead of giving up. Zoom finishes the recording before it finishes the transcript. If the transcript is not ready when the notification arrives, Ruby retries at 2 minutes, 5 minutes and 10 minutes rather than filing an empty call.

Participants and recording links come across. Ruby reads the participant list with names and emails where Zoom exposes them, and keeps the recording and playback URLs on the meeting record.

Analysis starts automatically. If the meeting was already linked to a deal on your calendar, the five-agent chain runs as soon as the transcript lands: meeting analysis, stakeholder tracking, MEDDIC scoring, deal health, sales strategy.

Frequently asked questions

What permissions does Ruby AI need in Zoom?

Read access to your meetings, your cloud recordings and your past-meeting participant lists. Ruby cannot start, schedule or modify a meeting, and cannot read chat.

Does a Ruby AI bot join my Zoom calls?

No. Ruby has no meeting bot. Ruby reads the transcript from the cloud recording Zoom already produced, after the call ends.

Does Ruby AI write anything to Zoom?

Nothing to your data. The only write is the cloud-recording notification Ruby subscribes to at connect, so Zoom knows where to send the alert.

What if the transcript is not ready when Zoom notifies Ruby AI?

Ruby retries at 2 minutes, 5 minutes and 10 minutes. Zoom finishes the recording before it finishes the transcript, so this is normal rather than an error.

Which Zoom events does Ruby AI act on?

Only recording.completed. Every other Zoom event is ignored, so connecting Zoom does not put Ruby in the path of anything else in your account.

Need help connecting Zoom?

View the technical guide: Zoom 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

• HubSpot and Salesforce, where the analysis lands