Original announcement: n8n · 2026-11-13. Read the official announcement.
Summary of the Update
On November 13, 2026, n8n announced a significant update to its workflow automation platform: the implementation of public API rate limits that control request volumes on a per-API key basis. This feature is designed to protect shared instances where multiple teams coexist, preventing excessive API usage by any one workflow or team from impacting others.
The rate limiting feature is available starting with version 2.47.0 across all supported plans and can be used in both n8n Cloud and self-hosted environments. It functions in tandem with idempotency keys, a capability introduced earlier, that make retrying API requests safe and idempotent.
Why This Matters for n8n Users
In scenarios where multiple teams or integrations share a single n8n instance, the public API can become overwhelmed if one workflow issues many requests rapidly. For example, a workflow processing a list of 1,000 items could send approximately 1,000 API calls in quick succession, potentially monopolizing instance resources.
Prior to this update, some users implemented custom rate limiters to handle these situations. Now, n8n provides built-in controls that let administrators cap public API usage per API key, helping ensure fair resource allocation and system stability.
Details of n8n’s Public API Rate Limits
- Configurable Limits: Admins can specify separate caps for read and write requests, adjustable globally and per endpoint.
- Per-API Key Counting: Each API key has independent tracking to avoid one team’s traffic affecting another.
- Clear Client Feedback: When limits are exceeded, clients receive HTTP 429 responses with
Retry-Afterand rate-limit headers, indicating when to retry and remaining allowances. - Immediate Effect: Rate limit settings apply instantly upon changes via the UI or API without requiring a restart.
- Multi-Main Support: In clustered, multi-main setups, request counts are shared via Redis, ensuring consistent enforcement.
Best Practices for Developers and Admins
To effectively use these new controls, developers and administrators should:
- Enable rate limiting from the settings panel, API, or environment variables depending on their deployment.
- Use idempotency keys on public API POST requests to safely retry without duplicating operations.
- Implement batching for workflows making many requests to the API, setting appropriate batch sizes and intervals to keep under limits.
- Monitor rate-limit headers in client responses to adjust request frequencies and avoid hitting caps.
Practical Checklist
- Update to n8n version 2.47.0 or later.
- Activate public API rate limits in Settings > Policies > Public API Limits or configure via API/environment variables.
- If applicable, update API clients to send idempotency keys with POST requests for safe retries.
- Configure workflow nodes that call the API (n8n node, HTTP Request node) to use batching with sensible batch sizes and intervals.
- Monitor usage and adjust rate limit settings as needed to balance performance and fairness.
Note: The official announcement does not specify default limit values, comprehensive configuration examples, or impacts on existing workflows aside from recommendations to use batching and idempotency keys.
Developers sharing an n8n instance with multiple teams will find these new controls especially valuable for maintaining operational stability and ensuring fair API access.


