New in n8n: Public API rate limits that keep every team on your instance running
Blog post from n8n
n8n 2.47.0 introduces configurable public API rate limiting for all Cloud and self-hosted plans, enabling administrators to cap requests per API key and prevent high-volume or runaway workflows from disrupting other teams sharing an instance. Limits can be configured separately for reads and writes, globally or by endpoint, with clients receiving 429 responses and headers such as Retry-After and X-RateLimit-Remaining to guide backoff behavior; multi-main deployments share counters through Redis. Rate limiting is disabled by default and can be enabled through the settings interface, public API, or self-hosted environment variables, with environment settings taking precedence. Clients should distribute large workloads, monitor rate-limit headers, and add randomized retry delays, while n8n workflows calling their own instance should use batching because nodes issue one request per item. The feature complements idempotency keys, introduced in version 2.45.0, which store successful POST responses for 12 hours so retried requests with the same key and body do not create duplicates.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.