Skip to main content
Zoom delivers webhooks through Event Subscriptions, configured once on your Marketplace app.
This guide covers the Zoom (Server-to-Server OAuth) integration. For the regular Zoom integration (authorization code, one end user per connection), see its own webhooks guide instead — the setup differs enough between the two that they’re documented separately.

​
How it works

  1. Zoom sends a POST request to your Nango webhook URL when a subscribed event occurs on the account that authorized your app.
  2. Nango verifies the delivery’s signature against the Webhook secret on the integration, then matches the event’s payload.account_id against connection_config.accountId on your connections — the same Account ID you entered when connecting (see how do I link my account?).
  3. Nango forwards the event to your app, or triggers a sync.
Zoom doesn’t expose Event Subscriptions setup through any API — there’s no endpoint to create a subscription, enable an event type, or retrieve the Secret Token. Everything in Setup is a one-time dashboard task, done once per app.

​
Setup

​
1. Get your Nango webhook URL

In the Nango dashboard, open your Zoom (Server-to-Server OAuth) integration and copy the Webhook URL. Use it as-is, with no query param — Nango matches each delivery to a connection via account_id.
A Server-to-Server app is typically set up for one account, so this is usually just the one connection. If you have more than one Zoom (Server-to-Server OAuth) connection (each its own app, with its own Account ID), register a separate Event Subscription per app (see step 3) — each app has its own Features → Access page.

​
2. Set the webhook secret in Nango

  1. Go to the Zoom App Marketplace, open your app under Develop → Build App, then go to Features → Access.
  2. Turn on Event Subscriptions. Zoom immediately generates a Secret Token on this page — copy it.
  3. In the Nango dashboard, open your Zoom (Server-to-Server OAuth) integration, go to the Settings tab, and paste it into the Webhook Secret field.
Do this before creating any Event Subscription. Zoom validates the destination URL synchronously as part of both creating a subscription and saving the app, and Nango can only answer that validation request once the secret is set — see step 3.
Zoom issues one Secret Token per app, so the integration-level Webhook secret covers every connection under that app — there’s no per-connection override.

​
3. Add Event Subscriptions in Zoom

  1. On the same Features → Access page, click Add Event Subscription.
  2. Under Event notification endpoint URL, paste your Nango webhook URL from step 1. Zoom immediately sends a validation request to that URL to confirm you control it — Nango answers this automatically since the Webhook secret is already set. If validation fails, double-check the secret matches the Secret Token from step 2 before retrying.
  3. Under the event subscription’s scope, choose “All users in your account” — this app is only ever used by your own account.
  4. Click Add events and select the events you want to receive.
  5. Save the app.

​
Handle the webhook

Once routed, you have two options:
  • Forward it to your app — Nango forwards the event to your webhook URL with connection attribution. See External webhook forwarding.
  • Process it in a sync — run a sync when the webhook arrives using webhookSubscriptions and onWebhook in a sync script. See Real-time syncs.

​
Payload

Every delivery has the same shape: an event name, an event_ts timestamp, and a payload object carrying account_id plus the affected object (its fields vary by event):

​
Supported events

event (used as the webhook type for webhookSubscriptions/onWebhook) is one of Zoom’s namespaced event names. Common ones: For the full list across meetings, webinars, recordings, phone, chat, and more, see Zoom’s webhook events reference.

​
Connection matching

Nango matches payload.account_id against connection_config.accountId on your connections. If nothing matches payload.account_id, the delivery is still accepted (so Zoom doesn’t see an error and retry), but isn’t routed to any connection.
With no Webhook secret configured, every delivery is rejected outright — it never reaches routing.

​
Retries and duplicate deliveries

Zoom retries a failed delivery (any non-2xx response) up to 3 times, at +5min, +25min, and +85min. Each attempt, including retries, carries a freshly signed timestamp — not a replay of the original request. Nango also dedupes by the delivery’s x-zm-request-id, which stays the same across retries. If the same delivery arrives again after already being processed, Nango accepts it (so Zoom stops retrying) but doesn’t forward it or re-trigger a sync a second time.

​
Rollback strategy

To stop deliveries, remove the event notification endpoint (or disable Event Subscriptions entirely) from Features → Access on your app in the Zoom App Marketplace. Re-enable notifications by creating a new subscription with the steps above.
Need help getting started? Join us in the community.