Overview
This node integrates with OnlyOffice to manage files and folders via its API. Specifically, the File - Move operation allows users to move a file from one folder to another within their OnlyOffice environment. This is useful for organizing documents, automating file management workflows, or restructuring project directories programmatically.
For example, you might use this node to automatically move a report file into an "Archived Reports" folder after it has been finalized, or to reorganize files based on metadata or workflow status.
Properties
| Name | Meaning |
|---|---|
| Item ID | The unique identifier of the file to move. |
| Destination Folder ID | The unique identifier of the folder where the file will be moved to. |
| Conflict Resolution | How to handle conflicts if a file with the same name exists in the destination folder: - Skip (do not move) - Overwrite (replace existing file) - Duplicate (create a copy with a new name) |
Output
The output JSON contains the response from the OnlyOffice API after attempting to move the file. Typically, this includes details about the moved file or an error message if the operation failed.
The structure generally reflects the updated file metadata such as its new location, ID, title, and other relevant attributes returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for OnlyOffice with appropriate permissions to manage files.
- The node uses the OnlyOffice API base URL configured in the credentials.
- Network access to the OnlyOffice API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing
Item IDorDestination Folder IDwill cause the API call to fail. - Insufficient permissions in the API key may result in authorization errors.
- Conflicts during move operations if conflict resolution is set to "Skip" and a file with the same name exists.
- Invalid or missing
Error messages:
"Unknown file operation: move"— indicates an internal misconfiguration; ensure the operation parameter is correctly set.- API errors related to invalid IDs or permissions will be passed through; verify that the IDs exist and the API key has required scopes.
Resolutions:
- Double-check input IDs for correctness.
- Confirm API credentials have file management rights.
- Adjust conflict resolution setting according to desired behavior.
Links and References
- OnlyOffice API Documentation
- n8n documentation on Creating Custom Nodes