Overview
This node implements an HTTP GET request operation designed to send query parameters to a specified endpoint. It is useful when you need to retrieve data from a web service or API by passing parameters in the URL's query string. Typical use cases include fetching filtered lists, searching resources, or retrieving specific information based on criteria defined as query parameters.
For example, you might use this node to:
- Retrieve user data from an API by specifying user IDs as query parameters.
- Search for products in an e-commerce API by sending search terms and filters.
- Request weather data for a specific location by passing latitude and longitude as query parameters.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Selects the type of data to send; currently only "Query" (query parameters) is supported. |
| Query Parameters | A collection of key-value pairs representing the query parameters to be appended to the URL. |
The Query Parameters property allows multiple entries, each with:
- Key: The name of the query parameter.
- Value: The value associated with the key, which will be sent as part of the URL query string.
Output
The node outputs JSON data representing the response received from the HTTP GET request. The structure of the JSON output depends on the external API or service being called but typically includes the requested data or error information.
If the response contains binary data, it would be handled accordingly, but based on the provided code and properties, the focus is on JSON responses via query parameters.
Dependencies
- Requires an active internet connection to perform HTTP requests.
- Optionally uses an API authentication token or API key credential if configured (not mandatory as per the bundled code).
- The base URL is preset to a Bitrix24 REST API endpoint (
https://sub-123.bitrix24.ru/rest), so the node is tailored for integration with Bitrix24 services unless modified.
Troubleshooting
- Empty or incorrect query parameters: Ensure that all required keys and values are correctly set; missing or malformed parameters can lead to unexpected results or errors.
- Network issues: Connection failures or timeouts may occur if the target server is unreachable.
- Authentication errors: If the API requires authentication, ensure that valid credentials are provided.
- Unexpected response format: If the API changes its response structure, the node’s output may not match expectations.
Common error messages might include HTTP status codes like 400 (Bad Request) due to invalid query parameters or 401/403 (Unauthorized/Forbidden) if authentication fails.
Links and References
- Bitrix24 REST API Documentation
- HTTP GET Method - MDN Web Docs
- n8n HTTP Request Node Documentation (for general HTTP request usage)