Resources · Make integration

Zoom Make integrationAutomate Zoom with Make.

Your Zoom account can handle the dull half of your meetings on its own. The Zoom Make integration brings 30 modules, 5 of them instant triggers, to open meetings, register attendees, fetch recordings and post chat messages. No code anywhere, and a first scenario you build here.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does a Zoom Make integration actually automate?

Make is a visual automation tool where you assemble a scenario, a chain of steps that runs without you. Each step is a module: one Zoom action, one trigger, one search. Zoom brings 30 of them, so Make can open a meeting, sign someone up for a webinar, go and get a recording or drop a message in a channel while your attention is elsewhere.

Recordings that file themselves. Watch recordings catches the event, Download a cloud recording pulls the file into the scenario, and the module after it puts the video where your team actually looks for it.

Attendee lists that stay current. Add a webinar registrant turns a form fill into a real seat, List webinar registrants reads the session back out, and your CRM stops living on exports.

Rooms that appear on their own. Create a meeting opens the call from whatever event deserves one, Send a chat message tells the channel it exists, and nobody copies a link by hand again.

What Make will not do here: the 30 modules stop at meetings, webinars, registrants, panelists, recordings and chat. Anything past that line goes through Make an API call, which reaches any part of the Zoom API with the same connection. Zoom also exists as an n8n node, so if the tool itself is still an open question, the n8n vs Make comparison and the Zoom n8n integration page are the two pages to read next. To learn the editor properly rather than by trial, there is Make training.

Connect

How do you connect Zoom to Make?

  1. 01

    Add a Zoom module and open the connection window

    Drop any Zoom module into your scenario and click Create a connection. A connection is your Zoom account linked to Make once, then reused by every Zoom module. If the module carries the instant tag, Make wants a webhook first, the call Zoom sends when something happens: click Create a webhook, then Create a connection.

  2. 02

    Collect your credentials in the Zoom App Marketplace

    Zoom will not talk to Make without a registered app of your own. Log in to the Zoom App Marketplace, click Manage, open Created Apps and select your OAuth app. If Zoom asks for a callback URI, the one to paste is https://www.integromat.com/oauth/cb/zoom-user.

  3. 03

    Paste the credentials and finish the authorization

    Copy the Client ID and the Client secret shown on your screen, paste them into Make, then follow whatever the authorization window asks for. The optional Connection name field only matters once a second Zoom account joins the mix, and the connection then serves every Zoom module in every scenario.

First scenario

Your first scenario: back up a Zoom recording

GoalWhen a recording event happens in Zoom, Make pulls the file and hands it to the app that keeps it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to place the first module. Search Zoom by name, then pick Watch recordings.

  2. 02

    Connect your Zoom account

    This module has the instant tag, so Make asks for a webhook before anything else. Click Create a webhook, then Create a connection, and authorize with the credentials from your Zoom app.

  3. 03

    Add the download step

    Click the + to the right of the trigger and add Download a cloud recording. Map the values it needs from the bundle the trigger sent, a bundle being one item passing from one module to the next.

  4. 04

    Test with Run once

    Run once executes the scenario a single time, for testing. Click it, then make a recording event happen in Zoom. Each module shows the bundle it received, which is where you confirm the file really came through.

  5. 05

    Switch the scenario on

    Save, then flip the scenario on. The trigger is instant, so there is no interval to choose: Make waits for Zoom to call it and the chain runs at the next recording event.

Triggers

What starts a Zoom scenario?

5 modules start a scenario when something happens in Zoom. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Zoom as soon as it happens.

Zoom1Watch chat channels

Watch chat channels

Instant trigger

In MakeTriggers when your activity in a channel occurs.

Watch chat channels keeps an eye on what happens to the Zoom chat channels you take part in, and hands that activity straight to the rest of your scenario.

How it fires
instant. Zoom calls Make through a webhook as soon as it happens, so nothing is polled and there is no interval to choose.
When to use it
a support team that wants every channel it joins logged in a shared tracker, without anyone remembering to do it.
Watch out
it reports what happens to a channel, not what people write inside one. For message content, Watch chat messages is the trigger you want.
Zoom2Watch chat messages

Watch chat messages

Instant trigger

In MakeTriggers when a chat message is sent, updated, replied or deleted in your channel.

Every message sent, edited, answered or deleted in your channel wakes this trigger up and starts the scenario with that message in hand.

How it fires
instant. The webhook is Zoom's side of the deal: it calls Make the second the message moves, with no schedule involved.
When to use it
an agency that mirrors client messages from a Zoom channel into its project tool, so the conversation does not live in two places.
Watch out
four kinds of event share one trigger. Filter on the one you actually care about, otherwise a corrected typo restarts the whole chain.
Zoom3Watch meetings

