Back to Nodes

HttpRequestThrottled

Last updated Oct 10, 2026

n8n community node with built-in HTTP request throttling (rate limiting)

12 Weekly Downloads
137 Monthly Downloads

Included Nodes

HttpRequestThrottled

Description

@bauer-group/n8n-nodes-http-throttled-request

![πŸš€ Release & NPM Publish](https://github.com/bauer-group/EXT-n8n-httpThrottled/actions/workflows/nodejs-release.yml)
![npm](https://www.npmjs.com/package/@bauer-group/n8n-nodes-http-throttled-request)
![GitHub package](https://github.com/bauer-group/EXT-n8n-httpThrottled/releases)

An n8n community node that adds intelligent rate-limit throttling to HTTP requests. It automatically detects rate-limit responses (HTTP 429, 503, 504) and waits the appropriate time before retrying, using information from response headers.

Features

  • Full V3 Feature Set β€” Inherits all parameters from the built-in HTTP Request node (50+ auth types, pagination, response format, proxy, SSL, etc.)
  • Automatic Rate Limit Detection β€” Detects HTTP 429, 503, and 504 status codes
  • Smart Wait Time Calculation β€” Parses Retry-After, X-RateLimit-*, and HubSpot-specific headers
  • Jitter Support β€” Prevents thundering herd with configurable random variance

Installation

n8n Community Nodes (Recommended)

1. Open your self-hosted n8n instance
2. Go to Settings β†’ Community Nodes
3. Enter @bauer-group/n8n-nodes-http-throttled-request
4. Click Install

The node appears immediately in the node panel β€” no restart required.

> Community Nodes are only available on self-hosted n8n instances.

Docker

Create a custom Dockerfile that pre-installs the package:

FROM n8nio/n8n:latest
USER root
RUN npm install -g @bauer-group/n8n-nodes-http-throttled-request
USER node

Then build and run:

docker build -t n8n-throttled .
docker run -it --rm -p 5678:5678 n8n-throttled

Or with docker-compose β€” replace image with build:

services:
  n8n:
    build: .
    ports:
      - "5678:5678"

Quick Start

1. Add the HTTP Request (Throttled) node to your workflow
2. Configure it exactly like the built-in HTTP Request node
3. Throttling is enabled by default β€” no extra setup needed
4. When the API returns 429, the node automatically waits and retries

Default Throttling Settings

| Setting | Default | Description |
| ———————— | ——- | ————————————— |
| HTTP Codes | 429 | Status codes that trigger throttling |
| Default Wait Time | 5000 ms | Fallback wait when no header is present |
| Random Jitter | Β±25% | Variance to prevent thundering herd |
| Max Throttle Retries | 5 | Max attempts before failing |

Documentation

| Document | Description |
| — | — |
| Configuration | Full parameter reference, throttling settings, safety limits |
| How It Works | Throttling behavior, header priority, architecture, execution flow |
| Migration Guide | Replace existing HTTP Request nodes (manual, JSON, API script) |
| Troubleshooting | Common issues and solutions |

Development

npm install
npm run build
npm test

Project Structure

β”œβ”€β”€ src/
β”‚   └── nodes/
β”‚       └── HttpRequest/
β”‚           β”œβ”€β”€ HttpRequestThrottled.node.ts   # Main node (V3 composition + fallback)
β”‚           β”œβ”€β”€ v3-loader.ts                   # Dynamic V3 node loader
β”‚           β”œβ”€β”€ throttle-wrapper.ts            # Helper interception for throttling
β”‚           β”œβ”€β”€ throttling.ts                  # Wait time calculation logic
β”‚           β”œβ”€β”€ throttling-props.ts            # Throttling UI properties
β”‚           └── translations/de/               # German translation
β”œβ”€β”€ docs/                                      # Documentation
β”œβ”€β”€ test/
β”‚   └── throttling.test.ts                     # Unit tests
β”œβ”€β”€ package.json
└── tsconfig.json

License

MIT

Contributing

1. Fork the repository
2. Create a feature branch
3. Run tests: npm test
4. Submit a pull request

From our network Other tools and sites we build