Resources · n8n integration

Zoom n8n integrationAutomate Zoom with n8n.

Every Zoom meeting in your workflow, created and updated without opening the app. The Zoom n8n integration ships one node with 5 operations on the Meeting resource: create, retrieve, list, update, delete. No trigger node here, so a Schedule Trigger starts the run. Aimed at ops teams.

Try the Zoom integration on n8nSee the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Zoom n8n integration actually do?

The Zoom n8n integration is a single node, n8n-nodes-base.zoom, that calls the Zoom API for you. It covers one resource, Meeting, with 5 operations: create a meeting, get a meeting, get many meetings, update a meeting, delete a meeting. A credential holds your Zoom app details, and any workflow picks it from a dropdown.

Nothing gets installed. The node comes with n8n, on n8n Cloud and on a self-hosted instance alike.

Start with the booking scenario, because it is the one most teams build first. A prospect picks a slot on a form, the workflow runs meeting.create with a Topic and a Start Time, and the join link goes straight into Slack for the account manager. Send the same link by email with Gmail and the prospect never waits for a manual invite.

Second scenario: the weekly check on what is actually scheduled. meeting.getAll with Return All switched on walks through every page of results and hands you the full list, which you drop into Google Sheets for a quick look at who books what. Leave Return All off and n8n stops at Limit, which is fine for a spot check and wrong for a monthly report.

Third one is housekeeping. A deal moves to lost in your CRM, the workflow reads the stored meeting ID, calls meeting.update to push the slot back or meeting.delete to drop it. Both operations need the meeting ID, not the topic, so store that ID the moment the meeting gets created.

Know where the node stops. One resource, 5 operations, all of them about meetings. Anything else in the Zoom API goes through the HTTP Request node, which reuses the very same credential through predefined authentication, so you keep one place to manage access. There is also no Zoom trigger node: a workflow that reacts to Zoom starts from a Schedule Trigger on a fixed interval, from an n8n Webhook called by another service, or from the trigger of the tool sitting next to Zoom in the process.

If you want an outside view of the platform before you build on it, the n8n review covers what it does well and where it hurts. To get a team building these workflows without trial and error, look at the n8n training.

Connect

How do you connect Zoom to n8n?

  1. 01

    Create an OAuth app in Zoom

    Your Zoom account needs one of three permissions first: Account owner, Account admin, or the Zoom for developers role. Without one of them the app cannot be created. Then create an OAuth app and pick User-managed app when Zoom asks how the app is managed. Zoom generates a Client ID and a Client Secret for it, the two values n8n will ask for.

  2. 02

    Register the redirect URL

    Open a Zoom credential in n8n, in the Credentials menu, and copy the OAuth Callback URL it displays. Paste it into your Zoom app as an OAuth Redirect URL. If the n8n credential also shows a Whitelist URL, add that one as a redirect URL too. Skip this and the connection loops back with an error instead of returning a token.

  3. 03

    Grant the meeting scopes

    In the Zoom app, add the scopes the node needs. For the full range of what the node does, select meeting:read and meeting:write. Then copy the Client ID and Client Secret into the n8n credential and connect. The credential is stored once and shows up in the dropdown of every Zoom node you add afterwards.

Actions

What the Zoom node can do

The Zoom node exposes 5 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateGetGet ManyUpdateDelete
Meeting✓✓✓✓✓

Meeting

5 operations
01

Create a meeting

meeting.create

What you see in n8n

Notes & use cases

This operation books a meeting on the connected Zoom account and returns its meeting ID, the value every later operation depends on.

Key parameters

  • Topic: the meeting title attendees see, usually {{ $json.subject }} from the item that started the run.
  • Type: 1 for an instant meeting, 2 for a scheduled one, 3 for recurring with no fixed time, 8 for recurring with a fixed time.
  • Start Time: only read for scheduled and fixed-time recurring meetings, paired with Timezone Name or ID.
Use cases
a demo request opens the slot and the confirmation email carries the join link back to the prospect.
02

Delete a meeting

meeting.delete

What you see in n8n

Notes & use cases

Removing a meeting is the cleanup step of a cancellation flow: Zoom drops the slot and the join link stops working.

Key parameters

  • ID: the meeting ID returned at creation, typically {{ $json.id }} read back from wherever you stored it.
  • Occurrence ID: targets one date of a recurring meeting instead of the whole series.
  • Schedule Reminder: when on, hosts and alternative hosts get an email about the cancellation.
Use cases
a deal marked lost in the CRM clears next week's call and warns the host by email.
03

Get a meeting

meeting.get

