Description:

The DropboxDeleteFolder workflow step deletes the specified folder in Dropbox.

The step supports:

• Selecting an OAuth provider for Dropbox access.
• Specifying the Dropbox folder path to delete.
• Using workflow-provided values for the folder path where applicable.
• Returning a True or False result for subsequent workflow processing.
• Connecting different workflow paths based on the returned result.

Usage:

The DropboxDeleteFolder step is typically placed after the workflow has finished processing the contents of a Dropbox folder and the folder is no longer required.

A typical workflow pattern is:

Process Dropbox Folder → Delete Folder → Continue Process

The step can be used after activities that:

• Process files stored in a Dropbox folder.
• Move or copy documents to another location.
• Complete a document-processing operation.
• Complete a temporary workflow operation.
• Determine that a Dropbox folder is no longer required.

To use this step, you must configure the Dropbox connection in the FlowWright application. To do so, go to Integrate > Connections > OAuth and create a new OAuth source. 

A sample Dropbox connection configuration is provided here for reference.

Typical Workflow Suggestions:

Delete Temporary Dropbox Folders

Use the step to remove a Dropbox folder that was created or used for temporary workflow processing.

Example:

Create/Use Temporary Folder → Process Files → Delete Folder

Clean Up Completed Processing Folders

Use the step after a workflow has completed processing the documents in a Dropbox folder.

Example:

Process Documents → Generate Output → Delete Folder

Delete a Folder After Document Migration

Use the step after documents have been transferred from a Dropbox folder to another destination.

Example:

Read Dropbox Folder → Migrate Documents → Delete Folder

Clean Up Temporary Documents

Use the step as part of a cleanup stage after temporary documents have been processed.

Example:

Generate Temporary Documents
          ↓
      Process Files
          ↓
      Delete Folder
          ↓
    Continue Workflow

Conditional Folder Cleanup

The step can be placed after a decision so that the folder is deleted only when the workflow reaches the appropriate branch.

Example:

Validate Processing
        |
        v
     Decision
      /    \
    Yes     No
     |       |
     v       v
 Delete    Keep
 Folder    Folder

Delete an Archived Processing Folder

A workflow can use the step when a business process has determined that a Dropbox folder is no longer required.

For example:

Identify Folder
      |
      v
Verify Processing Complete
      |
      v
Delete Folder

Delete a Folder After Successful Delivery

Use the step after documents have been successfully delivered to another system or destination.

Example:

Process Documents
      |
      v
Send Documents
      |
      v
Delete Folder
      |
      v
Complete Process

Use Workflow Values for the Folder Path

The Path to delete folder input is a string property, so the workflow can be designed around a folder path supplied by the process configuration or workflow context where supported.

For example:

Identify Folder
      |
      v
Path to delete folder
      |
      v
DropboxDeleteFolder

Handle the Delete Result

The step provides both True and False return paths.

Example:

                 ┌── True ──> Continue Process
                 |
Delete Folder ───┤
                 |
                 └── False ─> Handle Result

Clean Up After Workflow Processing

The step can serve as the final cleanup activity in a workflow:

Retrieve Documents
       ↓
Process Documents
       ↓
Generate Results
       ↓
Delete Folder
       ↓
Complete

Example:

Let’s build and execute the “DropboxDeleteFolderDef” example.                 

• Create a new definition named “DropboxDeleteFolderDef” and open it in designer mode. 
• Drag a “DropboxDeleteFolder” step to the canvas.
• Connect the dots between the “Start” step and “DropboxDeleteFolder” 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 “DropboxDeleteFolder” step to configure its “Required” properties. Provide a name for the step. Select the “Dropbox” OAuth provider from the drop-down list. Enter the folder path to delete. 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 process step to view its properties. When the workflow reaches the Delete Folder step, FlowWright uses the configured OAuth provider and folder path for the Dropbox operation. The step provides the True and False return paths for subsequent workflow processing. Verify the workflow result and the state of the target Dropbox folder after execution.

Tips:

• Verify that the correct OAuth provider is selected before executing the workflow.
• Verify that the Path to delete folder points to the intended Dropbox folder.
• Use a dedicated test folder when developing and testing the workflow.
• Test the workflow with the True return path.
• Test the workflow with the False return path and verify the configured alternative handling.
• Avoid using production folders while initially testing the step.
• Review the workflow sequence carefully before placing the deletion step after automated processing.
• If the folder path is dynamically generated, verify the resulting path before the delete operation executes.
• Use meaningful workflow activity names so that folder-cleanup operations are easy to identify.
• Consider whether the folder needs to be retained before automatically deleting it.
• Verify downstream activities after the deletion operation.
• Test the workflow after changing the OAuth configuration or folder path.
• Keep cleanup operations separate from critical processing activities where possible.
• Do not assume specific Dropbox behaviors such as recursive deletion, automatic handling of non-existent folders, retry behavior, or authorization failure handling unless confirmed by the FlowWright implementation.

Definition Sample:

You may provide a sample DropboxDeleteFolder process definition for users to download and import into their FlowWright Process Definition page, following the same approach used in the SearchAndReplaceString documentation. The reference documentation instructs users to verify missing configuration after importing a sample, including workflow-specific settings and downstream paths.

After importing a sample, verify and complete any required configuration, including:

• OAuth provider.
• Dropbox folder path.
• Workflow-specific folder-path values.
• Environment-specific OAuth configuration.
• Downstream True workflow path.
• Downstream False workflow path.
• Any preceding processing or validation activities.

After verifying the configuration, save the Process Definition before execution.

Click here to download the sample file.