Nodes for making HTTP requests, building URLs, constructing headers, and responding to webhooks.

HTTP nodes handle outbound web requests and webhook responses. They let you call any REST API, construct URLs with query parameters, build headers, and send custom responses back to webhook callers.

This category contains both impure nodes (HTTP Request, Respond to Webhook) and pure nodes (Parse Response, Build URL, Build Headers, Form Data).

HTTP Request

Make an outbound HTTP request to any URL.

Pin	Direction	Type	Description
Exec	Input	Exec	Triggers the request
URL	Input	String	The target URL
Method	Input	Enum	HTTP method: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS (default: GET)
Headers	Input	Object	Request headers
Body	Input	Any	Request body
Timeout (s)	Input	Float	Request timeout in seconds (default: 30)
Exec	Output	Exec	Fires after the response is received
Response	Output	Object	Parsed response body
Status	Output	Integer	HTTP status code
Headers	Output	Object	Response headers

Impure. Use HTTP Request to call any REST API — querying external APIs, creating tickets, sending notifications, or fetching data.

Respond to Webhook

Send a custom HTTP response back to the webhook caller. This node is only valid inside patterns where the On Webhook trigger uses Response Node mode.

Pin	Direction	Type	Description
Exec	Input	Exec	Triggers the response
Status Code	Input	Integer	HTTP status code (default: 200)
Headers	Input	Object	Response headers
Body	Input	String	Response body text
Exec	Output	Exec	Fires after the response is sent

Impure. Use Respond to Webhook when you need to compute a response before sending it — returning enriched data, custom status codes, or formatted results to the caller.

Parse Response

Parse an HTTP response body by content type.

Pin	Direction	Type	Description
Response	Input	Object	The response object from HTTP Request
Format	Input	String	Parse format: "json", "text", or "xml" (default: "json")
Data	Output	Any	Parsed response data

Pure. Use Parse Response to extract structured data from API responses when the automatic parsing needs to be explicit.

Build URL

Construct a URL from a base, path, and query parameters.

Pin	Direction	Type	Description
Base URL	Input	String	The base URL (e.g., "https://api.example.com")
Path	Input	String	URL path to append (default: empty)
Query Params	Input	Object	Key-value pairs for query string
URL	Output	String	Complete URL with query parameters

Pure. Use Build URL to construct API endpoints dynamically — appending pagination parameters, filter criteria, or resource IDs.

Build Headers

Construct an HTTP headers object from a JSON definition.

Pin	Direction	Type	Description
Headers	Output	Object	The constructed headers object

Properties:

Headers JSON — the headers as a JSON object (default: {}).

Pure. Use Build Headers to create reusable header sets — authentication headers, content-type declarations, or custom header combinations.

Form Data

Build a form-encoded payload from a JSON definition.

Pin	Direction	Type	Description
Form Data	Output	Object	The form data object

Properties:

Fields JSON — the form fields as a JSON object (default: {}).

Pure. Use Form Data to construct payloads for APIs that expect form-encoded data rather than JSON.

Events — On Webhook triggers that receive inbound requests
Data Formats — parse and generate JSON, CSV, XML response data
Encoding — encode URLs, compute HMAC signatures for API authentication

HTTP