What you see in n8n

Notes & use cases

Reading one meeting gives you its current state, useful before deciding whether the rest of a workflow should keep going.

Key parameters

  • ID: the meeting ID; the topic will not work here, Zoom matches on the identifier only.
  • Occurrence ID: pulls the details of one specific occurrence of a recurring meeting.
  • Show Previous Occurrences: when on, the response also covers the past occurrences of that recurring meeting.
Use cases
before sending a reminder, check the slot still exists and read its start time to build the message.
04

Get many meetings

meeting.getAll

What you see in n8n

Notes & use cases

Listing is how you get a view of the calendar rather than a single call, and it is the operation that feeds reports.

Key parameters

  • Return All: on, n8n follows every page of results until the list is complete; off, it stops at Limit.
  • Limit: the maximum number of meetings returned when Return All stays off.
  • Type: filter on scheduled, live for meetings running right now, or upcoming.
Use cases
a Monday export of every upcoming meeting into a spreadsheet the team reads before the week starts.
05

Update a meeting

meeting.update

What you see in n8n

Notes & use cases

Changing an existing meeting keeps the same join link alive, which matters when the invite already went out to attendees.

Key parameters

  • ID: identifies the meeting to change; leave it empty and the node stops the execution.
  • Topic and Agenda: rename the call and rewrite its description inside Update Fields.
  • Duration: the new length in minutes, handy when a discovery call turns into a working session.
  • Schedule For: hands the meeting to a colleague, addressed by their email.
Use cases
a rescheduled slot updates in place instead of forcing a new link on everyone.
Need help

Need help automating Zoom with n8n?

A person reads every message.

FAQ

Zoom and n8n, the questions that come next

01Is the Zoom n8n integration free?
Yes on the n8n side. The Zoom node is built into n8n, so there is nothing to install and nothing extra to pay for it, whether you run n8n Cloud or a self-hosted instance under the Community Edition and its Sustainable Use licence. The same workflow behaves the same way in both setups, which means you can prototype on Cloud and move the JSON to your own server later. What a Zoom account itself costs is a separate question and depends on your Zoom plan, not on n8n. The credential you create is reusable, so a second or third Zoom workflow adds no setup cost at all.
02Which Zoom credentials does n8n need?
OAuth2, in practice. The node accepts an access token credential and an OAuth2 credential, but Zoom removed support for JWT access tokens in 2023 and fully deprecated that method, so new credentials have to go through OAuth2. You create a user-managed OAuth app on the Zoom App Marketplace, which gives you a Client ID and a Client Secret. The n8n credential shows an OAuth Callback URL, and sometimes a Whitelist URL, and both belong in the Zoom app as OAuth Redirect URLs. Add the meeting:read and meeting:write scopes to cover everything the node does. Your Zoom account also needs to be account owner, account admin, or hold the Zoom for developers role.
03What are the limits of the Zoom node in n8n?
The node stays on one thing: meetings. One resource, 5 operations, covering creation, retrieval, listing, update and deletion. Anything else exposed by the Zoom API is out of scope for the dedicated node, and the answer there is the HTTP Request node, which calls any Zoom endpoint while reusing the same credential through predefined authentication. Second limit worth knowing: listing is paginated. Leave Return All off and you only get up to Limit meetings, which quietly truncates a report. Third: the operations that change or read a single meeting need the meeting ID, never the topic, so keep that ID somewhere your workflow can read it back.
04Can n8n react to a Zoom meeting in real time?
No, because Zoom has no trigger node in n8n. There is nothing to listen with on the Zoom side, so a workflow that reacts to meetings has to be started some other way. Three options cover almost every case. A Schedule Trigger runs the workflow at a fixed interval and calls Get Many to see what changed since the last pass, which is the closest thing to monitoring here. An n8n Webhook, meaning a URL that another service calls, lets a third-party tool kick off the workflow. Or the trigger of the tool sitting next to Zoom in your process, a form or a CRM, starts the run and Zoom simply follows.
05n8n or Make for Zoom meetings?
It depends on three things, and price is only one of them. Make is hosted by Make, with no self-hosting option, and it bills per operation, so a workflow that lists hundreds of meetings every morning has a cost that grows with your volume. n8n runs on Make's model too, through n8n Cloud, but it can also run on your own server via Docker or npm, which changes who holds the data and how the bill behaves. The second criterion is where meeting data is allowed to live, an easy answer in regulated contexts. The third is how you like to think: both are visual, n8n leans closer to code when a workflow gets gnarly.
Same platform

Other docs you might need on this stack.

Browse all integrations