n8n HTTP Request Node: The Universal API Client
Master the HTTP Request node — auth methods, pagination, retries, binary downloads, and gotchas with large responses.
Key takeaways
- Use the Generic Credential type for any reusable auth — never paste tokens in node fields.
- Enable Pagination for any list endpoint, even if you think the result is small.
- Set explicit Response Format — JSON for APIs, File for binary downloads.
- Add Retry On Fail with 3 attempts for any external call.
When no native integration exists, the HTTP Request node is your bridge to the universe of REST APIs. It is also one of the most underutilized nodes — most users never explore pagination, batching, and the credential generic helpers.
Authentication done right
Create a Generic Credential (Header Auth, Bearer, OAuth2, Query Auth). Reuse across all HTTP nodes that hit the same API. Never put tokens in plaintext fields — they become impossible to rotate.
Pagination
Enable Pagination → choose Response Contains Next URL, or Next Cursor, or Page Increment. n8n loops until done and returns all items. Beats writing a Loop + IF + HTTP chain.
Binary downloads
Set Response Format → File. Downloads land as binary data on the item, ready to pass into S3, Sheets, or any other node that accepts binary.
Large responses
For payloads over 256MB, enable Response → Streaming or split the request. The execution data store has limits you do not want to discover on a Friday afternoon.
Frequently asked questions
- How do I send raw JSON without n8n auto-wrapping?
- Set Body Content Type → JSON and Use Expression on the body field with a raw JSON.stringify(...).
- Why am I getting 401 even with the right token?
- Token is in the wrong header (Authorization vs X-API-Key) or the OAuth scopes are insufficient.