Zoom

Zoom API (Recruiting & Meetings). 123 operations: meetings, registrants, polls, surveys, live streaming, past meetings and templates; webinars, panelists and past webinars; cloud recordings, transcripts and recording analytics; users, settings, presence and company contacts; Team Chat messages and channels; meeting and webinar reports.

Credential: Zoom (Server-to-Server OAuth: accountId + clientId + clientSecret) - see Credentials.

Scopes

Each operation below lists the scope it needs. Scopes are ticked on the Scopes tab of the Server-to-Server OAuth app in the Zoom App Marketplace. Pipory's Zoom credential is the account_credentials grant, so the token is account-wide and there is no per-user consent screen — a scope added in the Marketplace is simply picked up by the next token exchange. Zoom is midway through a scope migration and BOTH systems are live, so every value below names the GRANULAR scope first (meeting:write:meeting — what an app created today is offered, one scope per endpoint) and the CLASSIC one in parentheses (meeting:write — coarse, one per resource family, still accepted on existing apps). Two operations are granular-ONLY, and that is not an omission: the recording analytics summary and details endpoints shipped after the migration began, so an app still running on classic scopes cannot call them at all. The :admin suffix is the account-level variant, which is what an app must hold to act on a user OTHER than the one that installed it — 110 of the 123 operations have a user-level granular scope and the table names that one, but a Server-to-Server app is account-wide by construction, so the :admin form of the same scope is generally the one to tick; it is spelled out below only where Zoom offers no non-admin variant at all, which is List users and all twelve Reports endpoints. The trap that wastes the most time is not the scope string but the ROLE: a scope you cannot find in the Marketplace editor is usually one your Zoom role may not grant, because an account admin has to enable the Server-to-Server OAuth app role under User Management → Roles → Role Settings → Advanced features AND assign your role the matching permission before that checkbox exists to tick. And no scope fixes a PLAN gate — webinars need a Pro-or-higher plan with the Webinar add-on, cloud recording needs Pro-or-higher with Cloud Recording enabled on the host, every Reports endpoint needs Pro-or-higher, and the AI Companion meeting summary additionally needs the host's own Meeting Summary with AI Companion setting enabled and never returns for an end-to-end-encrypted meeting. If a run fails with a permission error, the node names the missing scope in the error - grant it and re-run; you do not need to rebuild the workflow.

Operations (123)

Meetings

Meeting registrants

Meeting polls & surveys

Meeting live streaming

Past meetings

Meeting templates

Webinars

Webinar registrants

Webinar panelists

Webinar polls & surveys

Webinar live streaming

Past webinars

Cloud recordings

Users & contacts

Team Chat

Reports

Example

Create a meeting and hand out the join link

The node's original operation and still the most useful one. The value a workflow wants is joinUrl — the link to put in a calendar invite or a Slack message — and it is available immediately, unlike Google Meet links which Google provisions asynchronously.

Set Operation to createMeeting, then fill in:

Sets {{meeting.joinUrl}} (the link to send), {{meeting.meetingId}}, {{meeting.startUrl}} (host-only — treat it as a secret) and {{meeting.topic}}.