Description:

The DropboxSendFile workflow step uploads a file to Dropbox as part of a FlowWright workflow. It is in the Dropbox category and appears in the workflow designer as Upload File.

The step supports:

• Selecting an OAuth provider.
• Specifying the source file to upload.
• Specifying the destination path in Dropbox.
• Uploading workflow-generated or existing files to Dropbox.
• Using the uploaded file in subsequent cloud-based processing.
• Continuing the workflow through True or False return paths.

The step uses a configured OAuth provider to establish the Dropbox connection and provides True and False return paths for subsequent workflow processing.

Usage:

The DropBoxSendFile step is typically placed after a workflow has created, received, generated, or otherwise obtained a file that needs uploading to Dropbox.

A typical workflow pattern is:

Create/Get File → Upload File → Continue Process

For example:

Generate Report → Upload File → Notify User

The source file path identifies the local or workflow-accessible file, while the destination file path identifies where to save the file in Dropbox.

The OAuth provider configuration identifies the authentication provider used by the step.

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.

Example:

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

• Create a new definition named “DropboxSendFileDef” and open it in designer mode. 
• Drag a “DropboxSendFileDef” step to the canvas.
• Connect the dots between the “Start” step and “DropboxSendFileDef” 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 “DropboxSendFile” step to configure its “Required” properties. Provide a name for the step. Select the “Dropbox” OAuth provider from the drop-down list. Provide the folder path information to create. 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 Upload File step to view its properties. When the workflow reaches the step, FlowWright uses the configured OAuth provider and source/destination paths to perform the file-upload operation. Verify:
  • The selected OAuth provider is correctly configured.
  • The source file exists and is accessible.
  • The source path identifies the intended file.
  • The Dropbox destination path is correct.
  • The uploaded file is available at the intended Dropbox location.
  • 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 access required for the intended Dropbox operation.
• Verify that the source file exists before the Upload File step executes.
• Use a meaningful source file path.
• Use a meaningful and organized Dropbox destination path.
• Test the upload with a representative file before deploying the workflow.
• Verify the uploaded file in the intended Dropbox destination.
• Test both the True and False workflow paths.
• Configure the False path for appropriate error handling when an upload fails.
• Avoid overwriting existing Dropbox files unintentionally; verify the destination-path behavior for the target FlowWright/Dropbox implementation.
• Use consistent Dropbox folder structures across related workflows.
• Use meaningful folder and file naming conventions.
• When using dynamic paths, test the generated path with representative workflow data.
• Verify that Variables referenced in source or destination paths contain the expected values before the step executes.
• Test paths containing spaces or other supported special characters when they occur in the deployment environment.
• Verify access to the source file from the server or execution environment where the workflow runs.
• Test the workflow after changing the OAuth provider configuration.
• Test the workflow after changing source or destination paths.
• Avoid placing sensitive information directly into paths unless required and appropriately protected.
• For workflows that upload several files, verify each source-to-destination mapping independently.
• Consider connecting the False path to logging, notification, or recovery processing.

Definition Sample:

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

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

• OAuth provider.
• Source file path.
• Dropbox destination path.
• Workflow Variable references used in paths.
• Environment-specific OAuth configuration.
• Source file availability.
• Dropbox folder structure.
• True workflow path.
• False workflow path.
• Downstream activities.

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

Click here to download the sample file.