n8n HTTP Request nodeConfigure HTTP Request in n8n.

The dropdown at the top decides which verb travels on the wire, and the rest of the panel adapts to it. Reads use GET, writes use POST or PUT, partial updates use PATCH.

• Method: seven choices, DELETE, GET, HEAD, OPTIONS, PATCH, POST and PUT, matching whatever the API documentation asks for.

Whatever endpoint you type here is where the call lands, and it is the one field the node refuses to run without. Expressions belong in it too, so the path changes per item.

• URL: the full endpoint, shaped like http://example.com/index.html, often assembled from the previous node with {{ $json.id }} inside the path.

Three ways to prove who is calling sit behind this selector, and the choice decides which extra field appears underneath.

• None (none): the request goes out with nothing attached.
• Predefined Credential Type (predefinedCredentialType): auth n8n already implemented, selected in Credential Type, recommended whenever the service is available.
• Generic Credential Type (genericCredentialType): fully customizable, set in Generic Auth Type, from Basic auth to OAuth2 API.

Some servers expect the caller to present a certificate of its own before the conversation starts. This switch is what makes the node offer one.

• SSL Certificates: a plain toggle, left off unless the target insists on client certificates.

Query parameters act as filters on the request. Turn this on when the API supports them and the call needs narrowing.

• Specify Query Parameters: keypair (Using Fields Below) for name and value pairs added one by one, or json (Using JSON).
• Query Parameters: the pairs themselves, extended with Add Query Parameter.
• JSON: the same filters written as a single object.

Headers carry metadata and context about the call, the kind of detail an API reads before it looks at anything else. This switch opens the fields that hold them.

• Specify Headers: keypair (Using Fields Below) for name and value pairs, or json (Using JSON).
• Headers: the pairs, added through Add Header.
• JSON: the whole header set as one object.

Creating or updating something means sending content along with the call. Switch this on, then match the format the API documents.

• Body Content Type: json (JSON), form-urlencoded (Form Urlencoded), multipart-form-data (Form-Data), binaryData (n8n Binary File) or raw (Raw).
• Specify Body: explicit fields (keypair) or a JavaScript object (json), filled through Body Parameters, JSON or a single Body such as field1=value1&field2=value2.
• Input Data Field Name: the incoming field holding the binary file, paired with Content Type for raw payloads.

Input items become requests one for one, which a rate-limited API notices fast. Add this option to split them into groups and breathe between groups.

• Items per Batch: how many input items go into each batch, with -1 disabling the split and 0 treated as one.
• Batch Interval (ms): the pause between batches, 0 for none. Set 1000 to keep the pace at one request per second.

By default the node downloads a response only when certificate validation succeeds. Adding this option lets the response through even when validation fails.

• Ignore SSL Issues (Insecure): a single switch, off in normal use, on when the certificate cannot be verified.

APIs disagree on how a repeated filter should look inside a URL, and this option picks the spelling, but only once Send Query Parameters is on.

• No Brackets (repeat): the name repeats, foo=bar&foo=qux.
• Brackets Only (brackets): square brackets after each name, foo[]=bar&foo[]=qux.
• Brackets with Indices (indices): brackets plus a position, foo[0]=bar&foo[1]=qux.

Header names come out lowercase unless you say otherwise. Turned on is the default behavior, turned off keeps the capitalization exactly as typed.

• Lowercase Headers: one switch, worth flipping only for a service that reads header names literally.

When a server answers with a new location, the node follows by default. This option is where that behavior gets bounded or stopped.

• Follow Redirects: on by default, off when you want to see the redirect answer itself rather than its destination.
• Max Redirects: the ceiling on how many hops the request accepts before giving up.

What comes out of the node is negotiable. This option shapes it, from the format to what counts as a failure.

• Include Response Headers and Status: returns the full response instead of the body alone.
• Never Error: succeeds even when the status code is not 2xx, so error handling moves into the workflow.
• Response Format: autodetect (Autodetect), json (JSON), text (Text) or file (File), the last two writing into Put Output in Field.

Large collections arrive in slices, and this option keeps asking until the collection is complete. Look at one unpaginated response first to see which shape the API uses.

• Pagination Mode: off (Off), updateAParameterInEachRequest (Update a Parameter in Each Request) with its Parameters, or responseContainsNextURL (Response Contains Next URL) with Next URL.
• Pagination Complete When: Response Is Empty, Receive Specific Status Code(s) with Status Code(s) when Complete, or Other with Complete Expression.
• Limit Pages Fetched and Max Pages, plus Interval Between Requests (ms).

Outbound traffic sometimes has to leave through a specific gateway, whether for filtering or for a fixed exit address. One field handles that.

• Proxy: the HTTP proxy the request should use, written like http://myproxy:3128, taking precedence over the global HTTP_PROXY, HTTPS_PROXY and ALL_PROXY environment variables.

A server that never answers is worse than one that refuses. This value caps how long the node waits for response headers and the start of the body before it aborts.

• Timeout: the wait in milliseconds, for instance 5000 on an endpoint that normally replies straight away.

A redirect can point somewhere else entirely. This option decides whether the secrets follow it there.

• Send Credentials on Cross-Origin Redirect: a switch that lets credentials, such as the Authorization header, travel on a redirect to a different origin.

Attached to an AI agent as a tool, the node feeds its response to a model, and a raw API answer wastes tokens. This option trims it before the model reads it.

• Expected Response Type: json (JSON) with Field Containing Data, Include Fields (All, Selected, Except) and Fields; html (HTML) with Selector (CSS), Return Only Content and Elements To Omit; or text (Text).
• Truncate Response and Max Response Characters: a hard ceiling on the size.