Daily limits

The cap

100 create or update calls, per Zoom user, per day. It resets at midnight UTC — not at midnight where you are, which matters if your working day straddles that line.

Two things about it surprise people.

An update spends the same allowance as a creation. The cap is not “100 meetings”; it is 100 calls that create or modify a meeting. A workflow that reschedules on every client reply can exhaust the day without creating a single new meeting.

It is per Zoom user, not per sub-account. Since one sub-account connects to one Zoom account, the two amount to the same thing in practice — but if several sub-accounts connect to the same Zoom login, they share one allowance and will exhaust it faster than any of them expects.

What spends it

Action	Spends
Create Meeting	yes
Update Meeting	yes
Create Webinar	yes
Update Webinar	yes
Get Meeting	no
Delete Meeting	no
Add Registrant, Get Registrant, Update Registrant Status	no
Update Attendance	no
Every trigger	no

Reads and registrant management are free. Only creating and modifying meetings counts.

Seeing what is left

The app’s settings page shows the day’s usage against the cap. That figure is counted from the app’s own records of what it has spent, which makes it a floor rather than an exact reading: a meeting created or edited directly in Zoom’s interface also spends allowance, and the app never sees it.

So treat the number as “at least this much used”. If your team also works in Zoom directly, the real figure is higher.

quotaRemaining is not this number

Create Meeting, Update Meeting, Create Webinar and Update Webinar all return a quotaRemaining output, and it reads exactly like the daily cap. It is not.

That field reports what Zoom’s rate-limit header said, and that header describes a rate-limit category window — Light, Medium or Heavy — which Zoom’s own reference states is separate from the 100-a-day limit. It has been observed returning 399, a number the cap cannot produce.

Zoom exposes no header for the real cap. A workflow branching on quotaRemaining to mean “am I about to run out of meetings” is branching on the wrong number.

It is kept and exposed because it is still the only live signal Zoom gives about throttling. Use it to detect being throttled, not to predict the daily cap.

-1 means Zoom sent no header on that call.

Staying under it

Do not reschedule on every change. The most common way to exhaust the allowance is a workflow that calls Update Meeting whenever an appointment record is touched, including changes that have nothing to do with the time. Condition the update on the start time having actually moved.

Do not update as a way of reading. Use Get Meeting, which is free.

Delete and recreate is two calls, one of which is free — deletion does not count, creation does. So cancelling and rebooking spends one, the same as an update. There is no allowance argument for preferring one over the other; prefer whichever leaves the client with the right emails.

Batch-created meetings are the risk case. A campaign that creates a meeting for every contact in a list will hit 100 quickly, and the 101st simply fails. Stagger it across days, or across Zoom accounts.

Watch for retry loops. A workflow that fails after Create Meeting and retries the whole branch spends allowance on each attempt.

What happens at the limit

Zoom refuses the call. The workflow step fails, and the run stops at that step.

The app surfaces the refusal with an error naming the cap rather than passing Zoom’s raw response through — the underlying message does not mention the daily limit and is close to unreadable without knowing what to look for.

Allowance returns at midnight UTC. There is no way to raise the cap from the app; it is a property of the Zoom plan.