RecipeAgents / n8n nodes / HTTP Request
Node reference · data pulled Oct 26, 2026n8n HTTP Request node: what the data shows
Calls any web API that has no dedicated n8n node, or does something the app node can't.
What it does
You give it a method, a URL, and optionally query parameters, headers and a body; it returns the response as items. It can reuse a stored credential from an app node or a generic one (basic auth, header, OAuth2 and so on), it can follow pagination, and you can paste a cURL command from an API's documentation to fill it in.
Half of all public templates use it. Its strongest partner is the Wait node: templates that hit rate limits pause between calls.
How often public templates use it
7,002 of the 13,574 public templates on n8n.io (51.6%) contain this node, in the snapshot we took on 2026-10-20. The table splits that by the year each template was published. 2026 runs to October 20.
| Year published | Templates with the node | Share of that year |
|---|---|---|
| 2024 | 266 of 462 | 57.6% |
| 2025 | 3,342 of 6,564 | 50.9% |
| 2026 | 3,239 of 5,845 | 55.4% |
The median template using this node has 252 views on n8n.io, against 284 for all templates. Template counts show what people publish, not what runs in production.
What it is used with
The most frequent partners are the nodes that appear most often in the same templates. "Lift" compares that with the whole library: 2× means the partner turns up twice as often next to this node as in an average template.
| Most frequent partner | Share of its templates | Lift |
|---|---|---|
| Code | 68.6% | 1.16× |
| Edit Fields (Set) | 62.5% | 1.12× |
| If | 56.0% | 1.11× |
| Google Sheets | 36.5% | 1.02× |
| Schedule Trigger | 35.9% | 1.13× |
| AI Agent | 27.5% | 0.88× |
Strong pairings (in at least 5% of its templates, lift 1.5× or more): 1. The top ones:
| Strong partner | Share of its templates | Lift |
|---|---|---|
| Wait | 26.7% | 1.51× |
Most viewed public templates that use it: Building your first whatsapp chatbot (541,254 views); Automate multi platform social media content creation with ai (442,651 views); Fully automated ai video generation and multi platform publishing (402,403 views).
Versions and changes
Node versions from the npm packages n8n-nodes-base and @n8n/n8n-nodes-langchain, version 2.44.4. New workflows get the default version; workflows built earlier keep the version they were built with until you replace the node.
| Node | Versions | Default | Credential types | Scope |
|---|---|---|---|---|
| HTTP Request | 1, 2, 3, 4, 4.1, 4.2, 4.3, 4.4, 4.5 | 4.5 | SSL client certificate | – |
Source on GitHub: packages/nodes-base/nodes/HttpRequest: 194 commits since the repository was reorganised on 2021-11-17, last on 2026-10-21.
Recent fixes and features
- 2026-09-08: feat(HTTP Request Node): Add support for PROPFIND, MKCOL, MOVE, COPY and REPORT methods (PR #24151)
- 2026-08-27: fix(HTTP Request Node): Keep SSL passphrases with whitespace intact (PR #37020)
- 2026-08-26: fix(HTTP Request Node): Show the API response when a file upload fails (PR #36924)
- 2026-07-31: feat(HTTP Request Node): Add Simplified Custom Auth generic credential (PR #35068)
- 2026-07-24: fix(HTTP Request Node): Include error body in continueOnFail mode (PR #34729)
- 2026-06-15: fix(Http Request Node): Preserve multipart filenames for binary uploads (PR #29022)
Merged dates from GitHub. A fix only helps once your n8n instance runs a release that includes it, so check your version.
Known problems
- 400 Bad Request. Usually malformed query parameters, often an array sent in the format the API does not expect. The node has an option for the array format. Source: n8n docs
- ECONNREFUSED inside Docker. In a container, localhost means the container itself. Point the URL at host.docker.internal (or 127.0.0.1 to avoid an IPv6 lookup on newer Node versions). Source: n8n docs
- 429 Too Many Requests. Use the node's Batching option or Retry on Fail to space calls out. Source: n8n docs
- Uploaded file has the wrong name. For form-data uploads the file name comes from the binary data, not the Name field. Source: n8n docs
- Mixed-up file names in parallel uploads. A 2026 fix stopped binary file names being mixed between parallel uploads; update if you upload files in batches. Source: n8n PR #30568
Forum trouble signal: not measured. The n8n community forum's terms forbid automated access, so we don't count forum threads.
Our recipes that use it
None of our 25 recipes uses this node yet. Browse all of them on the free n8n templates page.
Official docs and sources
Usage, pairings, AI share and views: our count of 13,574 public n8n.io templates (snapshot 2026-10-20). Versions: npm packages, version 2.44.4. Changes: n8n's GitHub repository. Docs read and data pulled Oct 26, 2026. We describe each node in our own words; the docs are the authority on settings.
Related nodes
- Split Out1,577 templates · score 58.3
- Edit Fields (Set)7,554 templates · score 51.3
- Code8,061 templates · score 51.0
- All 22 nodesSortable table with the scoring method
Questions
- How many n8n templates use the HTTP Request node?
- 7,002 of the 13,574 public templates on n8n.io (51.6%), in our snapshot of 2026-10-20.
- What is the HTTP Request node most often used with?
- Code, which appears in 68.6% of its templates. The most distinctive partner is Wait (lift 1.5×).
- Do I need the HTTP Request node if an app already has an n8n node?
- Only when the app node lacks the endpoint you need. You can reuse the app's stored credential in HTTP Request, so you don't re-enter keys.
- How do I handle an API that returns many pages?
- Use the node's Pagination option rather than building a loop by hand.