Overview
This node provides a generic interface to interact with the weLore REST API using an OpenAPI specification. It allows users to dynamically select resources and operations exposed by the API, then specify parameters to customize each request. The node is useful for automating workflows that require integration with the weLore platform, such as managing accounts, retrieving data, or performing actions supported by the API.
Typical use cases include:
- Fetching or updating data related to a specific account on weLore.
- Executing various API operations without needing to write custom HTTP requests manually.
- Automating repetitive tasks by chaining multiple API calls in n8n workflows.
For example, a user might configure this node to call a "getUser" operation on a "users" resource, passing query parameters to filter results, and then process the returned JSON data downstream.
Properties
| Name | Meaning |
|---|---|
| Account Name | The name of the account to use when making API requests. |
| Resource ID | Optional numeric identifier for a specific resource instance (used internally for parameter loading). |
| Parameters | A collection of key-value pairs representing additional parameters for the selected operation. Each parameter consists of: - Parameter Name or ID: Selectable from a dynamic list based on the chosen resource and operation. - Value: The value to assign to the parameter. |
The "Parameters" property supports multiple entries, allowing users to specify any number of parameters required by the API operation. Parameters can be used to replace path variables, query parameters, or request body fields depending on the operation's definition.
Output
The node outputs an array of JSON objects corresponding to the API responses for each input item processed. Each output item contains the parsed JSON response from the weLore API call.
If the API returns binary data, it would typically be handled separately, but this node focuses on JSON responses and does not explicitly handle binary output.
Dependencies
- Requires an API authentication token credential to authorize requests to the weLore API.
- Uses the OpenAPI schema (
docs.openapi.yaml) bundled with the node to dynamically load available resources, operations, and their parameters. - Makes HTTP requests to the base URL
https://api-weafinity.madfenix.com.
No additional external dependencies are needed beyond standard n8n credentials and HTTP request capabilities.
Troubleshooting
- Failed to load resources or operations: This error may occur if the OpenAPI schema file is missing or corrupted. Ensure the
docs.openapi.yamlfile is present and valid. - Operation not found for resource: Indicates the selected operation does not exist for the chosen resource. Verify the resource and operation selections.
- HTTP request errors: Could be due to invalid credentials, network issues, or incorrect parameters. Check the API token validity and parameter correctness.
- Parameter replacement issues: If parameters meant for URL path segments or query strings are not replaced correctly, ensure parameter names match those expected by the API and are specified properly in the "Parameters" collection.
- Continue On Fail behavior: When enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.
Links and References
- n8n Expressions Documentation
- weLore API Documentation (assumed) (not directly linked in code but inferred)