Overview
The node interacts with the HttpBin API, specifically supporting HTTP GET requests under the "HTTP Verb" resource. It allows users to send GET requests with customizable query parameters. This is useful for testing and debugging HTTP requests by sending specific query parameters and observing the response from HttpBin.
Practical examples include:
- Sending a GET request with custom query parameters to test how an API handles them.
- Debugging URL parameter encoding and transmission.
- Learning about HTTP request structures by inspecting the echoed response from HttpBin.
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 sent with the GET request. |
Output
The node outputs JSON data that reflects the response from the HttpBin API for the GET request made. The json output field contains the full response body, which typically includes details such as the URL requested, the query parameters received, headers, and other HTTP request metadata echoed back by HttpBin.
No binary data output is produced by this node.
Dependencies
- Requires access to the public HttpBin API at https://httpbin.org.
- Optionally can use an API key credential if configured, but it is not required.
- No additional environment variables or special n8n configurations are necessary.
Troubleshooting
- Common issues:
- Network connectivity problems may prevent reaching the HttpBin service.
- Incorrectly formatted query parameters could lead to unexpected responses.
- 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 service unavailability.
- Resolutions:
- Verify internet connection and HttpBin service status.
- Ensure query parameters are correctly specified as key-value pairs.
- Retry after some time if the service is temporarily down.