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.
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.
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.