HTTP Request

The HTTP Request node lets you call any REST API endpoint. Use it when there's no pre-built integration, or when you need full control over the API call.

Type: HTTP Color: Magenta gradient (#7D007D#C800C8) Credits: None (premium node) Tabs: Initialise → Configure → Test

Tab 1: Initialise

When you add an HTTP Request node, the Initialise tab opens with template options.

HTTP Request Initialise tab showing Start from scratch option and 5 templates
HTTP Request Initialise: choose a template or start from scratch

Templates

TemplatePre-fills
Start from scratchEmpty; configure everything manually
GET RequestMethod: GET, no body
POST JSONMethod: POST, Content-Type: application/json, raw JSON body editor
Authenticated RequestMethod: GET, Bearer token auth header
File UploadMethod: POST, Form Data with file field
Import cURLPaste any cURL command; it auto-populates method, URL, headers, body, auth

Select a template and click Continue → to move to the Configure tab.

Tip

Import cURL is the fastest way to set up an API call. Copy the cURL from any API documentation, paste it in, and all fields are auto-filled.

Tab 2: Configure

The Configure tab is where you set up the actual API call. Fields vary based on the template you chose.

Method

Select the HTTP method:

MethodWhen to use
GETFetch data (default)
POSTCreate data, submit forms
PUTReplace/update data
PATCHPartially update data
DELETERemove data

URL (required)

The API endpoint URL. Supports FX formulas; use variables from previous nodes:

https://api.example.com/users/{{trigger.body.user_id}}

Path variables use :variableName syntax; they appear in a separate field below the URL.

Query Parameters

Key-value pairs appended to the URL as ?key=value&key2=value2. Each value supports FX formulas. Add unlimited rows.

Headers

Custom HTTP headers as key-value pairs. Each value supports FX formulas. Common examples:

Content-Type: application/json
Authorization: Bearer {{token}}
X-API-Key: {{connection.api_key}}

Body (POST, PUT, PATCH only)

The request body. Five body types:

TypeDescriptionContent-Type
NoneNo body
Raw → JSONJSON editor with Grid (key-value table) or FX (raw formula) modesapplication/json
Raw → TextPlain texttext/plain
Raw → XMLXML stringapplication/xml
Raw → HTMLHTML stringtext/html
Form DataKey-value pairs with text or file fieldsmultipart/form-data
URL EncodedKey-value pairs URL-encodedapplication/x-www-form-urlencoded
BinaryUpload a file or use an FX formula for file dataapplication/octet-stream
Note

For JSON bodies, the Grid mode lets you build the JSON visually as key-value pairs. The FX mode gives you a raw formula editor for complex payloads.

Authorization

TypeFields
NoneNo authentication
BasicUsername + Password
BearerToken (FX formula; can reference variables)

Tab 3: Test

The Test tab lets you run the API call with real data and see the response.

  1. Click Test to execute the request
  2. The response appears: status code, headers, and body
  3. If successful, the output schema populates automatically
  4. Downstream nodes can now reference response fields in the variable picker
Warning

Test runs make real API calls. If your endpoint creates data or triggers actions, be aware that the test will actually execute.

Output variables

After a successful test or execution:

VariableWhat it contains
{{http_request.body}}The parsed response body (JSON → object, text → string)
{{http_request.body.fieldName}}A specific field from the JSON response
{{http_request.status}}HTTP status code (200, 404, 500, etc.)
{{http_request.headers}}Response headers as key-value object

Validation

RuleSeverity
URL is requiredError: node won't save
Method defaults to GET if not setWarning
POST/PUT/PATCH without a bodyWarning (not error; some APIs don't need a body)

Error handling

By default, 4xx and 5xx responses stop the workflow. To handle errors gracefully:

  1. Enable Continue on error in the node settings
  2. Add an If-Else node checking {{http_request.status}}
  3. Route status === 200 to success, status >= 400 to error handling

Common patterns

Fetch + process

Trigger → HTTP Request (GET data) → Transformer (extract fields) → Create Record

POST with auth

Trigger → HTTP Request (POST to external API with Bearer token) → If-Else (check status) → Send notification

Webhook forwarding

Webhook Trigger → HTTP Request (forward payload to another service)
Tip

Chain multiple HTTP Request nodes to call different APIs in sequence. Each node's response is available to the next via variables.