Skip to content

HTTP Request

Makes HTTP requests to external APIs and services and returns the response data. Use this node to fetch data from REST APIs, submit forms, send webhooks, or interact with any HTTP-based service.

Configuration

Request

FieldDescriptionNotes
MethodThe HTTP methodGET, POST, PUT, PATCH, DELETE, HEAD, or OPTIONS. Defaults to GET.
URLThe full request URLRequired. Supports templates, e.g., https://api.example.com/users/{{data.user_id}}.

Authentication

FieldDescriptionNotes
AuthenticationAuthentication method to useNone, Basic Auth, Bearer Token, API Key in Header, or API Key in Query Parameter. Defaults to None.
UsernameBasic Auth usernameShown when Authentication is Basic Auth. Supports templates.
PasswordBasic Auth passwordShown when Authentication is Basic Auth. Supports templates.
TokenBearer token valueShown when Authentication is Bearer Token. Supports templates.
Header NameCustom header name for API keyShown when Authentication is API Key in Header. Defaults to X-API-Key. Supports templates.
API KeyThe API key valueShown when Authentication is API Key in Header. Supports templates.
Parameter NameQuery parameter name for API keyShown when Authentication is API Key in Query Parameter. Defaults to api_key. Supports templates.
Parameter ValueThe API key valueShown when Authentication is API Key in Query Parameter. Supports templates.

Query Parameters

FieldDescriptionNotes
Query ParametersKey-value pairs appended to the URLSupports templates.

Headers

FieldDescriptionNotes
HeadersCustom HTTP headersKey-value pairs. Supports templates.

Body

FieldDescriptionNotes
Body TypeFormat of the request bodyJSON, Form URL-Encoded, or Raw. Defaults to JSON.
Request BodyThe body contentShown for JSON and Raw body types. Supports templates. Defaults to {}.
Form ParametersKey-value form fieldsShown for Form URL-Encoded body type. Supports templates.
Content TypeMIME type for raw bodiesShown for Raw body type. Defaults to text/plain.

Response

FieldDescriptionNotes
Response FormatHow to parse the response bodyAuto-detect, JSON, XML, CSV, YAML, or Text. Defaults to Auto-detect.
Output each item separatelyWhen the response is an array, output each element as a separate itemEnabled by default.

Settings (tab)

FieldDescriptionNotes
Timeout (ms)Request timeout in millisecondsRange: 1,000--300,000. Defaults to 30000 (30 seconds).
Retry CountNumber of retry attempts on failureRange: 0--10. Defaults to 0 (no retries).
Retry Delay (ms)Base delay between retriesRange: 100--30,000. Defaults to 1000. Uses exponential backoff with jitter.
Follow RedirectsWhether to follow HTTP redirectsEnabled by default.
Max RedirectsMaximum number of redirects to followRange: 1--50. Defaults to 10. Shown when Follow Redirects is enabled.
Continue on HTTP ErrorTreat 4xx/5xx responses as data instead of failingDisabled by default.

Output

When Output each item separately is enabled and the response body is a JSON array, each element becomes a separate output item.

Otherwise, the output is a single item with:

FieldDescription
status_codeThe HTTP status code (e.g., 200)
headersResponse headers as key-value pairs
bodyThe parsed response body
body_rawThe raw response body as a string
binaryPresent for non-text responses; contains data (base64), mimeType, and fileSize

WARNING

By default, HTTP 4xx and 5xx responses cause the node to fail. Enable Continue on HTTP Error in the Settings tab if you want to handle error responses in your workflow logic.

TIP

Use the Retry settings for APIs that may be temporarily unavailable. The retry mechanism uses exponential backoff with jitter to avoid overwhelming the target server.