EAVFW

EAVFW node description

Overview

This node integrates with an external EAVFW API to create new records in specified tables. It is designed for scenarios where users need to programmatically insert data into a structured database exposed via the EAVFW service, such as CRM systems, inventory management, or custom business applications.

Typical use cases include:

  • Automating data entry by creating records based on input from other workflows.
  • Synchronizing data from external sources into the EAVFW-managed system.
  • Bulk inserting multiple records with dynamic field values.

For example, a user could create a new customer record by specifying the target table and setting fields like name, email, and phone number dynamically within an n8n workflow.

Properties

Name Meaning
Table The target table (entity) in which to create a new record. Options are dynamically loaded from the API manifest.
Fields A collection of fields to set on the new record. Each field includes:
- Field Name: The specific field in the selected table to populate (dynamically loaded based on the chosen table).
- Value: The value to assign to that field. Multiple fields can be set per record.

Output

The node outputs an array of JSON objects, each representing the result of a record creation attempt:

  • success: Boolean indicating if the record was created successfully.
  • data: The response data returned from the API after creating the record, typically including the created record's details.
  • fields: The list of fields and their values that were sent in the request.
  • table: The name of the table where the record was created.
  • payload: The processed data object sent to the API, with field names mapped to their logical names and values converted to appropriate types.

If an error occurs during record creation and "Continue On Fail" is enabled, the output will contain:

  • success: false
  • error: Error message describing what went wrong.
  • payload and response: Additional error context if available.

The node does not output binary data.

Dependencies

  • Requires an OAuth2 API credential configured with client ID, client secret, and token URL to authenticate requests.
  • Connects to the EAVFW API at https://quizzical-chebyshev-000.env.medlemscentralen.dk/api/.
  • Uses the /manifest endpoint to dynamically load available tables and fields.
  • Sends POST requests to /entities/{collectionSchemaName}/records to create records.

Troubleshooting

  • Invalid Table or Field Names: If the specified table or field does not exist in the API manifest, the node throws an error. Ensure the table and fields are correctly selected from the dropdowns populated by the API.
  • Invalid GUID Format for Lookup Fields: Lookup fields require values in GUID format. Providing an invalid GUID will cause an error.
  • Authentication Failures: Errors during OAuth2 token retrieval indicate misconfigured credentials or incorrect client ID/secret/token URL.
  • Type Conversion Errors: Values are automatically converted based on field type (integer, decimal, boolean, datetime). Providing incompatible values may cause errors.
  • API Connectivity Issues: Network problems or API downtime will cause request failures.
  • To handle errors gracefully, enable "Continue On Fail" so the workflow can proceed even if some records fail to be created.

Links and References

Discussion