HttpBin icon

HttpBin

Interact with HttpBin API

Actions2

Overview

This n8n node allows you to interact with the HttpBin API using HTTP GET requests. It is designed for testing and debugging HTTP requests by sending customizable query parameters and receiving structured responses that echo your request details. Common scenarios include:

  • Testing how your application sends query parameters.
  • Debugging webhooks or integrations by inspecting the exact data sent in a GET request.
  • Learning about HTTP request/response structure.

Example:
You can use this node to send a GET request with custom query parameters to httpbin.org/get and receive a response showing exactly what was received by the server.

Properties

Name Type Meaning
Type of Data options Selects the type of data to send. For GET, only "Query" (query parameters) is allowed.
Query Parameters fixedCollection Key-value pairs representing the query parameters to include in the GET request. Each entry has a "Key" (parameter name) and "Value" (parameter value).

Output

The node outputs a JSON object reflecting the response from HttpBin's /get endpoint. The typical structure includes:

{
  "args": { "param1": "value1", ... },   // Echoes back the query parameters sent
  "headers": { ... },                    // Request headers as seen by HttpBin
  "origin": "x.x.x.x",                   // IP address of the requester
  "url": "https://httpbin.org/get?..."   // Full URL including query string
}
  • args: Object containing all query parameters sent.
  • headers: Object with HTTP headers received by HttpBin.
  • origin: Your public IP address.
  • url: The full request URL.

No binary output is produced.

Dependencies

  • External Service: HttpBin API
  • Credentials: No authentication required for public endpoints.
  • n8n Configuration: None specific; works out-of-the-box.

Troubleshooting

Common Issues:

  • Malformed Query Parameters: If keys or values are missing, the args field in the response may not reflect your expectations.
  • Network Errors: If n8n cannot reach httpbin.org, you may see connection errors such as ENOTFOUND or ECONNREFUSED.
  • Unexpected Output: If you do not set any query parameters, the args object will be empty.

Error Messages:

  • "Request failed with status code 404": Likely due to an incorrect endpoint or method.
  • "Invalid parameter": Ensure all required fields ("Key" and "Value") are filled in the Query Parameters collection.

Links and References

Discussion