HTTP Node

The HTTP node calls external APIs to fetch data or submit data to third-party systems. It can configure method, URL, headers, params, body, and SSL verification options.

Configurable Fields

Field	Description
Label	Node name.
Method	HTTP method. Supports GET, POST, PUT, PATCH, DELETE, HEAD, and OPTIONS.
URL	API endpoint.
Skip SSL Verification	Whether to skip SSL verification.
Headers	Header key/value pairs. Each row can be enabled or disabled.
Params	Query param key/value pairs. Each row can be enabled or disabled.
Body Type	Request body type.

Screenshot pending: the current production workflow does not have an existing HTTP node. After adding an HTTP node in a test workflow, capture the settings panel that includes Method, URL, Skip SSL Verification, Headers, Params, and Body Type.

Body Type

The HTTP node supports these body types:

Type	Description
none	Sends no body.
form-data	Uses form-data fields.
x-www-form-urlencoded	Uses URL encoded fields.
json	Sends a JSON body.
raw	Sends raw body content.
binary	Sends a binary payload or template value.

Output

The HTTP node provides:

Field	Description
status_code	HTTP response status code.
body	Response body.
headers	Response headers.

You can use status_code in an If / Else node to handle success or failure, or use body in an LLM or End node to format the response.

Recommendations

• Put API keys or tokens in Headers instead of writing them into publicly visible content.
• Use If / Else to handle error statuses from external APIs.
• Validate JSON format before using a JSON body.
• Enable Skip SSL Verification only for testing or when explicitly required.