Will a 100-item Sume bulk run hit Zapier's webhook rate limit?

No, on the numbers alone: a Sume bulk queue holds at most 100 items, so at most 100 run webhooks, against Zapier's stated 1,000 requests per 5 minutes per Zap on legacy webhook routes. The queue itself has no webhook, so each item that should reach Zapier carries its own communication.webhook_url.

Sume facts are from the Bulk runs docs; the Zapier limits were read 2026-09-30.

What are Zapier's limits?

Zapier's page lists 20,000 requests every 5 minutes per user and 1,000 requests every 5 minutes per Zap in legacy webhook routes. Exceeding them triggers a 429.

Does the queue send one webhook or many?

Many, one per item that set a communication.webhook_url. The queue object has no callback, so poll GET /v1/format-run-queues/{queue_id} for queue-level progress. A queue reading completed means every item is terminal, not that all succeeded; check counts.failed.

What does Sume do if Zapier answers 429?

Run webhooks retry up to 10 attempts with exponential backoff and honor Retry-After on 429 and 503. Zapier also says that at high activity it may return 200 and delay processing by several minutes, and Sume cannot see that delay, so keep a poll of the queue as your source of truth.

How do I keep the batch small anyway?

Use a fresh Idempotency-Key per batch, because replaying a spent key returns 202 with the old queue. Split lists past 100 items across queues instead of raising concurrency.