ecoDMS icon

ecoDMS

ecoDMS-Integration für n8n

Overview

This node integrates with the ecoDMS document management system to perform searches and download documents based on specified filters. It is particularly useful for automating workflows that require retrieving documents matching certain criteria from ecoDMS, such as filtering by document type, folder, status, or custom attributes.

Typical use cases include:

  • Automatically fetching documents related to a specific project or client.
  • Downloading documents with a particular status or classification for further processing.
  • Archiving or backing up selected documents based on metadata filters.

For example, you could configure the node to search for all documents in a given folder with a status of "approved" and download up to 10 of them into your workflow for further analysis or storage.

Properties

Name Meaning
Suchfilter (searchFilters) A collection of filters to define the search criteria. Each filter includes:
- Attribut: The attribute to search by (e.g., Remark, Date, Document Type, Folder, Status, Editor, Reminder Date, Timestamp).
- Operator: The comparison operator, which varies depending on the attribute:
  • For text fields like Remark or Editor: equals (=), not equals (!=), contains (like), does not contain (!like), case-insensitive contains (ilike), case-insensitive does not contain (!ilike).
  • For document type, folder, status: equals (=), not equals (!=).
  • For date/time fields: equals (=), not equals (!=), greater than (>), greater or equal (>=), less than (<), less or equal (<=).
- Wert (Value): The value to compare against. Depending on the attribute, this can be a free text input or a selectable option loaded dynamically (e.g., document types, folders, status values).
Binäre Eigenschaft (binaryProperty) The name of the binary property where the downloaded documents will be stored within the node's output data. This allows subsequent nodes to access the actual file content. Default is "data".
Maximale Anzahl Dokumente (maxDocuments) Maximum number of documents to download. Limited to 100 for performance reasons. Default is 10.

Output

The node outputs an array of items, each representing a downloaded document matching the search criteria. Each item contains:

  • A json field with metadata about the document (such as its attributes and identifiers).
  • A binary property (named as per the binaryProperty input) containing the actual document file data, enabling downstream nodes to process or save the files.

This structure allows easy integration with other n8n nodes for further automation, such as uploading files to cloud storage or sending via email.

Dependencies

  • Requires connection to an ecoDMS server, configured via credentials that must include the server URL and authentication details (e.g., API key or token).
  • The node depends on ecoDMS API endpoints to perform searches and download documents.
  • Dynamic options for filters (document types, folders, statuses) are loaded via helper methods calling ecoDMS APIs.

Troubleshooting

  • Server URL Not Configured: If the server URL is missing in the credentials, the node will throw an error indicating it is not configured. Ensure the ecoDMS server URL is correctly set in the credential configuration.
  • Unsupported Resource or Operation: If an unsupported resource or operation is selected, the node will throw an error specifying the unsupported resource.
  • Performance Limits: The maximum number of documents to download is capped at 100 to avoid performance issues. Requesting more may cause errors or slow execution.
  • Filter Misconfiguration: Incorrect filter attributes or operators may result in no documents found or API errors. Verify that filters match the expected attribute types and valid operators.
  • Authentication Errors: Invalid or expired credentials will prevent successful API calls. Re-authenticate or update credentials as needed.

Links and References

Discussion