Watch meetings

Instant trigger

In MakeTriggers when an event occurs in your meeting.

This one listens to the life of a meeting and fires when an event occurs in it, which is the usual way to hang a scenario off a call without ever opening Zoom again.

How it fires
instant. Zoom pushes the event to Make through a webhook at the moment it occurs.
When to use it
a sales team that wants a follow-up task created the moment a discovery call is over.
Watch out
a meeting produces more than one kind of event, so check which one arrived before acting on it. A scenario meant for the end of a call will otherwise run at its start too.
Zoom4Watch recordings

Watch recordings

Instant trigger

In MakeTriggers when a recording event occurs in your meeting.

Recording events from your meetings land here, and that is the starting line for anything that files, converts or shares a Zoom recording.

How it fires
instant. Zoom rings Make through a webhook as soon as the recording event happens, so the file gets handled while the room is still warm.
When to use it
a training company that copies each session into its own storage, instead of hoping somebody downloads it later.
Watch out
the trigger tells you an event happened, it does not hand over the media. Getting the file is a separate step, and that step is Download a cloud recording.
Zoom5Watch webinars

Watch webinars

Instant trigger

In MakeTriggers when an event occurs in your webinar.

Nothing moves in a webinar without this trigger knowing: the session's events reach Make and the scenario picks up from there.

How it fires
instant. The app warns Make through a webhook as soon as it happens, so there is no interval to configure anywhere.
When to use it
a media team that runs webinars and wants its CRM updated the minute a session changes.
Watch out
it covers webinars, not calls. A session created with Create a meeting will never wake this trigger, and Watch meetings is the one that does that job.
Modules

Every Zoom action and search, one by one

Zoom gives you 25 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Zoom1

Add a meeting registrant

Action

In MakeRegisters a participant for a meeting.

Signs one person up for a meeting that already exists, so the seat is booked without anyone retyping a name in Zoom.

When to use it
a workshop sold from your site, where each order should become a registered attendee before the session opens.
Watch out
one bundle registers one person. A list coming out of a search means one operation per name, and operations are what Make counts on your plan.
Zoom2

Add a webinar registrant

Action

In MakeRegisters a participant for a webinar.

Turns a signup into a real webinar registrant, which is what you need when the form lives on your landing page and the session lives in Zoom.

When to use it
a product launch where every form fill reaches the session directly, with no export to shuffle around afterwards.
Watch out
a registrant is not a panelist. Speakers go through Add webinar panelists, and the two lists are not interchangeable in Zoom.
Zoom3

Add webinar panelists

Action

In MakeRegisters multiple panelists for a webinar.

Registers several speakers for a webinar in one call, which is the real difference with the registrant modules: this one thinks in groups.

When to use it
a round table whose guests already sit in a spreadsheet and should land in the session as panelists.
Watch out
adding a panel in bulk is easy, taking it apart is not. Remove a webinar panelist works one speaker at a time.
Zoom4

Create a meeting

Action

In MakeCreates a meeting for a user.

Opens a new meeting for a Zoom user, so the call exists before anyone thinks about creating it.

When to use it
a booking that arrives in your calendar and should carry its own Zoom room, set up by the scenario instead of by hand.
Watch out
the meeting is created under the account the connection belongs to. If several people in the team need to host, each host needs a connection of their own.
Zoom5

Create a webinar

Action

In MakeCreates a webinar for a user.

Builds the webinar itself, empty and ready, which is the step everything else hangs off: registrants, panelists, recordings.

When to use it
a campaign that spins up one session per city or per language, each created from the row that describes it.
Watch out
Zoom treats webinars and meetings as two different objects. A scenario built on this module cannot be reused as is for a plain call.
Zoom6

Delete a cloud recording

Action

In MakeRemoves a recording from a meeting or webinar.

Removes a recording from a meeting or a webinar, which is how a scenario keeps the Zoom cloud tidy once the file lives somewhere else.

When to use it
right after a copy that worked, at the tail end of the same scenario.
Watch out
a deletion does not come back. Put it behind a check that the copy really happened, and never point it at real recordings the first time you press Run once.
Zoom7

Delete a meeting

Action

In MakeRemoves a meeting by its ID. Occurrences of a recurring meeting can be removed by the occurrence ID.

Cancels a meeting from its ID, and a recurring meeting can be trimmed to a single date by passing the occurrence ID instead.

When to use it
a client who cancels in your booking tool, where the Zoom room should disappear at the same moment.
Watch out
without the occurrence ID, the whole series goes. Check which of the two you are mapping before the scenario goes live.
Zoom8

