Integration - HTTP

Type identifier: integration:http Category: Integration Operations

Description

The Integration - HTTP node performs HTTP requests to external URLs, supporting all common HTTP methods, custom headers, query parameters, request bodies, and OAuth 1.0a authentication. It can return parsed responses matching a defined schema.

Input Handles

Handle	Type	Description
`url`	`string`	(Dynamic) The URL to request.
`timeout`	`number`	(Dynamic) Request timeout in seconds.
`<variable>`	varies	Dynamic handles for configured variables.
`<searchParam>`	`string`	Dynamic handles for search parameters.
`<header>`	`string`	Dynamic handles for header values.
`body`	varies	(Dynamic) Request body content.

Note: Dynamic input handles appear based on configuration.

Output Handles

Handle	Type	Description
`result`	schema-defined	The parsed response body.
`responseHeaders`	schema-defined	Response headers (if configured).

Configuration Options

Basic Options

Option	Type	Default	Description
Method	`"GET"` \| `"POST"` \| `"PUT"` \| `"PATCH"` \| `"DELETE"`	`"GET"`	HTTP method for the request.
URL	`string` or dynamic	-	The target URL (must be valid URL format).
Timeout	`number` or dynamic	`15`	Request timeout in seconds (1-900).

Search Parameters

Array of key-value pairs appended to the URL as query parameters.

Field	Type	Description
Key	`string`	Parameter name.
Value	`string` or dynamic	Parameter value.

Headers

Array of custom HTTP headers to include in the request.

Field	Type	Description
Key	`string`	Header name.
Value	`string`, dynamic, or template	Header value (supports variable interpolation).

Body

Request body configuration (for POST, PUT, PATCH methods):

Content Type	Description
text	Plain text body (`text/plain`).
json	JSON body with schema validation (`application/json`).
form	URL-encoded form data (`application/x-www-form-urlencoded`).

Form body supports two modes:

Key-Value: Simple key-value pairs
Object: Schema-validated object

Response Schema

Option	Description
Result Schema	Schema for parsing response body.
Response Headers Schema	Schema for extracting specific response headers.

OAuth 1.0a (Optional)

Field	Type	Description
Consumer Key	`string` or dynamic	OAuth consumer key.
Token	`string` or dynamic	OAuth token (optional).
Signature Method	`"HMAC-SHA1"` \| `"HMAC-SHA256"` \| `"PLAINTEXT"`	Signature algorithm.
Include Body Hash	`boolean`	Include body hash in signature.
Realm	`string` or dynamic	OAuth realm (optional).

Behaviour

Constructs the request URL from base URL and search parameters
Validates the URL is not targeting local/internal addresses (security)
Resolves all dynamic values (such as headers and body)
If OAuth 1.0a is configured, signs the request
Sends the HTTP request with configured timeout
Parses response according to result schema
Extracts response headers if schema is configured
Returns parsed data through output handles

Security

Local/internal URLs are blocked by default, including when a redirect or a hostname's DNS answer points to an internal address.

Examples

Simple GET Request

Configuration:

Method: GET
URL: https://api.example.com/users
Result Schema: Array of user objects

POST With JSON Body

Configuration:

Method: POST
URL: https://api.example.com/orders
Headers:
- Authorization: Bearer <token>
Body:
- Content Type: JSON
- Value: Order object from dynamic input

OAuth 1.0a API Call

Configuration:

Method: GET
URL: https://api.twitter.com/1.1/statuses/user_timeline.json
OAuth 1.0a:
- Consumer Key: (from secret)
- Token: (from secret)
- Signature Method: HMAC-SHA256