Overview
This node acts as a trigger for Zoom events, starting an n8n workflow whenever a specified Zoom event occurs. It is designed to listen for webhook notifications from Zoom, such as meetings or webinars being created, updated, started, ended, or participants joining/leaving. This node is useful for automating processes based on real-time Zoom activity, like logging meeting details, sending follow-up emails after a webinar ends, or updating CRM records when participants join.
Typical use cases include:
- Automatically capturing meeting or webinar lifecycle events.
- Triggering workflows on participant actions (join/leave).
- Handling recording completion notifications.
- Validating and securely receiving Zoom webhook calls.
Properties
| Name | Meaning |
|---|---|
| Event Type | The specific Zoom event that triggers the workflow. Options include various meeting and webinar events such as "Meeting Created", "Webinar Ended", "Recording Completed", etc. |
| Verification Token | A string token used to verify incoming webhook requests from Zoom, ensuring they are authentic. This token must match the one configured in the Zoom Webhook settings. |
| Verification Method | The method used 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: The type of Zoom event triggered (e.g., "meeting.created").payload: An object containing detailed information about the event, such as meeting or webinar details, participant info, timestamps, etc.
The output is provided as an array with a single JSON object per webhook call, suitable for further processing in the workflow.
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 manage webhooks.
- Needs the Zoom API to create and delete webhook subscriptions dynamically.
- Uses cryptographic functions (HMAC SHA256) for verifying webhook signatures if the "Signing Secret" verification method is selected.
- Requires proper configuration of the Zoom Webhook URL and verification token or signing secret in both Zoom and the node properties.
Troubleshooting
No valid access token found!
Occurs if the OAuth2 credentials do not contain a valid access token. Resolve by re-authenticating or refreshing the token.Failed to register Zoom webhook:
Indicates issues creating the webhook subscription on Zoom's side. Check network connectivity, API permissions, and validity of the access token.Unauthorized webhook call / Invalid signature:
Happens when incoming webhook requests fail verification. Ensure the verification token or signing secret matches exactly what is configured in Zoom's webhook settings and the node.Error deleting Zoom webhook subscription:
May occur during node deactivation if the webhook ID is invalid or the access token has expired. Verify credentials and webhook existence.No refresh token available!
If the node attempts to refresh tokens but none exist, reauthorize the OAuth2 credentials.