GuidesNodes
HTTP
Make HTTP requests to external APIs, webhooks, and services.
HTTP nodes make an HTTP request and return the response. Use them to call external APIs, trigger webhooks, or interact with any service that exposes an HTTP endpoint.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| url | string | No | The request URL. Supports placeholders such as https://api.example.com/users/{{input.userId}}. |
| method | string | No | HTTP method: GET, POST, PUT, DELETE, or PATCH. Defaults to GET. |
| headers | string | No | Request headers as a JSON object string. Values support placeholders (for example, Authorization: Bearer {{secrets.apiKey}}). |
| body | string | No | Request body for POST, PUT, and PATCH requests. Typically JSON. Supports placeholders to inject dynamic data. |
Input
The node receives the trigger payload and upstream node outputs. Use placeholders in url, headers, and body to inject that data into the outgoing request.
Output
The node produces the HTTP response, including status code, headers, and body. The response body is parsed and passed to downstream nodes. Failed requests (4xx/5xx status codes or network errors) are recorded in the node execution record with full request and response metadata for debugging.
Tips
- Store API keys and tokens in Secrets and reference them with placeholders (for example,
{{secrets.apiKey}}). Never hardcode credentials in node configuration. - For JSON APIs, set the
Content-Type: application/jsonheader and provide a JSON-formatted body. - Request and response metadata (URL, method, status code, headers, timing) are recorded with every execution for auditability.
- If the target API may return errors or unexpected response shapes, add a Code or Switch node downstream to validate and handle the response.