【The service is receiving too many requests from you】By using HTTP node to connect with Imgur

Questions
,
1

:jigsaw: Describe the problem / error

Hi everyone,

I’m currently using an HTTP Request node in n8n to upload images to Imgur using the public URL method. My setup follows the Imgur API documentation, using the POST method with image, type, title, and description fields.

However, when I execute the workflow, I consistently get this error:

The service is receiving too many requests from you. Try spacing your requests out using the batching settings under 'Options'.

I tried adjusting the batching settings as suggested:

  • Items per Batch: 1
  • Batch Interval (ms): 500000

But the error still persists.

To confirm that the API format is correct, I tested the exact same request in Postman with identical headers and body. It works fine there — the image uploads successfully and I get a public Imgur link.

So I believe the issue is not in the request structure, but in how n8n sends it (perhaps too quickly or too frequently?).

:hammer_and_wrench: My Setup

  • n8n version: 1.88.0
  • Environment: Docker
  • Operating System: Windows / MacOS
  • Target API: Imgur Upload

:bulb: What I’ve Tried

  • Using type=url with both public image URLs and S3 pre-signed URLs.
  • Adding a delay between executions using batching options.
  • Breaking down image handling into 3 Code nodes:
    1. Extract image URL from Notion data
    2. Convert to Imgur-ready format
    3. (Optional) Fetch binary if not using type=url
  • Directly replacing the image value with a hardcoded image URL in the HTTP node to isolate the issue — still failed in n8n, but succeeded in Postman.

:mag: Sample HTTP Node Configuration

:question: Questions

  1. Is this a known issue with how n8n handles rate limiting on Imgur’s API?
  2. Should I use a different method (e.g., send image as base64 instead of via url) to avoid this?
  3. Are there any other throttling strategies or recommended practices for Imgur uploads in n8n?
2

Hi @UniversalVinyl_IMS

Does the endpoint you use require authorization?

:link: Imgur API

3

Yes, I’m using the https://api.imgur.com/3/image endpoint with Authorization: Client-ID my_client_id in the headers.

The same setup works fine in Postman, so I think it’s not an authorization issue. Could it be how n8n handles timing or retries?

4

If it works in Postman, it should work in n8n.

I think you should start with a single request to make sure everything is configured correctly.