Overview
The node "EAVFW" is designed to create records in a specified table within the EAVFW environment. It allows users to input data either through a field builder interface, where individual fields and their values are specified, or by providing a raw JSON payload that matches the logical field names defined in the system's manifest.
This node is beneficial in scenarios where automated creation of structured records is needed, such as integrating form submissions, syncing data from other systems, or batch importing data into the EAVFW platform.
Practical examples:
- Creating a new customer record by specifying fields like name, email, and phone number.
- Importing complex nested data structures by sending a JSON payload directly.
- Automating data entry workflows where the source data format varies between simple key-value pairs and full JSON objects.
Properties
| Name | Meaning |
|---|---|
| Table | The target table in which to create the record. Options are dynamically loaded from available tables. |
| Input Type | Method to input data: - Field Builder: Specify individual fields and their values. - JSON: Provide a JSON payload matching the table's schema. |
| Fields | (Shown if Input Type is Field Builder) A collection of fields to set on the new record. Each entry includes: - Field Name: The specific field in the table. - Value: The value to assign to that field. |
| JSON Payload | (Shown if Input Type is JSON) Raw JSON object representing the record to create. Field names must match the logical names from the manifest. |
Output
The node outputs the created record(s) in the json output field. This typically contains the newly created record's data as returned by the EAVFW environment, reflecting the fields and values stored.
If binary data were involved, it would be summarized here, but this node focuses on JSON data representing records.
Dependencies
- Requires an API authentication token credential for the EAVFW environment.
- Depends on dynamic loading methods to fetch available tables and fields (
getTables,getFields). - No additional external services beyond the configured EAVFW API connection.
Troubleshooting
- Common issues:
- Selecting a table without proper permissions may cause authorization errors.
- Providing invalid field names or mismatched JSON structure can lead to validation errors.
- Empty or malformed JSON payloads will result in request failures.
- Error messages:
- Authorization errors indicate missing or invalid API credentials; verify and update the API key/token.
- Validation errors usually specify which field caused the problem; ensure field names and types match the table schema.
- Network or timeout errors suggest connectivity issues with the EAVFW API endpoint.
Links and References
- Refer to the EAVFW platform documentation for details on table schemas and field definitions.
- Consult the n8n documentation on creating custom nodes and using fixed collections for more context on property configurations.