node cookbook

N8N HTTP Request Node Cookbook

Use the HTTP Request node as the general-purpose connector for APIs that do not have a built-in n8n node or need custom headers, methods, bodies, or authentication.

Use when: n8n workflows, APIs
First check: Read the target API documentation for endpoint, method, authentication, and body shape.
Time to check: 5-10 minutes
Next step: Run the recommended steps, then verify a production execution.

Independent third-party notes. n8n is a trademark of its owner and is referenced only for compatibility and troubleshooting context.

Quick Answer

Use the HTTP Request node as the general-purpose connector for APIs that do not have a built-in n8n node or need custom headers, methods, bodies, or authentication.

Version awareness

Last reviewed 2026-05-21

Applies to: n8n Cloud, self-hosted n8n, node cookbook, production workflows
Official docs checked: n8n HTTP Request Node
Version-sensitive assumptions: n8n node parameters, credential names, and queue mode defaults can change between releases; confirm against your installed version before changing production.
What may change after upgrades: Node parameter names, credential scopes, webhook behavior, Docker image defaults, and queue worker expectations may shift after n8n upgrades.

Key Facts

Node role: General API request builder.
Common setup: Method, URL, authentication, headers, query parameters, and body.
Best fit: Custom APIs, unsupported SaaS tools, internal endpoints, and advanced API features.
Companion nodes: Code, Set, IF, Webhook, Schedule Trigger, and Respond to Webhook.

Recommended Steps

Read the target API documentation for endpoint, method, authentication, and body shape.
Configure the HTTP method and URL.
Add authentication and required headers.
Map workflow data into query parameters or body fields.
Test with a small request and inspect status code and response body.

Verification

The request returns the expected status code.
The response body has the fields downstream nodes expect.
Authentication failures are visible and actionable.

Warnings

API credentials in headers or body should be stored in credentials, not hard-coded fields.
Retries and rate limits should be handled deliberately for production workflows.

Production Cookbook

Common production use cases

Call internal APIs.
Send webhook-style requests to SaaS apps.
Fetch data before branching or enrichment.

Required credentials/scopes

API key, OAuth2, or header auth stored in n8n credentials.
Least-privilege API scope for the endpoint.

Input fields that usually break

Content-Type header.
JSON body quoting.
Pagination cursors.
Timeout and retry settings.

Common errors

Invalid JSON body.
401/403 due to wrong credential or scope.
429 due to missing backoff.
HTML error page parsed as JSON.

Output shape example

{
  "statusCode": 200,
  "body": {
    "id": "resource_123",
    "state": "ok"
  },
  "headers": {
    "content-type": "application/json"
  }
}

Small working pattern

Build the request body as an object, enable response status inspection, branch on status code, and log only redacted context.

Related recipes using this node

When to use HTTP Request or Code instead: Use the app node when it supports the exact action; use HTTP Request for unsupported API endpoints; use Code only to reshape data before/after the call.

Sources

n8n HTTP Request Node Accessed 2026-05-07