Make takes 300 webhook requests per 10 seconds: a Sume queue fits

Make's webhooks page states a limit of 300 incoming requests per 10 seconds, with 429 beyond it. A Sume bulk queue has at most 100 items and at most 16 children in flight, and each child sends one terminal webhook when it finishes, so a single queue cannot reach that rate from fresh deliveries alone. The two numbers that deserve more attention are Make's queue size and the retries Sume sends if Make answers with an error.

The numbers

The Make page also says the webhook queue holds 667 items per 10,000 credits, up to 10,000 items, answers 200 Accepted when it takes a request, 400 Queue is full when it cannot, and keeps logs for 3 days (30 days on Enterprise). Sume treats anything but a 2xx as a failed attempt.

Steps

Check the shape of your own load before you rely on the arithmetic.

• Count the webhooks you expect in a burst: one per item that carries a communication.webhook_url, per queue, per day.
• Compare against 300 per 10 seconds, and against your Make queue capacity if the scenario is slow.
• Keep the scenario fast, with a short first module and heavy work after the reply, so the queue drains.
• Save the Sume run id from each delivery in your own record, since Make's logs last only days.

What Sume does not do

Sume does not slow its deliveries to match a receiver. If Make answers 429 or 400, Sume counts a failed attempt and retries, using your Retry-After on a 429 or 503 when it is longer than its own backoff. The queue-size figure depends on your Make plan's credits, so read your own plan; we only quote the page.

Several queues at once add up, so three queues started in the same minute can deliver more than one queue would. Even then you would need hundreds of finishes inside ten seconds to touch the limit, which a concurrency window of 16 makes unlikely.

When the numbers do matter

The queue capacity is the figure that can surprise you. If your scenario is paused or slow and a day of deliveries arrives, the queue fills, Make answers 400, and Sume starts its retry schedule. After ten refused attempts the delivery status becomes exhausted, and the run is unchanged, so you can re-send each delivery by hand with the redeliver endpoint, which does not use one of the automatic attempts. Count your expected deliveries per day and compare with the queue capacity of your plan before the campaign starts.