Overview
This node, named "EAVFW," is designed to interact with the EAVFW environment, specifically allowing users to query records from a specified table. It enables searching for existing records based on flexible search criteria defined by the user. This functionality is useful in scenarios where you need to retrieve data entries matching certain conditions from a database or data store structured in an Entity-Attribute-Value (EAV) model.
Practical examples include:
- Retrieving customer records where the status equals "active."
- Finding product entries with prices greater than a specified amount.
- Querying user data with case-insensitive matching on usernames.
Properties
| Name | Meaning |
|---|---|
| Table | The target table from which to query records. Options are dynamically loaded from available tables. |
| Search Criteria | One or more conditions to filter records. Each condition includes: |
| - Field Name: The field within the table to apply the condition on (dynamically loaded based on table). | |
| - Operator: Comparison operator to use (Equal, Not Equal, Greater Than, Greater Than or Equal, Less Than, Less Than or Equal). | |
| - Right: The value to compare the field against. | |
| Options | Additional options affecting query behavior: |
| - Ignore Case: Whether to ignore letter case when evaluating conditions (default: true). | |
| - Less Strict Type Validation: Whether to attempt casting value types based on the selected operator (default: true). |
Output
The node outputs JSON data representing the records that match the specified search criteria from the selected table. Each output item corresponds to a record found in the query. If binary data were involved, it would be summarized here, but this node focuses on JSON record data only.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials to connect securely to the EAVFW environment.
- Dynamic loading of tables and fields depends on methods implemented in the node's loadOptions functions.
- No additional external services beyond the authenticated EAVFW API connection are required.
Troubleshooting
Common Issues:
- Incorrect or missing table selection may result in no data returned or errors.
- Invalid search criteria, such as unsupported operators or mismatched field types, can cause query failures.
- Authentication errors if the OAuth2 credential is not properly configured or expired.
Error Messages:
- Errors related to "table not found" indicate the selected table does not exist or is inaccessible.
- "Invalid search criteria" errors suggest issues with the field name, operator, or value types.
- Authentication errors typically require re-authentication or checking API key validity.
To resolve these issues:
- Verify the table and field names are correct and accessible.
- Ensure search criteria values match expected data types or enable loose type validation.
- Confirm OAuth2 credentials are valid and have necessary permissions.
Links and References
- EAVFW Environment Documentation (Replace with actual URL if available)
- OAuth2 Authentication Setup Guide in n8n: https://docs.n8n.io/credentials/oauth2/
- n8n Node Development Documentation: https://docs.n8n.io/integrations/creating-nodes/