Delete a webinar

Action

In MakeRemoves a webinar for a user.

Deletes a webinar from the user's account, definitively.

When to use it
a session that never filled up and should stop showing in Zoom.
Watch out
anything you still need about that session is easier to grab beforehand. Run List webinar registrants first if the names matter to you.
Zoom9

Download a cloud recording

Action

In MakeDownloads a Cloud Recording by its URL and token.

Pulls the recording file into the scenario from its URL and token, so the next module can store it, send it or convert it.

When to use it
the archive scenario, where each finished session ends up in your own storage rather than in the Zoom cloud.
Watch out
the Free plan caps files at 5 MB and transfer at 512 MB. A full session recording goes past that, so this module belongs on a paid plan.
Zoom10

End a meeting

Action

In MakeEnds a meeting for a user.

Closes a meeting that is still running, from the scenario instead of from the host's screen.

When to use it
a room left open long after everyone has gone, or a slot that must not eat into the next one.
Watch out
cutting a live call is abrupt for whoever is still in it. A warning posted through Send a chat message beforehand makes it civil.
Zoom11

Get a meeting

Action

In MakeRetrieves the details of a meeting.

Reads one meeting and brings its details back into the scenario, which is how a message or a record gets filled with real information instead of a placeholder.

When to use it
a recap posted in another tool, where the details of the call have to be exact.
Watch out
it handles one meeting at a time. To walk through several, List meetings comes first and this module runs after it.
Zoom12

Get a webinar

Action

In MakeRetrieves the details of a webinar.

Brings back the details of a single webinar, usually because the scenario has to write something about that session somewhere else.

When to use it
a confirmation page or an internal record that has to show the session exactly as Zoom holds it.
Watch out
this module expects a webinar. For a plain call, Get a meeting is its counterpart, and the two IDs are not the same thing.
Zoom13

Make an API call

Action

In MakePerforms an arbitrary authorized API call.

The escape hatch. Any part of the Zoom API can be reached from here, with the same connection as every other module, for the day the catalog stops short of what you need.

When to use it
a corner of Zoom that has no module of its own, reached without leaving the scenario or building a second connection.
Watch out
this one assumes you can read the Zoom API reference. Everything else on this page works without that, so keep it for the gap you cannot fill otherwise.
Zoom14

Remove a webinar panelist

Action

In MakeRemoves a single panelist from a webinar.

Takes one speaker off a webinar, precisely, without touching the rest of the panel.

When to use it
a guest who cancels and should come off the panel straight away.
Watch out
one operation removes one panelist. Clearing a whole panel means running the module once per person, usually behind List webinar panelists.
Zoom15

Send a chat message

Action

In MakeSends a chat message to a channel or a contact.

Writes a message in a Zoom channel or straight to a contact, which turns Zoom into the place where your scenario talks back to the team.

When to use it
the last step of a scenario, to say that the recording is filed and where it landed.
Watch out
a scenario that posts on every event becomes background noise fast. Send the message when a human is needed, not when everything went fine.
Zoom16

Update a meeting

Action

In MakeUpdates the details of a meeting.

Pushes a change onto a meeting that already exists, so Zoom follows what the rest of your tools already know.

When to use it
a call moved in your calendar, where the Zoom room should carry the new details rather than the old ones.
Watch out
the module updates, it does not create. If the meeting was deleted on the Zoom side, the scenario needs Create a meeting instead.
Zoom17

Update a webinar

Action

In MakeUpdates the details of a webinar.

Changes the details of a webinar already in the account, one session at a time.

When to use it
a speaker swap or a new date that everyone who already registered should see in Zoom.
Watch out
the module expects a session that exists. Chain it after List webinars or Get a webinar when the scenario has to find the right one first.
Zoom18

Update meeting registrants status

Action

In MakeUpdates registrants status for a meeting.

Moves the registrants of a meeting from one status to another, which saves someone going through the Zoom list by hand.

When to use it
a meeting whose signups are checked against your customer base before the invitation goes out.
Watch out
it works on the status, not on the registration itself. Adding a person is Add a meeting registrant, and both often sit in the same scenario.
Zoom19

Update webinar registrants status

Action

In MakeUpdates registrants status for a webinar.

Applies a status change to the people registered for a webinar. One module, one session, the one you point it at.

When to use it
a paid webinar where only the signups whose payment went through get in.
Watch out
a status is a decision. Put the rule that makes it inside the scenario, because a filter sitting in front of this module is far easier to fix six months later than a habit living in someone's head.
Zoom20

List cloud recordings

