n8n now offers public API rate limits that keep every team on your instance running.
n8n 2.47.0 introduces per-key public API rate limits for all plans on n8n Cloud and self-hosted. Admins can set read and write ceilings globally or per endpoint, enable them via settings, API, or environment variables, and rely on Redis in multi-main setups. Over-limit requests receive 429 responses with Retry-After and rate-limit headers, helping clients back off safely. Combined with idempotency keys, the feature prevents runaway workflows from overwhelming shared instances, while batching in the n8n and HTTP Request nodes keeps automated workflows within limits.
Key Takeaways
- n8n 2.47.0 introduces per-key public API rate limits across all plans, helping prevent runaway workflows from overwhelming shared instances.
- Admins can enable and configure separate read/write limits globally or per endpoint via the settings page, API, or environment variables, with 429 responses and retry guidance headers.
- API clients should follow rate-limit headers by respecting Retry-After, adding jitter, and monitoring remaining quota, while workflows should use batching to avoid per-item API calls.
- Only requests using an API key against /api/v1 count toward limits; editor traffic is excluded, and each key has its own counter within the same configured limits.
- Idempotency keys, available since n8n 2.45.0, make retries after rate limits safe by preventing duplicate POST requests and returning stored responses for retries.
Meta description: n8n 2.47.0 adds per-key public API rate limits and idempotency keys, helping teams cap runaway workflows and protect shared n8n instances now.
Tags: n8n, API rate limiting, automation workflows, public API, idempotency keys
n8n public API rate limits arrived in n8n 2.47.0, and they are available on every plan across n8n Cloud and self-hosted. The feature lets admins cap how many requests each API key can send to an instance, so a runaway workflow hits its own key limit instead of blocking other teams. It also works alongside idempotency keys, available since n8n 2.45.0, so clients can learn when to slow down and when a retry is safe.
Why per-key limits matter
Shared n8n instances turn the public API into a common dependency. API clients from different teams call it, and workflows can call the same instance's API through the n8n node or the HTTP Request node. Because a node runs once for each item, a list of 1,000 items can create about 1,000 requests in a short time.
Without per-key controls, one busy workflow can affect everyone else on the instance. Some customers had been building their own rate limiters around n8n to reduce that risk. The new limits put that protection inside n8n. Each team can continue building, while the instance is less likely to be overwhelmed when one workflow runs away.
How admins can configure and enable limits
Rate limits set a ceiling on traffic from each API key. A client that sends too much traffic reaches its own limit rather than blocking other keys. Admins decide what traffic is acceptable, with separate limits for reads and writes. Those limits can apply across all endpoints or per endpoint, which makes it possible to set a tighter ceiling for writes than for reads. Each API key keeps its own count within those rules.
When a key reaches a limit, n8n answers with a 429 response. That response includes Retry-After and rate-limit headers, so clients can see when to retry and how many requests remain. Limits begin with default values, and changes made in the settings page or through the API apply immediately without a restart. In multi-main setups, every main shares one count per API key through Redis, so a key that reaches its limit receives a 429 from every main until the window ends.
Rate limiting is off by default. Admins can enable it in three ways, depending on how they run n8n. In the settings page, go to Settings > Policies > Public API Limits, turn on Enable API key rate limits, adjust the limits and windows, and select Enable limits. Through the public API, use GET /api/v1/settings/rate-limits to read current settings and PUT /api/v1/settings/rate-limits to replace them. The API key used for these requests needs the securitySettings:manage scope. On self-hosted instances, set N8N_PUBLIC_API_RATE_LIMIT_ENABLED to true and restart n8n, then use the N8N_PUBLIC_API_RATE_LIMIT_* variables to change individual limits and windows. An environment variable overrides settings made through the settings page or API, and the settings page shows the affected field as locked until the variable is changed and n8n is restarted.
How clients and workflows stay under limits
API clients can use the rate-limit headers to avoid hitting ceilings. Four habits help them stay within limits: wait for the number of seconds in Retry-After before retrying; add a small random delay of up to 5 seconds so retries from different clients spread out; watch X-RateLimit-Remaining and slow down as it approaches 0 until the time in X-RateLimit-Reset; and spread large jobs out by sending requests at a steady rate across the window.
Workflows that call the API of their own instance need one extra step. The n8n node and the HTTP Request node send one request per item and fail on a 429, so a large list can reach a limit quickly. Add Batching to the node, using Request Options for the n8n node and Options for the HTTP Request node, then set Items per Batch and Batch Interval (ms). Sending five items each second produces 300 requests a minute, which is below every default limit. Batching is a better fit here than Retry On Fail, because Retry On Fail waits at most 5 seconds between tries and often retries inside the same window.
Only requests that use an API key at /api/v1 count toward the limits. Requests from the n8n editor do not count. Each API key has its own count, but every key works within the same limits. To give one integration more headroom, run it on a separate n8n instance. Changing a limit while requests are in progress applies the new limit immediately; if the new limit is lower than an API key's current count, that key's next request gets a 429, and the count resets when the window ends.
To turn off one type of limit, set that limit to 0. Reads or writes can be disabled globally or per endpoint while other limits remain active. When rate limiting is enabled, at least one limit must be more than 0.
Why idempotency keys matter
Rate limits mean clients may sometimes receive a 429 and need to try again. Retrying a POST request carries a risk: if the first request already succeeded, the retry could create a duplicate. Idempotency keys make those retries safe, so clients can back off after a 429 and try again with confidence.
Send an Idempotency-Key header with a public API POST request. If the request succeeds, n8n stores the response for 12 hours, and a retry with the same key and body receives that stored response instead of running the POST again. If the first request fails, n8n releases the key, so the retry runs normally. The API idempotency documentation covers the key format and the responses for conflicting or in-progress requests.
What to do next
Update to n8n 2.47.0 or later, turn on rate limits in Settings > Policies > Public API Limits, and check the API rate limits documentation for the full configuration reference. If clients send POST requests, add idempotency keys at the same time using the API idempotency documentation.
Featured image: Abstract friendly illustration showing n8n workflow nodes, API keys, and a rate-limit dial, with no people, logos, or text.

Comments (0)