n8n · HTTP Request node
429 - The service is receiving too many requests from you
Short answer
This n8n HTTP Request error displays when the node receives a 429 from the service you are calling, which often means you have hit its rate limits. Use Batching. In the HTTP Request node, select Add Option > Batching, set Items per Batch, and set Batch Interval (ms) to add a delay between requests.
VerifiedLast verified
01Error text
429 - The service is receiving too many requests from you02Likely causes
- You have hit the rate limits of the service that you're calling.
03How to fix it
- Use Batching. In the HTTP Request node, select Add Option > Batching, set Items per Batch, and set Batch Interval (ms) to add a delay between requests.
- Or use Retry on Fail. In the node Settings, enable Retry on Fail, then set Max Tries and Wait Between Tries (ms).
04Official documentation
→Related errors
- Bad request - please check your parametersThis n8n HTTP Request error displays when the node receives a 400 error indicating a bad request. Review the API documentation for your service to format your query parameters.
- The resource you are requesting could not be foundThis n8n HTTP Request error displays when the endpoint URL you entered is invalid. Refer to your service's API documentation to verify you have a valid endpoint.
- Connection refused (ECONNREFUSED)ECONNREFUSED in the n8n HTTP Request node means the node reached a host but the target port has no listener, most often because of Docker networking on self-hosted n8n. Address the target by a name the container can route to, such as host.docker.internal or the Compose service name.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for n8n work:Open n8n jobsn8n rates and salaries