How to automate Zoom
Compare Zapier, Make, n8n, Power Automate, and Pipedream — automate Zoom with HubSpot. Pick the right tool, set it up, and ship.
Video · 1 integration
Automating Zoom typically means creating meetings on demand, syncing registrant data with CRMs or webinar platforms, and triggering follow-up workflows when meetings start or end. Teams automate it to eliminate manual scheduling, track attendance without logging into the dashboard, and connect meeting activity to tools like HubSpot or email sequences. The platform's webhook system and REST API make this technically possible, but several hard limits and recent authentication changes mean the choice of automation platform matters more than it might seem.
What it costs to automate Zoom
Platform pricing at different volumes. Annual billing shown.
| Platform | Free tier | 100 tasks/mo | 1K tasks/mo | 10K tasks/mo |
|---|---|---|---|---|
| Make | 1,000 credits/mo | Free | Free | $10.59/mo |
| n8n | Yes | $20/mo | $20/mo | $50/mo |
| Pipedream | 100 credits/mo | Free | $29/mo | $79/mo |
| Zapier | 100 tasks/mo | Free | $69/mo | $69+/mo |
| Power Automate | 750 runs/mo | Free | $15/mo | $15/mo |
Zoom integrations
Each page compares all five platforms for that pair.
Zoom triggers & actions by platform
Which capabilities each platform supports for Zoom.
| Capability | Pipedream | Zapier | Power Automate | Make | n8n |
|---|---|---|---|---|---|
| Triggers | |||||
| New Zoom meeting | ✓ | ✓ | — | — | — |
| HubSpot Trigger | — | — | — | — | ✓ |
| New meeting summary | — | ✓ | — | — | — |
| New participant | — | ✓ | — | — | — |
| New recording | ✓ | — | — | — | — |
| New registrant | — | ✓ | — | — | — |
| New summary | ✓ | — | — | — | — |
| New webinar registrant | — | ✓ | — | — | — |
| New Zoom recording | — | ✓ | — | — | — |
| Watch meeting summaries | — | — | — | ✓ | — |
| Watch Zoom meetings | — | — | — | ✓ | — |
| When a HubSpot contact is created | — | — | ✓ | — | — |
| Zoom webhook (HTTP trigger) | — | — | ✓ | — | — |
| Zoom webhook (meeting.ended, recording.completed) | — | — | — | — | ✓ |
| Actions | |||||
| Create engagement | ✓ | ✓ | ✓ | ✓ | ✓ |
| Create deal | ✓ | ✓ | ✓ | ✓ | — |
| HubSpot Create contact | ✓ | — | ✓ | — | ✓ |
| Add to HubSpot workflow | — | ✓ | — | — | — |
| Create/update contact | — | — | — | ✓ | — |
| Create/update HubSpot contact | — | ✓ | — | — | — |
| Update deal | — | — | — | — | ✓ |
Things to know about automating Zoom
Meeting Creation Has a Hard Daily Cap
The Create a Meeting API is limited to 100 requests per day per user — not a soft throttle, a hard stop. Any workflow that programmatically schedules meetings at volume will hit this ceiling quickly, and there is no burst allowance.
JWT Auth Is Completely Dead
Zoom disabled JWT app authorization entirely on September 1, 2023. Any existing integration still using JWT credentials will fail silently or throw auth errors — the current required standard is Server-to-Server OAuth, which issues tokens valid for only 1 hour before requiring a refresh.
Webhook Validation Breaks Zapier and Make
Since Zoom mandated Challenge Response Check (CRC) validation for all webhooks in February 2024, it is not possible to complete that handshake through Zapier or Make — Zap webhooks don't allow you to control the HTTP response body Zoom requires. Pipedream is the most commonly cited workaround because it gives you full control over the response.
Rate Limits Are Shared Across Your Entire Account
Zoom enforces API rate limits at the account level, not the user or app level. If you have 10 users or multiple apps drawing from the same account, they all share the same daily quota — a spike from one workflow can exhaust the budget for everything else simultaneously.
Webhook Reliability Is Not Guaranteed
Zoom retries failed webhook deliveries only 3 times — at 5 minutes, 25 minutes, and 85 minutes after the original attempt — and stops completely if your endpoint never acknowledges with a 200 or 204 within 3 seconds. At high volume, participant join and leave events are known to fire inconsistently or not at all for some meetings.
Scope Requirements Create Security Trade-offs
Getting full automation access requires scopes like meeting:write:admin and user:write:admin, which demand administrator-level 'View and Edit Users' permissions across the account. Organizations that only need meeting-level access often find this an uncomfortable security compromise with no narrower alternative.
What breaks at scale
The Zoom Create a Meeting API enforces a hard limit of 100 calls per day per user, and this is an account-wide shared counter. Once you hit it, every subsequent meeting creation attempt returns an error for the rest of the 24-hour window — there is no queue, no overflow, and no way to burst through it. Teams that route all programmatic scheduling through a single API user, which is common in multi-user automation setups, will exhaust this in hours during busy periods. The fix requires distributing meeting creation across multiple licensed users, each with their own 100-call daily budget.
Zoom's webhook system has a known and documented reliability problem with participant events: meeting.participant_joined and meeting.participant_left events do not fire consistently across all meetings, and there is no way to detect this failure from the receiving end. Combined with the 3-second acknowledgment window and only 3 retry attempts before Zoom permanently stops sending events to your endpoint, any workflow that depends on real-time attendance data will silently produce incomplete records. If your endpoint slows down under load and misses that 3-second window, Zoom doesn't alert you — it simply stops delivering, with no recovery path after the final retry.
Zoom has changed API limits without updating documentation or notifying developers, and this has caused production outages. Teams running 60 batch registration calls per day have found their integrations suddenly broken after an unannounced change dropped the Batch Registration limit to 3 requests per registrant per day. Zoom support initially denied anything had changed, meaning teams spent significant debugging time before confirming the change was real. Any automation relying on Zoom's documented rate limits in a production environment should build in monitoring for HTTP 429 responses and treat unexpected failures as a signal to re-verify current limits, not just retry.
Frequently asked questions
Can you automate Zoom with Zapier, Make, or n8n?
All five major platforms — Zapier, Make, n8n, Power Automate, and Pipedream — offer Zoom integrations, but they vary significantly in what they can actually handle. Zapier and Make both have a documented blocker: they cannot complete Zoom's mandatory webhook Challenge Response Check, which means inbound Zoom webhook triggers don't work reliably on those platforms. Pipedream and n8n give you lower-level HTTP control that makes CRC validation possible, and Power Automate handles Zoom primarily through its connector ecosystem with some limitations on webhook-based triggers.
What are the Zoom API rate limits for automations?
Zoom's rate limits depend on API complexity tier and account level: Light APIs allow up to 80 requests per second, Medium APIs up to 60 req/sec, and Heavy or Resource-Intensive APIs drop to 20–40 req/sec plus a 60,000 requests per day cap. The most impactful hard limit for automation is the Create a Meeting endpoint, which is capped at 100 requests per day per user regardless of account tier. These limits are enforced account-wide and shared across all apps and users on the same Zoom account.
Why are my Zoom webhooks not working in Zapier or Make?
The most common cause is Zoom's mandatory webhook validation requirement, introduced in February 2024, which requires your endpoint to respond to a CRC token challenge with a specific encrypted response body. Zapier does not allow you to control the HTTP response returned by its webhook listener, so the CRC handshake cannot be completed. Make has the same limitation. The recommended workaround from the developer community is to route Zoom webhooks through Pipedream, which lets you write custom response logic, or through n8n if you're self-hosting with full HTTP control.
How do I automate Zoom meeting registration with HubSpot?
The typical pattern is to trigger a Zoom meeting or webinar registration when a HubSpot contact reaches a specific lifecycle stage or form submission, using the Zoom Create Meeting Registration or Add Webinar Registrant API. Zapier and Make have pre-built HubSpot-to-Zoom templates that cover basic registration sync, but they are limited by Zoom's batch registration cap of 3 requests per registrant per day and the 100 meeting creation calls per day ceiling. For higher-volume webinar workflows, n8n or Pipedream give more control over retry logic and error handling when those limits are hit.