What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A 429 error in an n8n workflow usually means the external service called by a node has rejected a request because of its rate limit. Check the failed node’s response and the provider’s rules, then pace requests, configure retries, and reduce unnecessary calls. The right delay and batch size depend on that provider’s limits; there is no universal setting.
What a 429 error means in n8n
When an outbound HTTP Request node receives a 429, the service it called returned that status. n8n’s documentation describes the condition as “429 – The service is receiving too many requests from you.” As n8n puts it, “When an n8n node hits a rate limit, it errors.” A 429 is not, by itself, evidence that n8n imposed the limit.
![Computer Networking Bible: [3 in 1] The Complete Crash Course to Effectively Design, Implement and Manage Networks. Including Sections on Security, Performance and Scalability](https://m.media-amazon.com/images/I/41H4YJnxKgL._SL160_.jpg)
As an Amazon Associate I earn from qualifying purchases.
The provider decides what counts as too many requests. Limits can vary by account, endpoint, operation, or time window, so check the service’s API documentation for the quota that applies to your call. See n8n’s HTTP Request node common issues and rate-limit guidance.
Free tools Windows power users keep installed
One-click scans. No signup required.
How to diagnose the failing request
- Open the failed execution and inspect the node output. Note the endpoint, operation, error message, and any response body or headers available there.
- Confirm that the failing node is making an outbound request to the service that returned the 429. An inbound request to an n8n webhook is a different problem.
- Check the provider’s documentation for the applicable quota, its time window, and whether it limits requests by account, endpoint, concurrency, or another scope.
- Compare the limit with the workflow’s request pattern: how many items trigger calls, whether calls run close together, and whether concurrent executions add more requests.
Do not infer a provider’s exact quota from the status code alone. The response identifies a rate-limit rejection, but the provider’s documentation defines the relevant limits.
#1 Best Overall
How to prevent request bursts
Use HTTP Request batching
In the HTTP Request node, select Add Option > Batching, then configure Items per Batch and Batch Interval (ms). The interval pauses between batches, helping to spread calls across time when input items would otherwise trigger a burst. Set both values to fit the provider’s documented rules.
n8n’s documentation gives 1000 ms as an example interval for a service that permits one request per second. That is an illustration, not a generally safe setting: your provider may use a different limit or enforce additional daily or concurrency caps. See n8n’s rate-limit guidance.
Use Loop Over Items with Wait
If batching is unavailable for the node or you need an explicit workflow-level pause, place Loop Over Items before the API call and Wait after it, then connect the wait back to the loop. Choose the chunk size and wait duration using the provider’s actual limits. This makes the pacing visible in the workflow, but does not determine the provider’s quota for you.
How to configure retries
Retries can help when a failure is temporary, but they do not slow the workflow’s initial request stream. Pair them with batching or pacing if many items are generating calls faster than the provider allows.
- Open the node’s Settings.
- Enable Retry On Fail.
- Set Max Tries and Wait Between Tries (ms) to values appropriate for the provider’s limit and the workflow’s needs.
n8n recommends a wait longer than the rate-limit interval for rate-limit recovery. Its one-request-per-second example uses a 1000 ms delay; that is an example, not a universal threshold. A wait that is too short may simply trigger another rejection. Retries also do not guarantee success: if attempts are exhausted, handle the remaining failure explicitly rather than treating it as a successful run. See n8n’s HTTP Request node guidance.
What to do with a Retry-After header
Check the 429 response for Retry-After. RFC 9110 defines it as either an HTTP date or an integer delay in seconds; a server uses it to indicate how long a client ought to wait before making a follow-up request. See RFC 9110, section 10.2.3.
The documented Retry On Fail setting uses a configured wait in milliseconds. The cited n8n documentation does not say that this fixed delay automatically reads the response’s Retry-After value. If your workflow needs to honor that value dynamically, use a response-aware approach appropriate to the response format and verify its handling against the n8n version you run; do not assume the fixed-delay setting interprets the header.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsHow to reduce calls to the external API
If the workflow fetches one record per request, check whether the API supports retrieving a collection or filtered set in a single call. Where data freshness and the provider’s usage terms allow it, caching static external data and synchronizing that cache when the source changes can also reduce repeat requests. These options depend on what the API supports and how current the workflow’s data must be. n8n discusses them in its API rate-limiting guide.
Best Value
- Used Book in Good Condition
Which remedy fits the problem?
| Approach | What it changes | Best fit |
|---|---|---|
| Retry On Fail | Retries a failed request after a configured, fixed wait; does not pace the initial stream. | Transient failures, paired with pacing when the initial workload exceeds a limit. |
| HTTP Request batching | Groups input items and inserts a configured pause between batches. | Many input items trigger calls through the HTTP Request node. |
| Loop Over Items plus Wait | Creates a visible workflow-level loop and pause around a call. | You need explicit chunking and pacing around a node. |
| Response-aware Retry-After handling | Uses the provider’s stated wait, if the workflow can read and act on the response value. | The provider supplies a Retry-After value and a dynamic wait is needed; the fixed-delay retry setting is not documented as parsing it. |
| Call reduction or caching | Reduces how many outbound requests the workflow needs to make. | The API supports collection or filtered retrieval, or the data can be cached without violating freshness needs or usage terms. |
| API gateway or WAF | Controls requests arriving at n8n, rather than requests n8n sends to an external API. | Public inbound webhook traffic needs rate limiting. |
When the traffic is hitting an n8n webhook
An inbound webhook receives requests from other systems; it is not the same as an n8n node receiving a 429 from an external API. For public webhook traffic that needs rate limiting, n8n’s September 18, 2026 guidance says the platform does not provide built-in inbound rate limiting and recommends placing a dedicated API gateway or web application firewall (WAF) in front of n8n. See n8n’s API rate-limiting guide.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
