Overview
The node "EAVFW" is designed to interact with the EAVFW environment, specifically allowing users to create records in specified tables. It supports two input methods for record creation: a field builder interface where individual fields and their values can be set, or a raw JSON payload that matches the logical field names defined in the manifest.
This node is beneficial when automating data entry into an EAVFW system, such as creating new entities or records programmatically based on workflow data. For example, it can be used to add new customer records, log entries, or any structured data that the EAVFW environment manages.
Properties
| Name | Meaning |
|---|---|
| Table | The target table in which to create the new record. Options are dynamically loaded from the EAVFW system. |
| Input Type | Method of providing data for the new record. Options: "Field Builder" (set fields individually) or "JSON" (provide full JSON payload). |
| Fields | When using "Field Builder", this collection allows specifying multiple fields by name and their corresponding values to set in the new record. Field names are dynamically loaded based on the selected table. |
| JSON Payload | When using "JSON" input type, this is the raw JSON object representing the record to create. Field names must match the logical names defined in the manifest. |
Output
The node outputs the result of the record creation operation in its json output field. This typically includes details about the newly created record, such as its unique identifier and any other metadata returned by the EAVFW environment. The exact structure depends on the API response but generally confirms successful creation and provides access to the created entity's data.
No binary data output is indicated.
Dependencies
- Requires an OAuth2 API credential configured for authenticating with the EAVFW environment.
- Depends on dynamic loading methods (
getTables,getFields) to populate selectable options for tables and fields. - The node uses bundled internal modules for routing and method implementations specific to EAVFW.
Troubleshooting
- Authentication errors: Ensure the OAuth2 credentials are correctly set up and valid.
- Invalid table or field names: Selecting a table or fields not present in the EAVFW environment will cause errors. Use the provided dynamic options to avoid this.
- Malformed JSON payload: When using the JSON input type, ensure the JSON is well-formed and field names exactly match those expected by the EAVFW manifest.
- Empty required fields: Required properties like "Table" must be set; otherwise, the node will fail to execute properly.
Links and References
- Refer to the official EAVFW API documentation for detailed information on table schemas and field definitions.
- OAuth2 setup guides within n8n documentation for configuring authentication credentials.