Overview
This custom n8n node allows you to interact with the HttpBin API using HTTP GET requests. It is designed for scenarios where you need to test, debug, or demonstrate HTTP request and response handling, such as sending query parameters and inspecting the resulting output. Common use cases include:
- Testing how your data is sent as query parameters.
- Debugging webhooks or integrations by observing the exact request/response cycle.
- Learning or demonstrating HTTP concepts in a controlled environment.
Example:
You can use this node to send a GET request with specific query parameters to httpbin.org and receive a structured JSON response showing exactly what was received.
Properties
Name | Type | Meaning |
---|---|---|
Type of Data | Options | Selects the type of data to send. For GET, only "Query" (query parameters) is available. |
Query Parameters | Fixed Collection | Key-value pairs representing the query parameters to include in the GET request. Each entry has: - Key: The name of the query parameter. - Value: The value assigned to that key. |
Output
The node outputs a json
object containing the full response from HttpBin's /get
endpoint. The structure typically includes:
{
"args": { "param1": "value1", "param2": "value2" }, // Your query parameters
"headers": { ... }, // Request headers sent
"origin": "x.x.x.x", // IP address of the requester
"url": "https://httpbin.org/get?param1=value1¶m2=value2"
}
- args: An object listing all query parameters sent.
- headers: The headers included in the request.
- origin: The source IP address.
- url: The full URL including query string.
No binary data is returned; all output is in JSON format.
Dependencies
- External Service: HttpBin
- Credentials: No authentication required for public endpoints.
- n8n Configuration: No special configuration needed.
Troubleshooting
Common Issues:
- Malformed Query Parameters: Ensure all keys and values are non-empty strings.
- Network Errors: If httpbin.org is unreachable, check your network connection or proxy settings.
- Unexpected Output: Double-check the query parameters for typos or incorrect formatting.
Error Messages:
- "Request failed with status code 4xx/5xx": Indicates an issue with the request or remote server. Verify the endpoint and parameters.
- "Invalid input property": Make sure all required fields (especially "Key" and "Value") are filled.