Zoom Connector
Connector implementation
Build the Zoom integration
Video conferencing and webinar platform for meetings, events, and team collaboration
Implementation Overview
Implement a Zoom connector that authenticates to the vendor surface, normalizes source records in Tajo, and activates eligible data in Brevo.
Treat this as an implementation guide. Build and validate the auth, mapping, sync, and operations paths before production use.
mcp.zoom.us/mcp/zoom/streamable
| Property | Value |
|---|---|
| Integration surface | API + MCP |
| Implementation status | Implementation required |
| Category | Video & Webinars |
| Setup complexity | medium |
| Vendor documentation | developers.zoom.us/docs/api/ |
| Allowed host | Not recorded |
| Base URL | Not recorded |
| OpenAPI schema | github.com/zoom/api/blob/master/openapi.v2.json |
| MCP server | mcp.zoom.us/mcp/zoom/streamable |
| Last researched | 2026-08-19 |
Zoom publishes an OpenAPI v2 spec for its REST API — but the github.com/zoom/api repo was archived in 2021, so that spec is roughly five years stale. Three MCP endpoints were verified by handshake on 2026-08-07 (zoom, docs, whiteboard); all three name zoom.us as the authorization server, which does not offer dynamic client registration.
Authentication
-
OAuth 2.0 (MCP mode).
- Authorize: zoom.us/oauth/authorize
- Token: zoom.us/oauth/token
- The authorization server publishes no scope list.
-
Use github.com/zoom/api/blob/master/openapi.v2.json to generate or validate typed API clients and request models.
-
Validate the MCP server endpoint at mcp.zoom.us/mcp/zoom/streamable and document required headers, auth grants, and tool availability.
-
Keep developers.zoom.us/docs/api/ linked from the connector runbook so operators can confirm vendor behavior during incidents.
-
Store credentials per Tajo workspace and keep tenant-specific secrets out of connector configuration files.
-
Add a credential smoke test that verifies read access to a harmless resource before running backfills or enabling webhooks.
Data To Sync
Start with these inferred data domains, then confirm exact vendor resources and permissions from the source documentation:
- Events, webhooks, and behavioral activity
The connector should make source records idempotent by keeping a stable key such as a vendor object ID, email address, event ID, ticket ID, order ID, or campaign ID. If the vendor only exposes list APIs, Tajo should store the cursor strategy and replay policy explicitly.
Sync Shape
No typed contract exists for Zoom, so the direction of each resource and its conflict handling are not recorded. Direction is declared per resource on a connector contract; see the connector catalog for how contracts are promoted.
Mapping To Tajo/Brevo
No Brevo projection is recorded for Zoom. A projection is declared on a typed connector contract, and Zoom does not have one yet, so this page will not state a mapping it cannot source.
The conventions that apply to every connector — stable external IDs, normalization, backfill and sync strategy, error handling, and the builder checklist — are documented once under “Applies to every connector” on the connector catalog.