N8n HTTP Request Failing Due to Rate Limits – Possible Solutions?

Questions
1

Describe the problem/error/question

I encountered a rate-limiting issue while working with n8n. The first HTTP module request works fine, but when I attempt a second request to fetch the list of categories, it fails with a “too many requests” error. Interestingly, the same workflow works perfectly in Make.com.

Here’s the error message I received:

What is the error message (if any)?

{
  "errorMessage": "The service is receiving too many requests from you [item 51]",
  "errorDescription": "Try spacing your requests out using the batching settings under 'Options'",
  "errorDetails": {
    "rawErrorMessage": [
      "Try spacing your requests out using the batching settings under 'Options'"
    ],
    "httpCode": "429"
  },
  "n8nDetails": {
    "nodeName": "HTTP Request1",
    "nodeType": "n8n-nodes-base.httpRequest",
    "nodeVersion": 4.2,
    "itemIndex": 51,
    "time": "2/28/2025, 1:28:25 PM",
    "n8nVersion": "1.79.2 (Cloud)",
    "binaryDataMode": "filesystem",
    "stackTrace": [
      "NodeApiError: The service is receiving too many requests from you",
      "    at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/HttpRequest/V3/HttpRequestV3.node.js:525:33)",
      "    at processTicksAndRejections (node:internal/process/task_queues:95:5)",
      "    at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:627:19)",
      "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:878:51",
      "    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/execution-engine/workflow-execute.js:1211:20"
    ]
  }
}

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Is there a way to get all inputs from the previous node only? ithink the {{$input.all()}} gets the output of all previous nodes.

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main): own
  • Running n8n via (Docker, npm, n8n cloud, desktop app): website - n8n cloud
  • Operating system: windows
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3
  • v1
  • N/A
  • Own
  • n8n cloud
  • Windows 10
4

@Janna.greenway I notice that in your workflow the Authorization token is the same for both API’s. Maybe double check the authorization for the failing API request against what you have in make.com?

If the services are separate then they would typically have different authorization tokens.

Sometimes an API will return “429 Too many requests” instead of “403 Unauthorized” when the authorization is wrong because the rate-limiting is based on the authorization token.

Also, have you tried the request using another HTTP client such as curl or postman to verify the headers that you’re passing to the API?

5

image
image437×835 34.8 KB

image
image354×699 7.5 KB

Yes, I was able to get the categories in Postman using the same authorization tokens. In n8n, the authorization is the same as in Make, which is working correctly. So the token itself doesn’t seem to be the issue.

Let me know if you have any other thoughts!

6

Hey @Janna.greenway, For your 429 error, try adding batching to the HTTP Request node (Options > Batching, e.g., 5 items, 1000ms) since Postman works but n8n’s hitting the API too fast—also, $input.all() only pulls from the last node, so check its output if data’s off.

7

@Janna.greenway Thank you for the context! Looking at inflow’s API documentation:

If you send too many API requests in a short time, the inFlow API will return HTTP status code 429 Too Many Requests.

If you encounter this limit, we encourage you to try to reduce the number of API calls required, or contact us for help if you are unable to do so.

Currently, the limit is set to 60 requests per minute but this is not yet finalized and may change.

I think @Yo_its_prakash is right, if it’s working in postman and make, then indeed n8n could be hitting the API too fast, or there’s duplicate calls. As their docs indicate that they accept 60 request per minute (1 request per second).

8

Thanks, @limecodesyan and @Yo_its_prakash! I appreciate the insights.

I’ve tried adding both batching (50 items, 1000ms batch interval) and a 1-minute delay step, but I’m still getting the same 429 error in n8n. The strange part is that in Make, I don’t have any wait or batching, and it still works fine without hitting rate limits.

image
image363×310 2.31 KB

image
image1097×293 21.2 KB

image
image1150×216 32.5 KB

9

@limecodesyan I appreciate the affirmation on my solution. but it seems even after batching there are quite few issues.

10

@Janna.greenway Could make the batch size as 2 just for debugging purpose

11

Thanks, @Yo_its_prakash and @limecodesyan! Yeah, even after batching (tried reducing it to 2 items per batch with a 1000ms interval), I’m still hitting the 429 error.

image
image981×1002 37.1 KB

12

Since you are in cloud version, many things in the background will be stopped by the cloud server settings (n8n T&C) they might have temp halted your requests for this particular workflow/operation, the best options you got are:

  1. Try after few Hours
  2. Add a proxy and try again

Most important thing:
what is the clients rate limit, and reset time perios

13

That’s a good point, @Yo_its_prakash. The funny thing is this is already the third brand-new workflow I’ve tried, and I tested it a few days ago too—same issue every time. So if n8n Cloud is temporarily blocking it, it seems like it’s not resetting properly for my account/workflow.

the client’s API allows 60 requests per minute (1 per second), and I’ve already tried spacing them out, but n8n still gets blocked while Make and Postman work fine.

Might be worth reaching out to n8n support to see if there’s a background restriction at play. Any thoughts?

14

@Janna.greenway It’s worth reaching out to Inflow Inventory’s support they may shed light on whether the request is actually being received as they would see the logs on their end. Or they could point to what’s not gelling with n8n’s server.

Another thing you could try to isolate the issue is try running this workflow on a self-hosted instance of n8n.

15

I was able to make it work by increasing the batch interval instead to 10000ms. Thank you so much for your help @limecodesyan and @Yo_its_prakash!

image
image1581×1047 99.4 KB

16

If this (The Batching with interval Comment) helped, please consider marking it as the solution.
Also i would like to add a proper time interval, the final minimal interval for this is:
Batching 1 per 1000ms

17

Thank you! marked it as a solution as well. Additional question if you guys have tried it, is there a way to get the $input.all() but for the 3 nodes back node?

18

Yes it is entirely possible, but responding here would deviate this discussion, and we might get marked for spam, can you create quick new question on that

19

will do. Thank you @Yo_its_prakash!