Actions26
- Archiv Actions
- Dokument Actions
- Dokument herunterladen
- Dokument mit Klassifikation herunterladen
- Dokumentversion herunterladen
- Dokumentinformationen abrufen
- Dokument hochladen
- Dokument mit PDF hochladen
- Templates für Datei abrufen
- Duplizierungscheck durchführen
- Version mit PDF hinzufügen
- Version hinzufügen
- Klassifikation mit Template-Erkennung abrufen
- Dokumenttyp Actions
- Klassifikation Actions
- Suche Actions
- Ordner Actions
Overview
This node integrates with the ecoDMS document management system, enabling users to manage and interact with documents and related resources. Specifically, the "Dokumentversion herunterladen" (Download Document Version) operation allows users to download a specific version of a document stored in ecoDMS. This is useful for workflows that require retrieving historical or current versions of documents for processing, archiving, or review.
Practical examples include:
- Automatically downloading the latest or a specific version of a contract document for further automated analysis.
- Retrieving archived versions of documents for compliance audits.
- Integrating document retrieval into broader automation workflows, such as sending documents via email or uploading them to other systems.
Properties
| Name | Meaning |
|---|---|
| Dokument-ID | The ID of the document whose version should be downloaded. |
| Version | The version number of the document to download. |
| Mit Klassifikation | Boolean flag indicating whether to use an additional classification ID when downloading. |
| Klassifikations-ID | The classification ID of the document; required if "Mit Klassifikation" is true. |
| Binäre Eigenschaft | The name of the binary property where the downloaded data will be stored in the output item. |
Output
The node outputs the downloaded document version as binary data attached to the specified binary property name (default: data). The binary data represents the actual content of the requested document version, which can then be used in subsequent workflow steps, such as saving to disk, sending via email, or further processing.
The JSON output fields typically contain metadata about the document version, but the main payload is the binary data holding the document file content.
Dependencies
- Requires connection to an ecoDMS server, configured via credentials that must include the server URL and authentication token/API key.
- The node depends on the ecoDMS API being accessible and properly authenticated.
- No additional external services are required beyond ecoDMS itself.
Troubleshooting
- Server URL not configured: If the server URL is missing in the credentials, the node will throw an error instructing to configure it.
- Unsupported resource or operation: Selecting a resource or operation not supported by the node will result in an error.
- Invalid document or version IDs: Providing incorrect or non-existent document IDs or version numbers may cause the API call to fail.
- Classification ID required: If "Mit Klassifikation" is enabled but no classification ID is provided, the node will likely error out.
- Network or authentication issues: Failures connecting to the ecoDMS server due to network problems or invalid credentials will cause errors.
To resolve these issues:
- Ensure credentials are complete and correct.
- Verify document and version IDs exist in ecoDMS.
- Provide classification ID if classification usage is enabled.
- Check network connectivity and API access permissions.
Links and References
- ecoDMS Official Website
- ecoDMS API documentation (if available from your ecoDMS installation or vendor)
- n8n Documentation on Creating Custom Nodes (for general understanding of node development)