Source connector

Zoom connector

Zoom integration for databases, warehouses and BI tools

Video meetings, webinars, and workplace collaboration. Datrise captures Zoom entities such as meetings, participants, webinars, recordings, and usage reports, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Zoom REST API v2 authenticates with OAuth 2.0, incremental runs key on from/to date-range parameters (per endpoint, e.g. the Dashboard and Reports APIs), and Zoom caps calls at Rate-limit categories (Light/Medium/Heavy/Resource-Intensive) vary by plan, e.g. Business+ accounts get 80 requests/second on Light endpoints versus Free accounts capped at 4 requests/second and 6,000 requests/day on the same category.

Of the 5 objects, 5 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `zoom_meetings`) with a schema derived from the Zoom API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Zoom pipeline page, and join the waitlist to get the Zoom connector (Work management) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Zoom data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
meetings	zoom_meetings	Upsert by primary key, incremental on updated-at
participants	zoom_participants	Upsert by primary key, incremental on updated-at
webinars	zoom_webinars	Upsert by primary key, incremental on updated-at
recordings	zoom_recordings	Upsert by primary key, incremental on updated-at
usage reports	zoom_usage_reports	Upsert by primary key, incremental on updated-at

Zoom API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Zoom REST API v2
Authentication	OAuth 2.0 — User-facing Marketplace apps use the standard OAuth 2.0 authorization-code grant, while server-to-server integrations use a Server-to-Server OAuth app on the `account_credentials` grant, which Zoom introduced to replace deprecated JWT apps.
Pagination	token — Most endpoints use `page_size` (up to 300 on lightweight list endpoints) plus `next_page_token`, which is an empty string on the last page; the older `page_number`/`page_count` style is being phased out.
Rate limit	Rate-limit categories (Light/Medium/Heavy/Resource-Intensive) vary by plan, e.g. Business+ accounts get 80 requests/second on Light endpoints versus Free accounts capped at 4 requests/second and 6,000 requests/day on the same category.
Incremental cursor	from/to date-range parameters (per endpoint, e.g. the Dashboard and Reports APIs) — There is no single updated-since field across the API: Dashboard/Reports endpoints take `from`/`to` restricted to a month within a rolling 6-month window, while most object list endpoints (users, meetings) have no updated-since filter and rely on webhooks for change detection.
Webhooks	Yes — Event Subscriptions (Marketplace webhooks, e.g. `user.created`, `user.deleted`, `meeting.deleted`)
Bulk export	No
Deletes detectable	Yes — Only surfaced via webhook events such as `user.deleted` and `meeting.deleted`; there is no deleted-records list endpoint to poll.

Official API reference

What bites when replicating Zoom

JWT apps were deactivated after September 8, 2023, so any connector still authenticating with a JWT app token must migrate to a Server-to-Server OAuth app using the `account_credentials` grant.
Access tokens from the `account_credentials` grant expire after 3,600 seconds and are not refreshable, so a new token must be requested on every expiry rather than refreshed.
Rate limits vary sharply by plan: Free accounts get only 1 request/second and 1,000 requests/day on Heavy endpoints versus 40 requests/second on Business+.
Dashboard and Reports endpoints restrict the `from`/`to` window to a single month that must fall within the trailing 6 months, so backfilling a year of history takes 12 separate paginated requests.

Compare this against every other documented API

Popular destinations for Zoom

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Zoom connector FAQ

What Zoom data does the connector extract?: 5 objects: meetings, participants, webinars, recordings and usage reports. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the Zoom integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Zoom data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Zoom → destination pair has its own page with the object-to-table mapping.

Related Work management sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Zoom pipeline with guided onboarding

Join the waitlist to get priority access for Zoom integrations with guided setup, schema-aware mapping, and production-grade incremental sync.