How to Use the HTTP Request Node in n8n to Call Any API

When an app has no ready-made n8n node, the HTTP Request node lets you talk to it directly through its API. It is the most powerful node for beginners to learn.

What an API call is

An API is a doorway into a service. You send a request to a URL with a method (GET to read, POST to create, PUT or PATCH to update, DELETE to remove), and you get a response, usually JSON.

Setting up the node

Choose the method.
Paste the URL from the service’s API documentation.
Add headers such as content type.
Add query parameters or a body as the docs describe.
Choose authentication: an API key, a bearer token or OAuth.

Always read the provider’s documentation; each API has its own rules.

Authentication

Store keys in credentials, not typed into fields. More in connecting any API and authentication.

Reading the response

The response becomes items you can use in later nodes. If the API returns a list inside a field, you may need to split it into items.

Pagination and limits

Large lists come in pages. Many APIs also limit how often you can call them. Use loops carefully (looping over items) and add waits if needed.

Common errors

401/403: wrong or missing credentials.
404: wrong URL.
429: too many requests; slow down.
400: body or parameters are not what the API expects.

Test outside n8n first

If something fails, try the same request in a simple API testing tool to see whether the problem is the request or the workflow.

Quick answers

When should I use the HTTP Request node?

When an app has no ready node but offers an API.

What does a 401 error mean?

Your credentials are missing or wrong.

How do I handle large lists from an API?

Use the API’s pagination and slow down with batches and waits.