Hi all. New here. Like what I’ve seen of n8n so far.
I am running into this issue - I’m getting a 429 error. The API I’m calling returns saying that I exceeded 200 requests per hour. However, I have only done maybe 10 at best, while connecting it to n8n and running test GETs.
How can this be explained? Does n8n hit this API multiple times on each request?
Thank you
A
Describe the issue/error/question
What is the error message (if any)?
Please share the workflow
(Select the nodes and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow respectively)
Share the output returned by the last node
Information on your n8n setup
n8n version:
Database you’re using (default: SQLite):
Running n8n with the execution process [own(default), main]:
Running n8n via [Docker, npm, n8n.cloud, desktop app]:
As the question is very generic and does not disclose important information like the Service or what exactly is done, I can sadly not give a very exact answer as it really depends on that. Some node actions will make a single request when they run, while others make multiple (as they, for example also have to collect information first or one has to be made for every item).
For example, will a “Get Many” of almost every node potentially make a lot of calls. After all, most APIs just return a limited number of results at a time. So if the API returns, for example, 100 entries max, and there are 20k entries, it has to make 200 calls.
Similar to a “Create”, not all APIs have batching support. So if 1k entries have to get created and it does not support batching, n8n will have to make at least 1k API calls.
I hope that is helpful
If you provide additional information, we can probably give you more insights and potentially help you with that problem.
I just switched my urlscan setting from private scans to public scans (limit 60 per minute), tried one scan and am told I have exceeded my limit (this was my first public scan)
Can you share the full page including the input items view along with the error? The API is not happy about something we need to be able to see everything to work it out.
Can you also confirm the n8n version you are using and how you are running it as you missed that from the template.