Description:

The DropboxDeleteFile workflow step deletes the specified file in Dropbox.

The step supports:

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

Usage:

The DropboxDeleteFile step is typically placed after a workflow has finished processing a Dropbox file and the file is no longer required.

A typical workflow pattern is:

Process Dropbox File → Delete File → Continue Process

The file path can represent a fixed Dropbox location or, where supported by the workflow configuration, a value supplied by the workflow.

The resulting True/False paths can then be used to continue processing or handle the alternative result.

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 Files

Use the step to remove files that were uploaded or created for temporary workflow processing.

Example:

Upload Temporary File
        ↓
Process File
        ↓
Delete File
        ↓
Continue Workflow

Clean Up Processed Files

Use DropboxDeleteFile after a file has been successfully processed.

Example:

Retrieve File
      |
      v
Process File
      |
      v
Generate Result
      |
      v
Delete File

Delete a File After Successful Migration

A workflow can process or transfer a Dropbox file to another destination and then delete the original file.

Example:

Read Dropbox File
       |
       v
Transfer File
       |
       v
Delete Original File
       |
       v
Continue

Delete Temporary Integration Files

Use the step when a Dropbox file is used as an intermediate file for an integration.

Example:

Create Integration File
        |
        v
Send to External System
        |
        v
Delete File
        |
        v
Complete

Clean Up Generated Documents

A workflow that generates temporary documents in Dropbox can remove the generated file after it has been delivered or consumed by another process.

Example:

Generate Document
       |
       v
Store in Dropbox
       |
       v
Deliver Document
       |
       v
Delete File

Delete a File After Archival

Use the step as part of a workflow that moves or archives a file and subsequently removes the original file when the workflow reaches the appropriate cleanup stage.

Example:

Identify File
      |
      v
Archive/Move File
      |
      v
Delete Original
      |
      v
Complete

Conditional File Cleanup

Place the step after a decision when the file should be deleted only under a particular workflow condition.

Example:

Process File
     |
     v
  Decision
   /    \
 Yes     No
  |       |
  v       v
Delete   Keep
 File    File

Delete Files After Successful Delivery

Use DropboxDeleteFile after successfully delivering the file to another application, user, or integration endpoint.

Example:

Read File
   |
   v
Process File
   |
   v
Send File
   |
   v
Delete File
   |
   v
Complete

Handle the Delete Result

The step provides both True and False return paths, allowing the workflow to handle the returned result separately.

Example:

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

Delete a File as Part of Workflow Cleanup

Use the step near the end of a workflow to remove files that are no longer required.

Example:

Retrieve Data
      ↓
Generate File
      ↓
Process File
      ↓
Delete File
      ↓
Complete Workflow

Use a Workflow-Supplied File Path

The Path to delete file input is a string property. This allows the workflow design to provide a file path through the configured step input where supported.

For example:

Identify File
     |
     v
Determine File Path
     |
     v
DropboxDeleteFile

Example:

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

• Create a new definition named “DropboxDeleteFileDef” and open it in designer mode. 
• Drag a “DropboxDeleteFile” step to the canvas.
• Connect the dots between the “Start” step and “DropboxDeleteFile” 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 “DropboxDeleteFile” step to configure its “Required” properties. Provide a name for the step. Select the “Dropbox” OAuth provider from the drop-down list. Enter the file path to delete. Click the Save button. Note: Click the "AI Predict" button to have Copilot 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 Delete File step to view its properties. When the workflow reaches the Delete File step, FlowWright uses the configured OAuth provider and file path for the Dropbox operation. The step provides the True and False return paths for subsequent workflow processing. Verify:
  • The configured OAuth provider.
  • The target Dropbox file path.
  • The workflow execution result.
  • The downstream workflow path.
  • The state of the target Dropbox file after execution.

Tips:

• Verify that the correct OAuth provider is selected.
• Verify that the Path to delete file points to the intended Dropbox file.
• Use a dedicated test file while developing the workflow.
• Test both the True and False workflow paths.
• Avoid initially testing against production files.
• Review the workflow sequence carefully before placing the deletion step.
• If the file path is dynamically determined, verify the resulting path before the delete operation executes.
• Use meaningful step names and descriptions to make cleanup activities easy to identify.
• Confirm that the file no longer needs to be retained before deleting it.
• Test the workflow after changing the OAuth configuration or file path.
• Consider connecting the False path to an appropriate handling or notification activity.
• Keep file-cleanup operations after the activities that depend on the file.
• Verify downstream workflow activities after the deletion operation.
• Test with representative file paths and workflow conditions.
• Do not assume specific Dropbox behavior such as retry handling, non-existent-file handling, authorization failure handling, or recovery behavior unless confirmed by the FlowWright implementation.

Definition Sample:

A sample definition for DropboxDeleteFile can follow the same approach as the SearchAndReplaceString documentation: import a downloadable sample definition into FlowWright, then complete it with environment-specific configuration.

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

• OAuth provider.
• Dropbox file path.
• Workflow-specific file-path values.
• Environment-specific OAuth settings.
• Downstream True workflow path.
• Downstream False workflow path.
• Any preceding file-processing activities.
• Any cleanup or error-handling activities.

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

Click here to download the sample file.