The Dropbox Move Item action is used to move a file or folder located on Dropbox from the specified source (fromPath) to a new destination (toPath). It is highly functional in file management, folder organization, and user-specific archiving scenarios.
Technical Specifications
Function: Moves a file or folder from one location to another.
Parameters
settings (Object – required): Dropbox API connection settings.
fromPath (String – required): The current path of the file or folder to be moved (e.g., /Documents/file.pdf).
toPath (String – required): The destination path of the file or folder to be moved (e.g., /Archive/file.pdf).
Result: Singular (One) → Returns the new path information of the moved item.
Value Binding
Fixed Value: Specific file paths can be entered manually.
Dynamic value: Can be automatically retrieved from user selections or the in-app file path.
fromPath: Enter the current path of the file/folder to be moved.
toPath: Enter the destination path to which the file/folder will be moved.
Enable Audit Logs: When enabled, user delegation update operations are added to audit log records. This allows you to track which records were updated, in which fields, when, and by which user.
Execution
When the action is executed, the file/folder is moved to the specified new location.
The returned result contains the new path information of the moved item.
Usage Scenario: “Move Documents to Archive”
When a user wants to move their active documents from the ‘Documents’ folder to the “Archive” folder:
fromPath = /Documents/report.pdf
toPath = /Archive/report.pdf
Action runs → File is moved to the “Archive” folder.
Dropbox Move Item Advanced Customizations
Batch Move: The user can select multiple files and trigger sequential move operations.
Dynamic Path Determination: The file or folder path selected from the user interface can be automatically linked.
Folder Configuration: New folders can be created and automatically checked before moving.
Technical Risks and Controls
If incorrect or incomplete fromPath is provided, the operation will fail.
If toPath conflicts with an existing file path, the old file may be overwritten → control should be added.
API quota limits and authorization errors should be considered.