TL;DR: N8n Automation Rate Limit Exceeded — most cases trace to a config mismatch, a hidden assumption, or a step skipped during setup. The fix path below covers the high-percentage causes first. If you're still stuck after 10 minutes, text PJ — most issues answered in one reply. 858-461-8054.
Operator Problem Guide
N8n Automation Rate Limit Exceeded
n8n workflows hit rate limits in 2026 when they make too many API calls in too short a time — either from a single high-volume workflow processing thousands of items in parallel, or from multiple workflows all hitting the same API at once. The error manifests as 429 responses in the failed node.
Why This Happens
Configuration gaps between tools or services
Missing integrations or manual workarounds that weren't designed to scale
Changes in vendor behavior, pricing, or API that weren't communicated clearly
What To Check First
Verify your current setup matches the vendor's latest documentation
Look for recent changes — platform updates, new team members, configuration drift
Check if the problem is consistent or intermittent (different root causes, different fixes)
When To Escalate
The problem is costing you money or customers per week
You've spent more than 2 hours on it without progress
A vendor quoted you more than $500 and you're not sure if it's necessary
Dealing with this right now?
The fix: add a Wait node between batches of API calls with a 1–2 second delay. For parallel processing, limit the concurrency in the SplitInBatches node — set "Batch Size" to a value that keeps your API call rate below the service's limit. For workflows that process items one at a time in a loop, add `{{ $json.i * 200 }}` milliseconds of wait time based on the item index to spread calls over time. If you are hitting Claude's API limits, check your usage tier in console.anthropic.com — upgrading your tier increases rate limits.
