ecoDMS icon

ecoDMS

ecoDMS-Integration für n8n
Join our community

Actions26

Overview

The node integrates with the ecoDMS document management system, specifically enabling classification of inbox documents. The "Inbox-Dokument klassifizieren" operation allows users to classify a document from the inbox by specifying its document ID and providing classification fields in JSON format. This is useful for automating document organization, metadata tagging, and categorization within ecoDMS.

Practical examples include:

  • Automatically classifying scanned invoices or receipts as they arrive in the inbox.
  • Tagging incoming contracts with relevant metadata for easier retrieval.
  • Updating document classifications based on workflow triggers.

Properties

Name Meaning
Dokument-ID The ID of the inbox document to be classified.
Felder Classification fields provided as a JSON object. These define the metadata or tags to apply to the document.

Output

The node outputs an array of JSON objects representing the result of the classification operation. Each output item typically contains information about the classified document, such as confirmation of successful classification or updated document metadata.

If the node supports binary data output (not explicitly shown here), it would represent associated files or attachments related to the document.

Dependencies

  • Requires an active connection to an ecoDMS server via an API key credential.
  • The server URL must be configured in the node credentials.
  • The node depends on ecoDMS API endpoints for document classification.
  • No additional external services are required beyond ecoDMS.

Troubleshooting

  • Error: "Server-URL ist nicht konfiguriert."
    This indicates that the ecoDMS server URL is missing in the credentials configuration. To fix, provide the correct server URL in the node's API credential settings.

  • Unsupported Resource Error
    If a resource other than those supported by the node is selected, an error will be thrown. Ensure the resource is set to "Klassifikation" for this operation.

  • Invalid Document ID or Fields
    Providing an incorrect document ID or malformed JSON in the classification fields may cause API errors. Verify the document exists and the JSON structure matches ecoDMS expectations.

  • API Connectivity Issues
    Network problems or invalid API keys can prevent communication with ecoDMS. Confirm network access and credential validity.

Links and References

Discussion