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
The node integrates with the ecoDMS document management system, allowing users to manage documents and their versions programmatically within n8n workflows. Specifically, the "Version hinzufügen" (Add Version) operation for the "Dokument" (Document) resource enables adding a new version to an existing document in ecoDMS. This is useful when you want to update or replace the content of a document while preserving its version history.
Common scenarios include:
- Automatically uploading updated files as new versions of existing documents.
- Archiving finalized document versions to prevent further changes.
- Managing document lifecycle and version control within automated workflows.
Example: After processing a file externally, you can add it as a new version to a specific document in ecoDMS, optionally locking the version to prevent further edits.
Properties
| Name | Meaning |
|---|---|
| Dokument-ID | The ID of the document to which a new version will be added. |
| Version fixieren | Boolean flag indicating whether the version should be locked after archiving (no more versions can be added). |
| Binäre Eigenschaft | The name of the binary property that contains the file data to upload as the new document version. |
Output
The node outputs an array of JSON objects representing the result of the version addition operation. Each output item typically includes metadata about the newly added document version, such as its ID, status, and any relevant ecoDMS response details.
If the node handles binary data (the new document version file), it expects the input binary property specified by the user but does not output binary data itself.
Dependencies
- Requires an active connection to an ecoDMS server via an API URL configured in the node credentials.
- Needs an API authentication token or key configured in the credentials to authorize requests.
- The node depends on the ecoDMS REST API to perform document versioning operations.
Troubleshooting
- Missing Server URL: If the ecoDMS server URL is not configured in the credentials, the node throws an error prompting to set it.
- Invalid Document ID: Providing a non-existent or incorrect document ID will cause the operation to fail; verify the document exists in ecoDMS.
- Binary Property Not Found: If the specified binary property does not exist in the input data, the node cannot upload the new version file.
- Version Lock Conflicts: Attempting to add a version to a document that has been locked (version fixed) will result in an error.
- API Errors: Network issues or invalid credentials will cause request failures; ensure connectivity and correct authentication.
Links and References
- ecoDMS Official Website
- ecoDMS API Documentation (if publicly available)
- n8n Documentation on Creating Custom Nodes