Overview
This 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 to the HttpBin service, which is useful for testing and debugging HTTP requests by echoing back the request data.
Common scenarios include:
- Testing how query parameters are sent and received by an API.
- Debugging HTTP GET requests by inspecting the echoed response from HttpBin.
- Learning or demonstrating HTTP request mechanics in workflows.
Example: Sending a GET request with specific query parameters to see how they are encoded and returned by the server.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Selects the type of data to send; currently only supports "Query" (query parameters). |
| Query Parameters | Key-value pairs representing the query parameters to be included in the GET request URL. |
Output
The node outputs JSON data that reflects the response from the HttpBin API. For a GET request with query parameters, the output JSON typically includes fields such as:
args: An object containing the query parameters sent in the request.- Other standard HttpBin response fields like
headers,origin,urlwhich provide details about the request environment.
No binary data output is produced by this node.
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 special n8n configurations are required.
Troubleshooting
Issue: Query parameters not appearing in the response.
- Cause: The "Type of Data" property must be set to "Query" and query parameters properly defined.
- Solution: Ensure query parameters are correctly added as key-value pairs and the node is configured for a GET operation.
Issue: Network errors or timeouts.
- Cause: Connectivity issues or HttpBin service downtime.
- Solution: Verify internet connection and try again later.
Error: Invalid parameter format.
- Cause: Missing keys or values in query parameters.
- Solution: Make sure each query parameter has both a key and a value defined.