Description:

The DropboxGetFile workflow step downloads a specified file from 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 Dropbox source file and the local destination path. It provides True and False return paths for subsequent workflow processing.

The step supports:

• Selecting an OAuth provider.
• Specifying the Dropbox file to download.
• Specifying the local machine path where the file should be saved.
• Downloading Dropbox files for subsequent workflow processing.
• Using workflow-generated values for source or destination paths where supported.
• Continuing the workflow through True or False return paths.

Usage:

The Download file step is typically placed when a workflow needs to retrieve a file stored in Dropbox and make it available on the local machine for subsequent workflow processing.

A typical workflow pattern is:

Dropbox File → Download File → Local Processing

For example:

Download Report → Process Report → Complete

The workflow identifies the Dropbox file using the source file path to be downloaded and specifies the local destination using the Path to save the file to the local machine.

A typical workflow can also use the result of the operation to determine whether processing should continue:

Download File → True → Continue

Download File → False → Error Handling

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:

Download a Report from Dropbox

Use the step when a workflow needs to retrieve a report stored in Dropbox.

Example:

Download File → Process Report → Complete

Dropbox source:

/Reports/MonthlyReport.pdf

Local destination:

C:\WorkflowFiles\MonthlyReport.pdf

After the download succeeds, subsequent workflow steps can process the local file.

Download a Document for Processing

Use the step to retrieve a document from Dropbox before another workflow activity processes it.

Example:

Download File → Process Document → Continue

For example:

/Documents/CustomerAgreement.pdf

can be downloaded to:

C:\WorkflowFiles\CustomerAgreement.pdf

The downloaded file can then be supplied to subsequent workflow processing.

Download a File Before a Local Operation

Use the step as a bridge between Dropbox storage and local workflow processing.

Example:

Download File → Local Processing → Generate Result

This pattern can be useful when a subsequent activity requires the file to be available on the local machine.

Download a File for Document Conversion

Use the step before a document-conversion activity.

Example:

Download File → Convert Document → Upload Result

For example:

/Documents/Input.docx

can be downloaded locally and then passed to a document-conversion step.

Download a File Before Data Extraction

Use the step when a workflow needs to retrieve a file from Dropbox before extracting information from it.

Example:

Download File → Extract Data → Process Data

The Dropbox file becomes available at the configured local destination for subsequent processing.

Download a File for Validation

Use the step before a validation or inspection operation.

Example:

Download File → Validate File → Continue

This pattern can be useful when a workflow needs to validate a document or other file stored in Dropbox.

Download a File for Archiving

Use the step when a workflow needs to retrieve a Dropbox file and place a local copy into a workflow-controlled location.

Example:

Download File → Archive Locally → Complete

Configure the local destination path to save the file to the local machine.

Download a File Before Sending It by Email

Use the step when a Dropbox file needs to be retrieved locally before being used as an email attachment.

Example:

Download File → Send Email → Complete

You can then supply the downloaded file to the subsequent email-processing activity.

Download a File and Process Its Contents

Use the step as the first stage of a file-processing workflow.

Example:

Download File → Read File → Transform Data → Save Result

This provides a simple pattern for retrieving externally stored workflow input before processing it.

Download Files Based on Workflow Data

Use workflow-generated values when the source or destination path needs to be determined dynamically.

Example:

Get Request Data → Download File → Process File

Conceptually:

/Customers/{{CustomerID}}/Document.pdf

could be downloaded to a corresponding workflow-specific local location.

The exact Variable reference syntax should follow the conventions supported by the FlowWright environment.

Handle Successful and Failed Downloads

Use the True and False return paths to handle the result of the download operation.

Example:

Start → Download File

True → Process Downloaded File

**False → Log Error`

The XML explicitly defines True and False as the two return values.

Download a File Before Uploading a Processed Version

A workflow can download a file, modify or process it, and then use another workflow step to upload the resulting file.

Example:

Download File → Process File → Upload File

This workflow pattern processes Dropbox content and creates a resulting file.

Example:

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

• Create a new definition named “DropboxGetFileDef” and open it in designer mode. 
• Drag a “DropboxGetFile” step to the canvas.
• Connect the dots between the “Start” step and “DropboxGetFile” 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 “DropboxGetFile” step to configure its “Required” properties. Provide a name for the step. Select the “Dropbox” OAuth provider from the drop-down list. Provide the source file folder path to download from. Provide the target folder path to store the file. 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 Download File step to view its properties. When the workflow reaches the Download File step, FlowWright uses the configured OAuth provider, Dropbox source path, and local destination path to download the file. Verify:
  • The correct OAuth provider is selected.
  • The Dropbox source file path is correct.
  • The source file exists in Dropbox.
  • The local destination path is correct.
  • The downloaded file is available at the configured local destination.
  • 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 source file exists in Dropbox before executing the step.
• Use an exact Dropbox source file path.
• Use a meaningful and appropriate local destination path.
• Verify that the workflow execution environment has access to the configured local destination.
• Test the download with a representative file before deploying the workflow.
• Verify the downloaded file after execution.
• Test both the True and False workflow paths.
• Connect the False path to appropriate error handling or recovery processing.
• Verify that the local destination directory is available before the step executes.
• Avoid unintentionally overwriting a local file; verify the destination-file behavior for the target FlowWright implementation.
• Use consistent local folder structures for files downloaded by related workflows.
• When using dynamically generated paths, test the resulting source and destination paths with representative workflow data.
• Verify any Variables used to construct paths before the Download File step executes.
• Test paths containing spaces or other supported special characters when they occur in the deployment environment.
• Verify that the file downloaded from Dropbox is the expected file before allowing downstream processing to continue.
• Test the workflow after changing the OAuth provider configuration.
• Test the workflow after changing the Dropbox source path.
• Test the workflow after changing the local destination path.
• Consider connecting the False return path to logging, notification, or recovery processing.
• Avoid storing downloaded sensitive files in locations that are accessible to unintended users or processes.
• If several workflows download files to the same local location, establish consistent naming and directory conventions.

Definition Sample:

You may provide a sample FlowWright Process Definition demonstrating the DropboxGetFile step.

When importing the sample definition, verify and complete any missing configuration, including:

• OAuth provider.
• Dropbox source file path.
• Local destination file path.
• Workflow Variable references used in source or destination paths.
• Environment-specific OAuth configuration.
• Dropbox file availability.
• Local destination directory availability.
• True workflow path.
• False workflow path.
• Downstream activities that consume the downloaded file.

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

Click here to download the sample file.