Actions27
- Archiv Actions
- Dokument Actions
- Dokument herunterladen
- Dokument mit Klassifikation herunterladen
- Dokumentversion herunterladen
- Dokumentinformationen abrufen
- Dokument hochladen
- Dokument mit PDF hochladen
- PDF in Inbox hochladen
- Datei hochladen
- Templates für Datei abrufen
- Duplizierungscheck durchführen
- Version mit PDF hinzufügen
- Version hinzufügen
- Klassifikation mit Template-Erkennung abrufen
- Klassifikation Actions
- Suche Actions
- Ordner Actions
- Workflow Actions
Overview
This node integrates with the ecoDMS document management system, allowing users to manage and interact with documents and related resources. Specifically, the "Dokumentversion herunterladen" (Download Document Version) operation enables downloading 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 fetching a particular version of a contract document for compliance checks.
- Downloading archived invoices for accounting automation.
- Retrieving classified document versions based on classification IDs for audit purposes.
Properties
| Name | Meaning |
|---|---|
| Dokument-ID | The ID of the document whose version you want to download. |
| 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 enabled. |
| 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 json output field typically contains metadata about the document version or operation result, but the main content is provided as binary data suitable for further processing or saving.
Dependencies
- Requires connection to an ecoDMS server, configured via credentials including the server URL and API authentication token.
- The node depends on the ecoDMS API being accessible and properly authenticated.
- No other external services are required beyond the ecoDMS API.
Troubleshooting
- Server URL not configured: The node throws an error if the ecoDMS server URL is missing in the credentials. Ensure the server URL is correctly set in the node's credential configuration.
- Unsupported resource error: If an unsupported resource is selected, the node will throw an error indicating the resource is not supported.
- API errors: Errors from the ecoDMS API (e.g., invalid document ID, version not found, or classification ID issues) will be surfaced as node operation errors. Verify input parameters and permissions.
- Binary property conflicts: Ensure the binary property name used does not conflict with existing properties in the workflow to avoid overwriting data unintentionally.
Links and References
- ecoDMS Official Website
- ecoDMS API Documentation (if publicly available)
- n8n Documentation on Creating Custom Nodes