dropBoxRenameFolder Step
Description:
The DropboxRenameFolder workflow step renames a specified folder in Dropbox as part of a FlowWright process.
The step uses a configured OAuth provider to access Dropbox and allows the workflow to specify both the existing folder path and the new folder name.
The step supports:
- Selecting an OAuth provider.
- Specifying the Dropbox folder to rename.
- Specifying the new folder name.
- Renaming folders as part of workflow automation.
- Using workflow Variables in folder paths or names where supported.
- Continuing the workflow through True or False return paths.
Inputs
- selOAuthProvider - The Select OAuth provider property specifies the OAuth provider that should be used to access Dropbox.
- folderPath - The Path of the folder to be renamed property specifies the existing Dropbox folder that should be renamed.
- renamedTo - The Rename Folder to property specifies the new name for the selected Dropbox folder.
Returns
- True – The True return path can be connected to the next workflow activity when the folder rename operation succeeds.
- False – The False return path can be used for error handling or an alternative workflow path when the folder rename operation does not succeed.
Usage:
The Rename Folder step is typically placed after a workflow has completed an operation that requires a Dropbox folder to be renamed.
A typical workflow pattern is:
Prepare/Complete Dropbox Content → Rename Folder → Continue Process
For example:
Complete Project → Rename Folder → Notify User
The workflow identifies the existing Dropbox folder using the path of the folder to be renamed and provides the new folder name using Rename Folder.
A typical workflow can also use the result of the operation to determine whether processing should continue:
Rename Folder → True → Continue
Rename Folder → False → Error Handling
To use this step, you must configure the Dropbox connection in the FlowWright application. Navigate to the Integrate—Connections—OAuth page to create a new OAuth source.
A sample Dropbox connection configuration is included here for reference.
Typical Workflow Suggestions:
Rename a Project Folder
Use the step when a Dropbox folder needs to be renamed after a project reaches a particular stage.
Example:
Complete Project → Rename Folder → Continue Process
Existing folder:
/Projects/Project-1045
New folder name:
Project-1045-Completed
The workflow can rename the folder after the project is completed.
Rename a Folder After Approval
Use the step to rename a folder after an approval event.
Example:
Approval → Rename Folder → Continue Process
Existing folder:
/Requests/REQ-1045/Pending
New folder name:
Approved
This can provide a folder naming convention that reflects the workflow state.
Rename a Folder After Rejection
Use the same pattern when a workflow reaches a rejection state.
Example:
Review → Rename Folder
Existing folder:
/Requests/REQ-1045/Pending
New folder name:
Rejected
The True path can continue processing after the rename operation.
Organize Completed Documents
Use this step to rename folders after document processing is complete.
Example:
Process Documents → Rename Folder → Archive
Existing folder:
/Documents/CurrentBatch
New folder name:
ProcessedBatch
This is useful for workflows that maintain Dropbox folders by processing status.
Rename a Folder Based on Workflow Data
Use workflow-generated values when the folder name needs to reflect process information.
Example:
Get Customer Data → Rename Folder
Existing folder:
/Customers/Customer123
New folder name:
Customer123-Completed
The exact Variable reference syntax should follow the conventions supported by the FlowWright environment.
Rename a Folder After File Upload
The Rename Folder step can be used after files have been uploaded into a Dropbox folder.
Example:
Upload Files → Rename Folder → Notify User
A workflow could upload files into a working folder and rename that folder after all required files have been processed.
Rename a Folder After Document Generation
Use the step after a workflow generates documents.
Example:
Generate Documents → Upload Documents → Rename Folder
For example:
Existing folder:
/Reports/MonthlyReport
New folder name:
MonthlyReport-Completed
This provides a simple way to indicate that document generation has finished.
Handle Successful and Failed Rename Operations
Use the True and False return paths to handle the result of the rename operation.
Example:
Start → Rename Folder
True → Continue Process
**False → Log Error`
The step explicitly provides these two return values.
Rename Folders as Part of an Archive Process
Use the step when completed workflow content needs to be moved into an archive naming convention.
Example:
Complete Workflow → Rename Folder → Archive Processing
Existing folder:
/Active/Request-1045
New folder name:
Request-1045-Archived
The workflow can then continue with other archive-related activities.
Use Different Folder Names for Different Workflow States
A workflow can use different Rename Folder steps for different process outcomes.
For example:
Approved path:
Review → Rename Folder → Approved
Rejected path:
Review → Rename Folder → Rejected
This allows Dropbox folder naming to reflect the workflow outcome.
Rename a Folder Before Notification
Use the Rename Folder step before sending a notification to users.
Example:
Complete Processing → Rename Folder → Send Notification
Send the notification only after the folder rename operation completes successfully.
Example:
Let’s build and execute the “DropboxRenameFolderDef” example.
- Create a new definition named “DropboxRenameFolderDef” and open it in designer mode.
- Drag a “DropboxRenameFolder” step to the canvas.
- Connect the dots between the “Start” step and “DropboxRenameFolder” steps, as shown above.
- Select the line between the steps to configure the “Connection Properties”. The default property values are “None, True, False, Error, and Evaluate”. Depending on the step’s purpose, you can configure additional values.
- Click the “DropboxRenameFolder” step to configure its “Required” properties. Provide a name for the step. Select the “Dropbox” OAuth provider from the drop-down list. Enter the source folder path to rename. Enter the new folder name. Click the Save button. Note: Click the "AI Predict" button for the Copilot to add new process steps that match your process description.
- The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. Configure the step state and percent fields individually, as shown below. Configure the “Logging” using the following properties.
- Save the process definition, create a new instance, and execute it. Render the process instance and click the Rename Folder step to view its properties. When the workflow reaches the Rename Folder step, FlowWright uses the configured OAuth provider and folder information to perform the rename operation. Verify:
- The correct OAuth provider is selected.
- The existing Dropbox folder path is correct.
- The target folder exists.
- The new folder name is correct.
- The folder has been renamed as expected.
- The workflow follows the expected True or False path.
Tips:
- Select the correct OAuth provider before executing the workflow.
- Verify that the OAuth configuration has the required access to the Dropbox location.
- Verify that the folder specified in the Path of the folder to be renamed exists.
- Use an exact and meaningful Dropbox folder path.
- Use a clear and consistent folder naming convention.
- Test the rename operation with a representative Dropbox folder before deploying the workflow.
- Verify the renamed folder in Dropbox after execution.
- Test both the True and False workflow paths.
- Connect the False path to appropriate error handling or recovery processing.
- Verify that the new folder name is appropriate before executing the rename operation.
- Avoid unintentionally renaming a folder that is used by another workflow.
- Use consistent folder naming conventions across related workflows.
- When using dynamically generated folder names, test the resulting name with representative workflow data.
- Verify any Variables used to construct folder paths or names before the Rename Folder step executes.
- Test the workflow after changing the OAuth provider configuration.
- Test the workflow after changing the source folder path.
- Test the workflow after changing the new folder name.
- Verify the result before allowing downstream workflow activities to operate on the renamed folder.
- Consider connecting the False return path to logging or notification when a rename operation fails.
- Keep folder names understandable for users who access the Dropbox location outside the workflow.
- Avoid including unnecessary sensitive information in folder names.
- If multiple workflows operate on the same Dropbox folder structure, establish consistent naming conventions.
Definition Sample:
You may provide a sample FlowWright Process Definition demonstrating the DropboxRenameFolder step.
When importing the sample definition, verify and complete any missing configuration, including:
- OAuth provider.
- Existing Dropbox folder path.
- New folder name.
- Workflow Variable references used in folder paths or names.
- Environment-specific OAuth configuration.
- Dropbox folder availability.
- True workflow path.
- False workflow path.
- Downstream activities that reference the renamed folder.
After verifying the configuration, save the Process Definition before execution.
Click here to download the sample file.