Skip to content

Zoom, without opening Zoom.

What is scheduled, who came, and where the recording and summary live.

  • Free to start
  • No card
  • Nothing irreversible without your yes
  • Your own account, not a shared login
Try asking Ray

Ask in your own words.

Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Zoom details, and Ray takes it from there.

  • @Ray send me the summary from the Acme call.

  • @Ray set up a 30 minute call with the Northwind team on Thursday.

  • @Ray who actually joined yesterday's standup?

  • @Ray push the design review out by an hour.

What Ray can and cannot do in Zoom

Reading is free, because reading changes nothing. Everyday changes Ray just makes, and anything that can't be taken back waits for your yes. The rest is not on Ray’s list.

11 reads wired, 1 action Ray does at once, and 3 actions that wait for your yes.

Runs on its own

What Ray reads in Zoom

  • Meetings, past instances, and who attended
  • Recordings and meeting summaries
  • Webinars and their registrants

Reading changes nothing, so Ray never stops to ask whether it may look something up.

Just does it

Ray does these at once

  • Update a meeting

Anything Ray can put back comes with an Undo button on its reply. In a schedule, a watch or a chase that has read outside content with nobody present, these wait for a yes too.

Asks first, every time

Always waits for your yes

  • Schedule a meeting
  • Register someone for a meeting or a webinar

Ray posts a card showing exactly what it is about to do. Nothing happens until someone approves, and no setting turns that off.

Not on the list

Things Ray is never handed

These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.

  • Delete a meeting or its recordings
  • Create or delete a whiteboard
  • Change classification labels
Before it acts

Exactly what Ray will ask you to approve.

Not a category of permission. These are the Zoom actions that stop in the thread with the real content before they happen.

  • Register someone for a Zoom meeting
  • Register someone for a Zoom webinar
  • Schedule a Zoom meeting

Ray does these at once

  • Update Zoom meeting

Everyday work. Anything Ray can put back comes with an Undo button on its reply.

The card Ray posts

Register someone for a Zoom meeting

Showing Email, Comments, Last name, Meeting id, Org and Job title, each carrying the exact content that will land.

ApproveDecline

How Ray works with Zoom

No workflow to build, and nothing to maintain when the work changes.

  1. 01

    Connect Zoom

    One click, right where you asked. Ray posts a connect card, you authorise Zoom with your own account, and the work you asked for picks up where it left off.

  2. 02

    Ask in plain words

    In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.

  3. 03

    It lands, with an Undo

    Reading runs on its own. Everyday changes land at once with an Undo, and anything that sends, spends or can't be taken back waits for your yes with the exact content in front of you.

and the rest

Megan

@Ray the checkout bug is back. Take a look in Zoom, and tell Dana it is being looked at.

Update Zoom meeting

Done
just now
Undo
Works with your stack

Ray uses Zoom together with the rest of your tools.

One ask can read Zoom, cross-reference what is in these, and land the finished result back in the thread. Not four connectors taking turns, one teammate with one memory.

What does connecting Zoom to Ray actually do?

Ray is an AI teammate that works in your team chat, on Slack today. Connect Zoom and it can do the Zoom part of a request without anyone leaving the conversation: read what it needs and make the change, asking first before anything that can’t be taken back.

It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.

Every person on the team connects their own Zoom account, so Ray can only reach what that person can already reach, and the history in Zoom shows who actually asked.

Security and permissions

  • You authorise Zoom on its own login screen. Your password never passes through Ray.
  • What waits for a yes is decided in the execution path, not by a prompt. No setting lets an irreversible action through without one.
  • Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
  • Disconnect Zoom in a message, or uninstall Ray and every connection it held is revoked.

How Ray handles your data

Zoom and Ray, answered

The questions teams ask before they connect Zoom. Every answer is how this integration is built rather than a promise about it.

More calendars & scheduling integrations

Ray uses them together in a single run when a request spans more than one.

Browse every integration

Put Ray to work in Zoom.

Free to start, no credit card, and nothing irreversible happens without your yes.

Add to Slack for free

By adding Ray, you accept the Terms and Privacy Policy.