ecoDMS icon

ecoDMS

ecoDMS-Integration für n8n

Overview

This node integrates with the ecoDMS document management system to retrieve document classification information using template recognition. It supports two modes:

  • For a file: Classify a new file provided as binary data.
  • For an existing document: Retrieve classifications for a stored document by its ID and version.

Typical use cases include automating document categorization workflows, extracting metadata from scanned documents, or integrating ecoDMS classification results into broader automation pipelines. For example, you could upload an invoice PDF as a file and get back its classification to route it automatically to the accounting department.

Properties

Name Meaning
Modus (mode) Select whether to classify a new file ("Für Datei") or retrieve classification for an existing document ("Für bestehendes Dokument").
Binäre Eigenschaft (binaryPropertyName) The name of the binary property containing the file data to classify. Required if mode is "Für Datei". Default is "data".
Dokument-ID (docId) The numeric ID of the existing document to retrieve classifications for. Required if mode is "Für bestehendes Dokument".
Versions-ID (versionId) The version number of the existing document to retrieve classifications for. Required if mode is "Für bestehendes Dokument". Default is 1.

Output

The node outputs an array of JSON objects representing the classification results returned by ecoDMS. Each item typically contains details about the detected classification(s) and recognized templates for the document or file processed.

If the input was a file, the output reflects the classification after analyzing the binary content. If the input was an existing document, the output corresponds to the stored classification data for that document version.

No binary data is output by this operation; the output is purely JSON metadata describing classifications.

Dependencies

  • Requires connection to an ecoDMS server via its API.
  • An API authentication credential must be configured in n8n with the server URL and access token.
  • The node depends on ecoDMS services being available and accessible from the n8n environment.

Troubleshooting

  • Server URL not configured: The node will throw an error if the ecoDMS server URL is missing in credentials. Ensure the server URL is correctly set.
  • Invalid document ID or version: When retrieving classification for an existing document, providing incorrect IDs may result in errors or empty results.
  • Binary property missing or invalid: In file mode, ensure the specified binary property exists and contains valid file data.
  • Network or authentication issues: Connection failures or unauthorized errors indicate problems with API credentials or network accessibility.
  • Unsupported resource or operation: The node only supports defined resources and operations; selecting unsupported ones will cause errors.

Links and References

Discussion