Advanced HTTP Request icon

Advanced HTTP Request

Makes HTTP requests with advanced type conversion and validation

Overview

This node performs advanced HTTP requests with flexible configuration options and enhanced type conversion for request data. It supports all common HTTP methods (GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS) and allows users to specify URLs, headers, and body content dynamically or statically. The node is useful when you need to interact with any RESTful API or web service where you want fine control over the request details, including dynamic data injection and response handling.

Typical use cases include:

  • Calling third-party APIs with complex authentication headers.
  • Sending JSON payloads with precise type conversions.
  • Handling redirects and SSL validation settings.
  • Retrieving full HTTP responses including headers and status codes for debugging or conditional logic.

Properties

Name Meaning
Method The HTTP method to use for the request. Options: DELETE, GET, HEAD, OPTIONS, PATCH, POST, PUT
URL The target URL to which the HTTP request will be sent.
Use Dynamic Data Whether to use incoming JSON data dynamically for query parameters, headers, and body with type conversion.
Headers Static list of HTTP headers to send with the request (only used if not using dynamic data).
Body JSON body content to send with POST, PUT, or PATCH requests (only used if not using dynamic data).
Options Collection of additional request options:
- Follow Redirects Whether to automatically follow HTTP redirects (default: true).
- Max Redirects Maximum number of redirects to follow (default: 5).
- Return Full Response Whether to return the full HTTP response including headers and status code instead of just the body.
- Timeout Request timeout in milliseconds (default: 30000 ms).
- Validate SSL Certificate Whether to validate SSL certificates (default: true).

Output

The node outputs an array of items, each containing a json field with the HTTP response data:

  • If Return Full Response option is disabled (default), the output JSON contains:

    {
  "data": <response_body>
}

    where <response_body> is the parsed response body from the HTTP request.

  • If Return Full Response is enabled, the output JSON includes:

    {
  "statusCode": <HTTP_status_code>,
  "headers": { <redacted_headers> },
  "body": <response_body>,
  "url": "<request_url>",
  "method": "<HTTP_method>"
}

    Sensitive header values such as authorization tokens and cookies are partially redacted for security.

The node does not output binary data.

Dependencies

  • Requires internet access to make HTTP requests.
  • Supports optional credentials for HTTP Basic Auth or Header-based Auth (configured separately in n8n).
  • No external libraries beyond those bundled with n8n workflow environment.

Troubleshooting

  • Invalid URL error: The node validates the URL format strictly. Ensure the URL starts with http:// or https:// and is well-formed.
  • Timeouts: Requests may fail if the server is slow or unreachable. Adjust the Timeout option accordingly.
  • SSL Validation errors: If connecting to servers with self-signed or invalid certificates, disable SSL validation via the option.
  • Type conversion errors: When using dynamic data, malformed JSON or incorrect types in input fields can cause conversion errors. Verify input data structure matches expected types.
  • Authentication failures: Make sure required API keys or credentials are correctly configured in n8n and included in headers if needed.
  • Redirect loops: Limit max redirects to prevent infinite loops.

Links and References

Discussion