Search

In MakeSearches cloud recordings from a meeting or a webinar.

Searches the cloud recordings of a meeting or a webinar and sends what it finds into the scenario.

When to use it
a catch-up run that goes looking for the recordings nobody filed while the automation was off.
Watch out
a search returns zero, one or several bundles, and the modules after it run once per bundle. Count that in your operations before aiming it at a busy account.
Zoom21

List meeting registrants

Search

In MakeLists all registrants of a meeting.

Returns the people registered for a meeting, one bundle each, ready for whatever comes next.

When to use it
the attendance list that lands in a spreadsheet after a training session, without opening Zoom at all.
Watch out
this reads registrants, it does not change them. Update meeting registrants status is the module that acts on what you find here.
Zoom22

List meetings

Search

In MakeLists all meetings, optionally by category.

Goes through the meetings of the account, and the search can be narrowed by category.

When to use it
an internal recap that needs to know what is planned before it decides anything.
Watch out
a search with no filter reads everything it can reach. Narrow it by category first, then chain the rest, or the scenario spends operations for nothing.
Zoom23

List webinar panelists

Search

In MakeLists all panelists of a webinar.

Gives you the panel of a webinar, speaker by speaker.

When to use it
the check you run before a session, to confirm that everyone who should be on stage actually is.
Watch out
panelists and registrants are two separate lists in Zoom, and this module only knows about the panel.
Zoom24

List webinar registrants

Search

In MakeLists all registrants of a webinar.

Walks through everyone signed up for a webinar and pushes them into the scenario one by one.

When to use it
the handover to your CRM after a session, where each registrant becomes a row or a contact.
Watch out
the list is a photograph taken when the scenario runs. Someone who signs up afterwards is simply not in it, so choose when the run happens with that in mind.
Zoom25

List webinars

Search

In MakeLists all webinars of a user.

Lists the webinars of a user, and it is often the first module of a scenario that has to find a session before doing anything to it.

When to use it
a cleanup pass that looks for the sessions nobody needs any more.
Watch out
it stays on one user's webinars. A team with several hosts needs one connection per host, and the scenario decides which one it asks.
Need help

Need help automating Zoom with Make?

A person reads every message.

FAQ

Zoom and Make, the questions that come next

01Is the Zoom Make integration free?
Yes. Zoom is a standard app, so it is available from the Free plan like the rest of the standard catalog. Free gives you 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of transfer. Paid plans bring the interval down to 1 minute, lift the limit on active scenarios and stretch execution to 40 minutes. Your Zoom subscription is a separate matter, handled on the Zoom side and priced by Zoom.
02What do you need to connect Zoom to Make?
A Zoom account, plus a registered app on the Zoom side. Zoom hands out API credentials through an app you create yourself, so before touching Make you log in to the Zoom App Marketplace, click Manage, open Created Apps and select your OAuth app. If Zoom asks for a callback URI, the documentation gives this one: https://www.integromat.com/oauth/cb/zoom-user. Copy the Client ID and the Client secret, go back to Make, add a Zoom module and click Create a connection to paste them. One connection then serves every Zoom module in every scenario you build.
03Does the Zoom trigger work in real time?
Yes. All 5 Zoom triggers are instant, which means Zoom calls Make through a webhook, a notification the app sends the moment something happens. There is no interval to set and nothing to poll: the scenario starts when the event lands. A scheduled trigger works the other way round, with Make going to look at regular intervals, and a new scenario checks every 15 minutes by default. Zoom has 0 scheduled triggers, so that clock is not what drives these scenarios. The scenario still has to be switched on for the webhook to be live.
04What if a Zoom module is missing in Make?
Use Make an API call. Zoom ships that module, and it reaches any part of the Zoom API from inside the scenario, with the same connection as the others, so you are not boxed in by the 19 actions and 6 searches in the list. One honest warning about the reference: the Make documentation page for Zoom states that its content is AI-generated from Zoom's official documentation, that it may contain mistakes, and that anything important should be checked with Zoom directly. When the stake is high, read the matching entry in the Zoom API reference.
05Make or n8n for Zoom?
It depends on who will maintain the scenario. Make is a visual editor where you assemble modules and read the bundles passing between them, which suits a team that wants to build without code. n8n sits closer to a developer tool, can be self-hosted, and feels natural if someone on the team writes JavaScript. Zoom exists on both sides with the same meetings, webinars and recordings, so the app is rarely the deciding factor. The plan you pay for, the interval you need and the person who fixes the scenario at eight in the morning matter more.
Hack'celeration Lab

Get our weekly automation tips.

No spam. Unsubscribe anytime.