Zoom
Read meetings, participants, recordings, transcripts and AI summaries, create meetings and send Team Chat messages.
A Zoom connection gives a playbook's functions fifteen operations of the Zoom API, from a document Auto ships of Zoom's Users, Meetings and Team Chat APIs for a user-managed app. You sign in to Zoom and allow Auto, and the connection acts as you: it reaches your own meetings, recordings and Team Chat alone, a meeting it creates is yours, and a message it sends is from you.
On Auto Cloud, available once Zoom's review of Auto completes; on a self-hosted runtime, with your own Zoom app, now.
What a playbook can do with Zoom
- Read who you are, your upcoming meetings and a meeting's details.
- Read a past meeting's details and its participants.
- List your cloud recordings and read a recording's details, a meeting's transcript details and its AI summary.
- List your Team Chat channels, read a channel's messages and a thread.
- Create and update a meeting, and send a Team Chat message.
A recording's or a transcript's file is not fetched: the operations answer what Zoom says about them, and the connection never receives a download token. Nothing is deleted.
The tools, as the connection lists them
Tools that read: user, meetings, meeting, pastMeetingDetails, pastMeetingParticipants, recordingsList, recordingGet, GetMeetingTranscript, Getameetingsummary, getChannels, getChatMessages and retrieveThread.
Tools that act: meetingCreate, meetingUpdate and sendaChatMessage.
An example workflow
Follow-ups after every customer call. A schedule trigger runs the workflow each evening. A lookup function lists the day's past meetings and, for each with a recording, reads its AI summary and transcript details. A reasoning function reads the summary with the account team's follow-up rules in its prompt and drafts, for each meeting, the actions promised, who owns them and the date mentioned. An interaction function sends the draft to the meeting's host in a Team Chat message and waits for a reply in that chat until the next morning, reading the channel's messages: "ok" records the actions, an edit replaces them. A last interaction function creates the follow-up meeting Zoom was asked for, with meetingCreate, where the host confirmed one. Every summary, draft and reply is in the run's history in Studio, where the account team reads them.
How to connect Zoom
- Sign in to Zoom and allow access to your meetings, recordings and Team Chat. Zoom shows on its consent screen what the connection may do.
Then:
- Ask your agent to connect Zoom to Auto, or open Settings, Agents, Connections in Auto Studio and choose Zoom. On Auto Cloud, Studio lists Zoom once Zoom's review of Auto completes.
- On the Studio page, check the service and its access, choose which playbooks may use the connection, and approve it.
- Have your agent check one small read through the connection before a function depends on it.
Step by step: Connect Zoom.
What it needs
- A Zoom account at
zoom.us; a Zoom for Government account is not served. - Cloud recordings, transcripts and AI summaries exist only where your Zoom plan and settings produce them; the guide's What your Zoom plan needs says which.
- A Zoom account whose admin restricts apps may need the admin to allow Auto once; see What your Zoom admin may have to allow.
- Your agent connected to Auto and signed in as you, with permission to change your organization, if your agent adds the connection. An agent connected with an API key cannot add one.
- On a self-hosted runtime, a user-managed Zoom app of your own, registered as the runtime's client, as Let people add connections sets out.
Zoom grants the scopes added to its app rather than scopes the request names, so the consent screen in Zoom lists them. They are the user-level scopes the fifteen operations need: your profile, your meetings, your recordings and their transcripts and summaries, and your Team Chat channels and messages; none that asks an administrator. The guide's What Auto does with each permission explains each one.
Permissions Auto asks for
No scopes are named: Zoom grants what you allow on its consent screen.
Good to know
A recording's and a transcript's files are never fetched; the operations answer their details, and the AI summary is what a function reads of a meeting's content. What a function reads, a summary or a chat, is kept in the run's history, where people with access to the playbook can read it. Removing the Auto app at Zoom removes the connection in Auto as well.