Overview
This node acts as a webhook trigger for Zoom events. It listens for specific Zoom event notifications and starts an n8n workflow when such events occur. The node registers a webhook URL with Zoom to receive event callbacks, verifies incoming requests using either a token or a signing secret, and outputs the event data for further processing.
Common scenarios include automating workflows based on Zoom meetings or webinars, such as:
- Notifying a team when a meeting is created or ended.
- Logging participant join/leave events.
- Triggering follow-up actions after a webinar starts or ends.
- Processing recording completion events automatically.
For example, you could use this node to start a workflow that sends a Slack message whenever a new Zoom meeting is created or to update a CRM system when a webinar registration is cancelled.
Properties
| Name | Meaning |
|---|---|
| Event Type | Select the Zoom event to trigger the workflow. Options include meeting and webinar lifecycle events like created, started, ended, participant joined/left, registration created/cancelled, recording completed, etc. |
| Verification Token | The verification token from your Zoom Webhook configuration used to verify incoming webhook requests. This is a sensitive string. |
| Verification Method | Method to verify Zoom webhook requests. Can be either "Token" (simple token comparison) or "Signing Secret" (HMAC SHA256 signature verification). |
Output
The node outputs JSON data representing the Zoom event payload received via the webhook. The output structure includes at least two main fields:
event: A string indicating the type of Zoom event (e.g., "meeting.created", "webinar.started").payload: An object containing detailed information about the event, including metadata and specifics depending on the event type.
The output is provided as an array with one element per webhook call, suitable for downstream nodes to process.
No binary data output is produced by this node.
Dependencies
- Requires an OAuth2 API credential for Zoom with a valid access token to register and delete webhooks.
- Needs the Zoom webhook verification token or signing secret configured in Zoom's webhook settings.
- Uses the Node.js
cryptomodule internally for HMAC signature verification when using the signing secret method. - Requires network access to Zoom's API endpoints (
https://api.zoom.us/v2/webhooksandhttps://zoom.us/oauth/token).
Troubleshooting
- Unauthorized webhook calls: If the verification token or signature does not match, the node responds with HTTP 401 Unauthorized. Ensure the verification token or signing secret matches exactly what is configured in Zoom.
- Failed webhook registration: Errors during webhook registration usually indicate invalid or expired OAuth tokens. Refresh the OAuth credentials or reauthenticate.
- No valid access token found: The node requires a valid access token to register the webhook. Make sure OAuth credentials are set up correctly and tokens are refreshed as needed.
- Invalid signature errors: When using the signing secret method, ensure the secret is correct and that Zoom is sending the expected headers (
x-zm-signatureandx-zm-request-timestamp). - Webhook deletion errors on deactivate: These are logged but do not stop workflow deactivation. They typically happen if the webhook was already deleted or the token expired.