Zoom

Read Zoom users, meetings, webinars, registrants, participants, cloud recordings and usage reports; create and update meetings and registrants.

Schedule meetings from business events and feed attendance and usage into CRM, HR and reporting.

Build a flow with Zoom Provider API documentation

Source actions

Destination actions

Data types

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

daily usage

Daily usage report
Source
New users, meetings, participants and meeting minutes per day for a month.

meeting registrants

Add meeting registrant
Destination
Not retried automatically
Registers a person for a meeting and returns their join link.
List meeting registrants
Source
Registrants of a meeting that requires registration.

meeting reports

List user meeting reports
Source
Past meetings of a user with participant counts and minutes (Pro or higher).

meetings

Create meeting
Destination
Not retried automatically
Schedules a meeting for a host user.
Get meeting
Source
Meeting details, settings and occurrences.
List meetings
Source
Meetings hosted by a user.
Update meeting
Destination
Duplicate protected
Updates topic, time, duration, agenda or settings of a meeting.

past meeting participants

List past meeting participants
Source
Participants of an ended meeting instance.

past meetings

Get past meeting
Source
Summary of an ended meeting instance.

recordings

List cloud recordings
Source
Cloud recordings of a user's meetings with file metadata.

users

Get user
Source
One user by ID or email.
List users
Source
Users in the account.

webinars

Get webinar
Source
Webinar details and settings.
List webinars
Source
Webinars hosted by a user.

Authentication

Server-to-Server OAuth app (account ID, client ID, client secret)

Plans and access

Any Zoom account; reports need Pro or higher, webinars a webinar licence, cloud recordings a paid plan. Server-to-Server OAuth apps are account-level and must be created by an admin with the scopes each operation needs.

Test environment

A free Zoom account can create an internal Server-to-Server OAuth app; paid features need a licence.

Rate limits

Per-account limits by API category (light, medium, heavy, resource-intensive) and plan; daily caps for meeting create/update per user. HTTP 429 with Retry-After.

Provider events

Zoom webhooks for meeting, webinar, recording and user events. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

Server-to-Server OAuth: account_id is sent as a query parameter on the token request (as in Zoom's token examples) and grant_type=account_credentials in the form body; the account ID is an identifier, not a secret.
Meeting start URLs and passcodes are never mapped, because they grant host access.
Recording metadata is read; recordings are not downloaded.
Meeting and registrant creation have no idempotency key and are not repeated automatically.
Deleting meetings, ending live meetings, and user provisioning are not implemented.
Recording and report date ranges are limited by Zoom to one month per request.