Overview
The node interacts with the HttpBin API, specifically performing HTTP GET requests with customizable query parameters. It is useful for testing and debugging HTTP requests by sending GET requests to HttpBin endpoints and inspecting the responses. Practical use cases include verifying how query parameters are sent and received, experimenting with different request configurations, or learning about HTTP request/response structures.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Selects the type of data to send; currently only "Query" (query parameters) is supported. |
| Query Parameters | Key-value pairs representing the query parameters to be included in the GET request URL. |
Output
The node outputs JSON data corresponding to the response from the HttpBin API for the GET request made. The json output field contains the parsed response body, which typically includes details about the request such as the URL, headers, and query parameters received by HttpBin. There is no binary data output.
Dependencies
- Requires access to the public HttpBin API at https://httpbin.org.
- Optionally uses an API key credential if configured, but it is not mandatory.
- No additional environment variables or n8n-specific configurations are required.
Troubleshooting
- Common issues:
- Incorrectly formatted query parameters may lead to unexpected results or errors.
- Network connectivity problems can prevent reaching the HttpBin service.
- Error messages:
- HTTP errors (e.g., 4xx or 5xx status codes) indicate issues with the request or server availability.
- Timeout errors suggest network delays or unresponsive endpoints.
- Resolutions:
- Verify that query parameters are correctly specified as key-value pairs.
- Ensure internet connectivity and that https://httpbin.org is reachable.
- Check for typos or invalid characters in parameter keys and values.