Phil Leggetter # How to Solve Make.com Webhook Rate Limit Errors Published May 30, 2025 · Updated Feb 9, 2026 * * * If you're using Make.com to receive webhooks from external platforms, you might encounter rate limit errors—especially during traffic spikes. This article explains why those errors occur and how you can solve them using the Hookdeck Event Gateway. You may also be interested in our guide on [how to reduce Make.com credit usage](/content/webhooks/platforms/how-to-reduce-make-com-credit-usage/index.html). ## The Problems [\#](/content/webhooks/platforms/how-to-solve-make-com-webhook-rate-limit-errors\#the-problems/index.html) Make.com allows you to create **custom webhook URLs** to trigger automations. However, these endpoints aren't designed for high-throughput or bursty traffic. When too many requests hit your Make webhook in a short time, Make will: - Respond with **HTTP 429 Too Many Requests**. This happens if you hit the rate limit for your Make plan. By default this is 30 webhooks per second. - Respond with **HTTP 400 "Queue is full."** This can happen if your Make Scenario [Connection](https://help.make.com/connect-an-application) fails to process a queued action. By default the queue size is 50. Make's webhook restrictions are explicitly noted in [Make's webhook documentation](https://help.make.com/webhooks#qcNsr), which cautions against high-frequency webhook traffic. Because webhook requests originate from external platforms (like Stripe, GitHub, or Iterable), Make **cannot retry** the request. Once rejected, the event is lost unless the **sending platform** is configured to retry on 429 responses. This puts the burden on the **webhook sender** to manage retries and rate adjustments—which may not always be configurable or reliable. ## The Solution: Hookdeck Event Gateway as a Serverless Webhook Queue [\#](/content/webhooks/platforms/how-to-solve-make-com-webhook-rate-limit-errors\#the-solution-hookdeck-event-gateway-as-a-serverless-webhook-queue/index.html) The Hookdeck Event Gateway sits between the webhook provider and Make.com, acting as a buffer, queue, and traffic controller. It ensures Make only receives traffic it can handle. ### Benefits [\#](/content/webhooks/platforms/how-to-solve-make-com-webhook-rate-limit-errors\#benefits/index.html) - **Guaranteed Webhook Ingestions**: The Event Gateway ensures that all webhook events are captured and processed, even if Make.com is temporarily overwhelmed. - **Rate Limiting**: Smooths out traffic spikes to avoid triggering Make 429 errors. - **Queueing**: Events are stored and released at a safe pace. - **Retries**: If Make becomes temporarily unavailable, Event Gateway will automatically retry delivery. - **Visibility**: Inspect and monitor webhook traffic through the Event Gateway's dashboard. ## How to Use Hookdeck Event Gateway as a Serverless Webhook Queue [\#](/content/webhooks/platforms/how-to-solve-make-com-webhook-rate-limit-errors\#how-to-use-hookdeck-event-gateway-as-a-serverless-webhook-queue/index.html) 1. **Get your Make.com webhook URL** Use the “Custom Webhook” module in your scenario and copy the generated URL. 2. **Create a Hookdeck Event Gateway Connection** An Event Gateway [Connection](/content/docs/connections/index.html) consists of: - [Source](/content/docs/sources/index.html) : your webhook provider (e.g., Stripe, Iterable) - [Destination](/content/docs/destinations/index.html) : the Make.com custom webhook URL Follow the [create a connection docs](/content/docs/connections#create-a-connection/index.html) for more details. 3. **Configure Delivery Rate Limiting** - Go to your destination settings in the [Event Gateway dashboard](https://dashboard.hookdeck.com/connections). - Enable **Max Delivery Rate** and set a limit for the Make webhook end point below the rate limit of your Make plan and based the limits of the Make Connection target. The Make webhook rate limit is 30, but your Make Connection may have a lower limit, so set the rate limit lower to be safe. 4. **Test Your Workflow** - Send some test events from your source platform - Watch how the Event Gateway queues and dispatches them to Make, avoiding overload As an example, you can use the following JSON data and JavaScript script to simulate sending movie data to your Make.com webhook URL. This file contains a list of movies with their details, which you can use in your Event Gateway and Make setup. The script will send the events as quickly as it can to the Hookdeck Event Gateway with no rate limiting, so you can see how Event Gateway handles the traffic and ensures that Make.com receives the events without hitting rate limits. movies.json ```json [\ {\ "title": "The Shawshank Redemption",\ "year": 1994,\ "genre": "Drama",\ "director": "Frank Darabont",\ "rating": 9.3\ },\ {\ "title": "The Godfather",\ "year": 1972,\ "genre": "Crime",\ "director": "Francis Ford Coppola",\ "rating": 9.2\ },\ {\ "title": "The Dark Knight",\ "year": 2008,\ "genre": "Action",\ "director": "Christopher Nolan",\ "rating": 9.0\ },\ ... ] ``` The output of running this script will look similar to this: ``` ... Successfully sent: To Kill a Mockingbird { status: 'SUCCESS', message: 'Request handled by Hookdeck. Check your dashboard to inspect the request: https://dashboard.hookdeck.com/requests/req_ZTZquKcu4rIebuahSBgg', request_id: 'req_ZTZquKcu4rIebuahSBgg' } Successfully sent: L.A. Confidential { status: 'SUCCESS', message: 'Request handled by Hookdeck. Check your dashboard to inspect the request: https://dashboard.hookdeck.com/requests/req_g6iHyCvkZO2E29NNdk4F', request_id: 'req_g6iHyCvkZO2E29NNdk4F' } ... ``` ## Optional: Add Filtering or Transformation [\#](/content/webhooks/platforms/how-to-solve-make-com-webhook-rate-limit-errors\#optional-add-filtering-or-transformation/index.html) The Event Gateway can help tailor the webhook payload before it hits Make: - [Filter](/content/docs/filters/index.html) only relevant events (e.g., only movies with a rating above 8.5). You can also your filters to route events to different destinations based on criteria like event type or content. - [Transform](/content/docs/transformations/index.html) the JSON body to match what your Make scenario expects. ## Common Platforms That Send Webhooks to Make.com [\#](/content/webhooks/platforms/how-to-solve-make-com-webhook-rate-limit-errors\#common-platforms-that-send-webhooks-to-makecom/index.html) Make.com users frequently connect the platform with these webhook sources to trigger automations across categories like e-commerce, communication, forms, and DevOps: ### E-Commerce & Payments [\#](/content/webhooks/platforms/how-to-solve-make-com-webhook-rate-limit-errors\#e-commerce--payments/index.html) - **Shopify** - Order creation, fulfillment, and inventory updates - **Stripe** - Payment success, refunds, and subscription changes ### Messaging & Notifications [\#](/content/webhooks/platforms/how-to-solve-make-com-webhook-rate-limit-errors\#messaging--notifications/index.html) - **Slack** - Event-based notifications and message automation - **Discord** - Trigger actions from server or channel events - **ManyChat** - Chatbot interactions forwarded to Make - **Paubox** - Secure email notifications and alerts ### Email & Communication [\#](/content/webhooks/platforms/how-to-solve-make-com-webhook-rate-limit-errors\#email--communication/index.html) - **Gmail** - Send webhook-triggered email notifications - **Facebook Lead Ads** - Capture form data for automated lead flows - **Facebook Pages** - Automate content and updates ### Forms & Surveys [\#](/content/webhooks/platforms/how-to-solve-make-com-webhook-rate-limit-errors\#forms--surveys/index.html) - **Google Forms**, **Typeform**, **JotForm**, **Gravity Forms** - Submit responses that trigger Make flows ### Spreadsheets & Databases [\#](/content/webhooks/platforms/how-to-solve-make-com-webhook-rate-limit-errors\#spreadsheets--databases/index.html) - **Google Sheets** - Add or update rows from webhook data - **Airtable** - Send record data to Make or sync across tools ### Cloud Storage & Docs [\#](/content/webhooks/platforms/how-to-solve-make-com-webhook-rate-limit-errors\#cloud-storage--docs/index.html) - **Google Drive** - Access, manage, or sync documents - **Notion** - Update databases or content via webhooks ### AI & Automation [\#](/content/webhooks/platforms/how-to-solve-make-com-webhook-rate-limit-errors\#ai--automation/index.html) - **OpenAI (ChatGPT, DALL·E)** - Trigger prompts or image generation - **Zapier** - Extend integration with other apps via webhook bridges ### Additional Resources [\#](/content/webhooks/platforms/how-to-solve-make-com-webhook-rate-limit-errors\#additional-resources/index.html) For more in-depth strategies on handling rate limit errors in Make.com, consider exploring the following resources: - [Fixing Rate Limit Errors - Make Help Center](https://help.make.com/fixing-rate-limit-errors): Offers guidance on customizing error handling, including using the Sleep module and Break error handler to manage 429 errors. - [Make Community Discussion on Error 429](https://community.make.com/t/error-429-or-rate-limit-error/36445): Community insights and shared experiences in dealing with rate limit issues. ## Conclusion [\#](/content/webhooks/platforms/how-to-solve-make-com-webhook-rate-limit-errors\#conclusion/index.html) Make.com is great for connecting APIs and automating workflows—but it’s not built to absorb bursts of webhook traffic. The Event Gateway solves that gap by acting as a serverless queue: rate-limiting, queueing, and retrying on your behalf. With the Hookdeck Event Gateway in place, your Make scenarios can run smoothly, even when webhook traffic spikes. * * * Phil Leggetter Head of Developer and Agentic Experiences Phil is Head of Developer and Agentic Experiences at Hookdeck with expertise in real-time communications technologies, and creator of the AAARRRP Developer Relations strategy framework.