Zoom Connector
Connect Zoom to Brevo through Tajo to automatically sync meeting participants and webinar attendees as contacts, trigger post-meeting follow-up sequences, and track engagement metrics for your marketing automations.
Overview
| Property | Value |
|---|---|
| Platform | Zoom |
| Category | Video Conferencing (Custom) |
| Setup Complexity | Medium |
| Official Integration | No |
| Data Synced | Participants, Events, Webinars, Contacts |
| Auth Method | OAuth 2.0 / Server-to-Server OAuth |
Features
- Participant sync - Auto-create Brevo contacts from meeting participants
- Webinar attendee capture - Sync webinar registrants and attendees
- Meeting event triggers - Fire automations on meeting start, end, and recording events
- Engagement tracking - Track attendance duration and participation metrics
- Webinar follow-up - Trigger targeted email sequences based on webinar attendance
- Recording notifications - Send recording links via Brevo email campaigns
Prerequisites
Before you begin, ensure you have:
- A Zoom account (Pro plan or above)
- A Zoom Server-to-Server OAuth app or OAuth app via Zoom App Marketplace
- A Brevo account with API access
- A Tajo account with connector permissions
Authentication
Server-to-Server OAuth (Recommended)
# Create a Server-to-Server OAuth app at marketplace.zoom.usexport ZOOM_ACCOUNT_ID=your_account_idexport ZOOM_CLIENT_ID=your_client_idexport ZOOM_CLIENT_SECRET=your_client_secret// Get access token via Server-to-Server OAuthconst tokenResponse = await fetch('https://zoom.us/oauth/token', { method: 'POST', headers: { 'Authorization': `Basic ${Buffer.from( `${process.env.ZOOM_CLIENT_ID}:${process.env.ZOOM_CLIENT_SECRET}` ).toString('base64')}`, 'Content-Type': 'application/x-www-form-urlencoded' }, body: new URLSearchParams({ grant_type: 'account_credentials', account_id: process.env.ZOOM_ACCOUNT_ID })});
const { access_token } = await tokenResponse.json();OAuth 2.0 (User-Level)
// Authorization URL for user-level OAuthconst authUrl = 'https://zoom.us/oauth/authorize?' + new URLSearchParams({ client_id: process.env.ZOOM_CLIENT_ID, redirect_uri: 'https://your-app.com/callback', response_type: 'code' });
// Exchange code for tokensconst tokenResponse = await fetch('https://zoom.us/oauth/token', { method: 'POST', headers: { 'Authorization': `Basic ${Buffer.from( `${process.env.ZOOM_CLIENT_ID}:${process.env.ZOOM_CLIENT_SECRET}` ).toString('base64')}`, 'Content-Type': 'application/x-www-form-urlencoded' }, body: new URLSearchParams({ grant_type: 'authorization_code', code: authorizationCode, redirect_uri: 'https://your-app.com/callback' })});Configuration
Basic Setup
connectors: zoom: enabled: true account_id: "${ZOOM_ACCOUNT_ID}" client_id: "${ZOOM_CLIENT_ID}" client_secret: "${ZOOM_CLIENT_SECRET}"
sync: participants: true webinars: true recordings: true
webhook: secret_token: "${ZOOM_WEBHOOK_SECRET}" verification_token: "${ZOOM_VERIFICATION_TOKEN}"
lists: meeting_participants: 15 webinar_attendees: 16 webinar_registrants: 17Field Mapping
field_mapping: email: email name: FIRSTNAME join_time: MEETING_JOIN_DATE duration: MEETING_DURATION webinar_title: WEBINAR_NAME attendance_status: ATTENDANCE_STATUS registration_source: UTM_SOURCEAPI Endpoints
| Endpoint | Method | Description |
|---|---|---|
https://api.zoom.us/v2/users | GET | List users |
https://api.zoom.us/v2/users/{userId}/meetings | GET | List meetings |
https://api.zoom.us/v2/meetings/{meetingId} | GET | Get meeting details |
https://api.zoom.us/v2/past_meetings/{meetingId}/participants | GET | List past meeting participants |
https://api.zoom.us/v2/users/{userId}/webinars | GET | List webinars |
https://api.zoom.us/v2/webinars/{webinarId}/registrants | GET | List webinar registrants |
https://api.zoom.us/v2/webinars/{webinarId}/participants | GET | List webinar participants |
https://api.zoom.us/v2/meetings/{meetingId}/recordings | GET | Get meeting recordings |
https://api.zoom.us/v2/webhooks | POST | Subscribe to webhooks |
Code Examples
Initialize Connector
import { TajoClient } from '@tajo/sdk';
const tajo = new TajoClient({ apiKey: process.env.TAJO_API_KEY, brevoApiKey: process.env.BREVO_API_KEY});
await tajo.connectors.connect('zoom', { accountId: process.env.ZOOM_ACCOUNT_ID, clientId: process.env.ZOOM_CLIENT_ID, clientSecret: process.env.ZOOM_CLIENT_SECRET});Sync Meeting Participants
// Retrieve past meeting participantsconst response = await fetch( `https://api.zoom.us/v2/past_meetings/${meetingId}/participants`, { headers: { 'Authorization': `Bearer ${accessToken}`, 'Content-Type': 'application/json' } });
const { participants } = await response.json();
for (const participant of participants) { if (participant.user_email) { await tajo.contacts.sync({ email: participant.user_email, attributes: { FIRSTNAME: participant.name, MEETING_DURATION: participant.duration, MEETING_JOIN_DATE: participant.join_time, ATTENDANCE_STATUS: 'attended' }, listIds: [15] }); }}Sync Webinar Attendees
// Get webinar attendees and sync to Brevoconst attendeesResponse = await fetch( `https://api.zoom.us/v2/past_webinars/${webinarId}/participants`, { headers: { 'Authorization': `Bearer ${accessToken}` } });
const { participants: attendees } = await attendeesResponse.json();
for (const attendee of attendees) { await tajo.contacts.sync({ email: attendee.user_email, attributes: { FIRSTNAME: attendee.name, WEBINAR_NAME: webinarTitle, ATTENDANCE_STATUS: 'attended', MEETING_DURATION: attendee.duration }, listIds: [16] });}Handle Zoom Webhooks
app.post('/webhooks/zoom', async (req, res) => { // Handle Zoom URL validation challenge if (req.body.event === 'endpoint.url_validation') { const hashForValidation = crypto .createHmac('sha256', process.env.ZOOM_WEBHOOK_SECRET) .update(req.body.payload.plainToken) .digest('hex');
return res.json({ plainToken: req.body.payload.plainToken, encryptedToken: hashForValidation }); }
// Verify webhook signature const message = `v0:${req.headers['x-zm-request-timestamp']}:${JSON.stringify(req.body)}`; const hash = crypto .createHmac('sha256', process.env.ZOOM_WEBHOOK_SECRET) .update(message) .digest('hex'); const signature = `v0=${hash}`;
if (req.headers['x-zm-signature'] !== signature) { return res.status(401).send('Unauthorized'); }
const { event, payload } = req.body;
await tajo.connectors.handleWebhook('zoom', { topic: event, payload: payload });
res.status(200).send('OK');});Rate Limits
| Category | Limit | Notes |
|---|---|---|
| Light API calls | 30 req/sec | GET user, meeting info |
| Medium API calls | 20 req/sec | List participants, webinars |
| Heavy API calls | 10 req/sec | Reports, recordings |
| Daily limit | 5,000+ | Depends on plan level |
Rate Limit Headers
Zoom returns X-RateLimit-Limit, X-RateLimit-Remaining, and Retry-After headers. Implement backoff logic based on these headers to avoid 429 errors.
Troubleshooting
| Issue | Cause | Solution |
|---|---|---|
| 401 Unauthorized | Token expired | Refresh Server-to-Server OAuth token |
| Missing participants | Meeting not ended | Wait until meeting ends for full data |
| Webhook validation fails | Wrong secret | Verify webhook secret in Zoom Marketplace |
| No email data | Guest participants | Enable registration to capture emails |
| Rate limit 429 | Too many requests | Implement exponential backoff |
Debug Mode
connectors: zoom: debug: true log_level: verbose log_webhooks: trueBest Practices
- Use Server-to-Server OAuth - Simpler authentication without user interaction
- Enable webinar registration - Required to capture attendee email addresses
- Process after meeting end - Participant data is only complete after meetings end
- Segment by event type - Assign different Brevo lists for meetings vs. webinars
- Track engagement metrics - Use duration and join time for lead scoring
- Send recording follow-ups - Automate recording link delivery via Brevo
Security
- OAuth 2.0 - Server-to-Server or user-level OAuth authentication
- Webhook verification - HMAC-SHA256 signature validation
- URL validation - Challenge-response verification for webhook endpoints
- Scoped permissions - Request minimum required OAuth scopes
- Token rotation - Server-to-Server tokens auto-expire (1 hour)
- Encrypted transport - TLS 1.2+ for all API communications
Related Resources
Open-Source Implementation Map
This section is derived from official or public repository material discovered for the Zoom connector. Use it as the engineering companion to the setup guide above: it shows where the API surface lives, what implementation assets exist, and how Tajo should translate them into reliable Brevo sync behavior.
Repository Snapshot
| Repository | Commit | Languages / formats | Files |
|---|---|---|---|
| zoom/api | 4429982 | erb (170), JavaScript (12), scss (5), Markdown (3), png (3), Ruby (2) | 208 |
Integration Shape
graph LR Source["Zoom API / repository"] --> Auth["Auth and scopes"] Source --> Objects["Objects, events, and schemas"] Auth --> Tajo["Tajo connector runtime"] Objects --> Tajo Tajo --> Brevo["Brevo contacts, attributes, lists, campaigns"] Tajo --> Ops["Backfill, cursor, retries, logs"]What To Reuse
- This definition is no longer being maintained. Please visit our new documentation to get started using the Zoom API.
- Zoom API Version 2
- This repo is the source code for our documentation. You can view the documentation here.
- Feel free to submit issues or fork this repo and contribute changes.
- Getting Started
Tajo Revamp Checklist
- Keep authentication setup aligned with the vendor docs and the public repository’s current API shape.
- Map primary resources into explicit Tajo sync objects with stable external IDs.
- Prefer cursor-based or updated-at incremental sync where the API exposes it; otherwise document the fallback.
- Treat webhook handlers as idempotent and replay-safe, especially for order, contact, ticket, and campaign events.
- Capture pagination, rate limits, retry headers, and partial-failure behavior in connector smoke tests.
- Keep examples small and runnable against sandbox or test-mode accounts.