How can I resolve the "RateLimit: Rate limit hit" error when publishing my Webflow site using Make (formerly Integromat) for automations with the CMS, specifically with a Webflow form triggering a ChatGPT response logged in the CMS?
TL;DR
- Add delays between key steps in your Make scenario to prevent exceeding Webflow’s 60-requests-per-minute-per-site limit.
- Use throttling, batching, and logging to reduce redundant API calls and monitor execution frequency to avoid overwhelming the system.
The “RateLimit: Rate limit hit” error occurs when you're sending too many API requests to Webflow too quickly. This often happens when automating tasks using Make (formerly Integromat), especially with flows involving form submissions, GPT responses, and CMS item creation.
1. Understand Webflow API Rate Limits
- Webflow imposes per-site API rate limits to avoid overloading their servers. As of now:
- 60 requests per minute per site per token.
- Exceeding this threshold triggers the “RateLimit: Rate limit hit” error.
- Batch operations, form-heavy automations, or multiple parallel scenarios can easily exceed the limit.
2. Add Delays or Rate Limit Controls in Make
- In your Make scenario, insert a "Sleep" or "Delay" module after key steps (e.g., after the GPT call or before CMS item creation).
- Even a 1-2 second delay between CMS operations can reduce burst traffic.
- If processing many form submissions, use Make’s iterator + aggregator plus throttling to handle them more slowly.
3. Avoid Unnecessary API Requests
- Ensure you’re not making redundant calls (e.g., repeatedly creating CMS items or updating the same item multiple times in one run).
- In Make, log incoming data first and confirm it’s different before sending write operations to Webflow CMS.
4. Use Webhooks Efficiently
- If your form submission triggers a webhook:
- Make sure only relevant data is sent, and avoid triggering multiple overlapping scenarios at once.
- Consider using a router module in Make to manage operational flow more efficiently.
5. Monitor Execution Frequency and Load
- In your Make dashboard:
- Review the Scenario Run History to identify how often it's triggered.
- Consider changing the trigger or adding conditional filters to reduce execution frequency.
6. Consider Webflow CMS Limits
- Webflow also has CMS item limits (max items per collection, daily operations, etc.).
- If Make tries to push data even when a limit is near, errors (not just rate-related) may also surface.
Summary
To fix the “RateLimit: Rate limit hit” error when using Make with Webflow CMS and ChatGPT:
- Add delays between CMS operations within your Make scenario.
- Throttle and batch processed inputs to stay under Webflow’s 60-requests-per-minute limit.
- Avoid redundant calls, log efficiently, and monitor load to keep your automation stable and error-free.