Overview
This node acts as a dynamic API caller for a backend system referred to as "GVA" (likely a custom or internal API platform). It allows users to specify an API endpoint path and HTTP method dynamically, then send requests with optional body and query parameters. This flexibility makes it useful for integrating with various GVA backend services without needing a dedicated node for each API.
Common scenarios include:
- Triggering different backend operations by specifying the API path and method at runtime.
- Sending data in JSON or form-data format to backend endpoints.
- Adding URL query parameters dynamically.
- Handling multiple API calls in one workflow execution.
Practical example: A user wants to create or update tags in a tag management system by calling the appropriate GVA API endpoint with JSON data describing the tag details.
Properties
| Name | Meaning |
|---|---|
| 发送请求体 | Whether to send request body data (boolean) |
| 请求体类型 | Request body content type; options are: Form-Data, JSON |
| 请求体参数 | Parameters for form-data body; list of name-value pairs (shown only if sending body as form) |
| JSON数据 | JSON formatted request body (shown only if sending body as JSON) |
| 发送查询参数 | Whether to add URL query parameters (boolean) |
| 查询参数 | Query parameters; list of name-value pairs |
Output
The node outputs an array of JSON objects representing the response(s) from the called API endpoint(s). Each item corresponds to one input item processed and contains the parsed JSON response from the backend.
If the API returns binary data, it would be included accordingly, but this node primarily handles JSON responses.
Dependencies
- Requires an API authentication credential to access the GVA backend system.
- Uses internal helper methods to fetch available API groups and APIs dynamically.
- The node depends on a method
gvaApiRequestto perform the actual HTTP request to the backend. - No external environment variables are explicitly required beyond the configured API credential.
Troubleshooting
- Operation format error: The operation parameter must be in the format
"path|method"(e.g.,/tags|POST). If not, the node throws an error indicating the expected format. - JSON parsing errors: When sending a JSON body, invalid JSON syntax will cause an error. Ensure the JSON is well-formed.
- API not found warning: If the specified API path and method do not match any known API, a warning is logged but execution continues.
- Failed to get API list: If fetching the list of APIs fails, the node logs the error but still attempts to execute the request.
- Continue on Fail: If enabled, the node will output error messages as JSON instead of stopping execution on failure.
Links and References
- No external links provided in the source code.
- For more information on n8n custom nodes and API integration, see the n8n documentation.
Note: All internal credential names and service identifiers have been generalized as per instructions.