Actions14
- File/Folder Actions
- File Actions
- Folder Actions
- Share Actions
Folder → Move Folder
AI-generatedOverview
This node operation moves a folder from a source location to a destination location within Twake Drive. It supports selecting the source and destination folders either via a dropdown browse interface or by manually specifying folder IDs. This operation is useful for organizing files and folders by relocating them within the Twake Drive storage hierarchy.
Use Case Examples
- Moving a project folder from one department's directory to another to keep files organized.
- Relocating a shared folder to a different parent folder to update access permissions or structure.
Properties
| Name | Meaning |
|---|---|
| File Select Mode | Determines how the source folder is selected, either by browsing a dropdown list or by manually entering the folder ID. |
| Target Folder (Source) Name or ID | The source folder to move, selected from a dropdown list or specified by ID if file select mode is dropdown. |
| Source Folder ID (Manual) | The source folder ID specified manually when file select mode is 'By ID (Manual)'. |
| Destination Select Mode | Determines how the destination folder is selected, either by browsing a dropdown list or by manually entering the folder ID. |
| Parent Folder (Destination) Name or ID | The destination parent folder where the source folder will be moved, selected from a dropdown list or specified by ID if destination select mode is dropdown. |
| Destination Folder ID (Manual) | The destination folder ID specified manually when destination select mode is 'By ID (Manual)'. |
Output
JSON
json- The JSON output contains the result of the move folder operation, typically including metadata about the moved folder such as its new location and identifiers.
Dependencies
- Requires OAuth2 API credentials for Twake Drive to authenticate and authorize folder operations.
Troubleshooting
- Common issues include invalid folder IDs or insufficient permissions to move folders, which may result in error messages indicating access denied or folder not found.
- Errors may also occur if the source or destination folder does not exist or if the node parameters are incorrectly configured (e.g., mismatched select modes).
- To resolve errors, verify folder IDs, ensure the OAuth2 credentials have appropriate permissions, and confirm the folder paths exist.