Actions13
- File/Folder Actions
- File Actions
- Folder Actions
- Share Actions
Overview
The node provides operations to manage files and folders within a Twake Drive instance. Specifically, the Move File operation moves a targeted file from its current directory to another specified directory. This is useful for organizing files dynamically based on workflow logic, such as archiving processed files, sorting uploads into project-specific folders, or restructuring storage.
Practical examples:
- Automatically move newly uploaded files into client-specific folders.
- Reorganize files after processing by moving them to an archive directory.
- Move files between team folders based on status changes in a project management workflow.
Properties
| Name | Meaning |
|---|---|
| File ID | ID of the targeted file to be moved. |
| Choose Destination Folder | Boolean flag to specify whether to select a custom destination folder. |
| Directory ID | ID of the destination directory where the file will be moved (required if above is true). |
Output
The node outputs JSON data representing the result of the move operation. Typically, this includes metadata about the moved file such as its new location, updated timestamps, and identifiers. The exact structure depends on the API response but generally confirms success and details of the moved file.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Twake Drive API.
- Needs the Twake Drive instance URL configured in the credentials.
- The node uses HTTP requests to interact with the Twake Drive REST API endpoints.
Troubleshooting
Common issues:
- Invalid or missing File ID: Ensure the file ID provided exists and is accessible.
- Incorrect Directory ID: The destination directory must exist; otherwise, the move will fail.
- Insufficient permissions: The API token must have rights to move files within the Twake Drive instance.
- Network or authentication errors: Verify API credentials and network connectivity.
Error messages:
- "File not found" or similar indicates the File ID is invalid.
- "Destination directory not found" means the Directory ID is incorrect or inaccessible.
- Authentication errors suggest invalid or expired API tokens.
To resolve these, double-check input IDs, ensure proper API credentials are set up, and confirm the user has necessary permissions in Twake Drive.
Links and References
- Twake Drive API Documentation (for detailed API endpoint info)
- n8n Documentation on Credentials (for setting up API keys)
- n8n Node Development Guide (for understanding node properties and execution)