Description:

The DropboxCreateFolder workflow step creates a folder in Dropbox at the specified path.

The step supports:

• Selecting an OAuth provider for Dropbox access.
• Specifying the path where the Dropbox folder should be created.
• Using a workflow-supplied value 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 DropboxCreateFolder step is typically placed before workflow activities that need a Dropbox folder to exist.

A typical workflow pattern is:

Determine Folder → Create Folder → Store/Process Files

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

A sample Dropbox connection configuration is provided here for reference.

Typical Workflow Suggestions:

Create a Folder for Workflow Processing

Use the step to create a dedicated Dropbox folder before processing files.

Example:

Start
  |
  v
Create Folder
  |
  v
Upload Files
  |
  v
Process Files

Create a Customer-Specific Folder

A workflow can use a folder path associated with a customer or business process.

Example:

Get Customer Information
        |
        v
Determine Folder Path
        |
        v
Create Folder
        |
        v
Store Customer Documents

/Customers/AcmeCorporation

Create a Folder for Document Processing

Create a Dropbox folder before generating or uploading documents.

Example:

Start
  |
  v
Create Folder
  |
  v
Generate Documents
  |
  v
Upload Documents

Create a Temporary Processing Folder

Use the step to establish a temporary Dropbox location for intermediate workflow files.

Example:

Start
  |
  v
Create Temporary Folder
  |
  v
Upload Input Files
  |
  v
Process Files

Create an Archive Folder

Use the step when a workflow needs to establish a Dropbox location for archived documents.

Example:

Process Documents
       |
       v
Create Archive Folder
       |
       v
Move/Store Documents

Create a Folder for Each Workflow Instance

A workflow can organize generated or processed files into a dedicated Dropbox folder for each process instance.

Conceptually:

Start
  |
  v
Determine Instance Folder
  |
  v
Create Folder
  |
  v
Generate/Store Files

Create a Folder Before Uploading Files

A common pattern is to create the required folder before using another Dropbox step to upload files.

Example:

Create Folder
      |
      v
Upload File
      |
      v
Process File

Create a Folder for Integration Processing

A workflow can create a Dropbox folder before exchanging files with another system.

Example:

Start
  |
  v
Create Integration Folder
  |
  v
Generate Integration Files
  |
  v
Send/Process Files

Conditional Folder Creation

Place the step after a decision when a folder should only be created under a particular business condition.

Example:

Check Requirement
       |
       v
    Decision
     /    \
   Yes     No
    |       |
    v       v
 Create   Skip
 Folder   Creation

Handle the Create Result

The step provides True and False return paths.

Example:

                 ┌── True ──> Continue Processing
                 |
Create Folder ───┤
                 |
                 └── False ─> Handle Result

Create a Folder Before Generating Reports

A reporting workflow can create a dedicated Dropbox folder before generating and storing reports.

Example:

Collect Report Data
        |
        v
Create Report Folder
        |
        v
Generate Report
        |
        v
Store Report

Create a Folder for Batch Processing

A workflow that processes a batch of documents can create a dedicated Dropbox folder for that batch.

Example:

Identify Batch
     |
     v
Create Batch Folder
     |
     v
Upload Batch Files
     |
     v
Process Batch

Example:

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

• Create a new definition named “DropboxCreateFolderDef” and open it in designer mode. 
• Drag a “DropboxCreateFolder” step to the canvas.
• Connect the dots between the “Start” step and “DropboxCreateFolder” 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 “DropboxCreateFolder” 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 create. 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 Create folder step to view its properties. When the workflow reaches the Create 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 configured OAuth provider.
  • The target Dropbox folder path.
  • The workflow execution result.
  • The downstream workflow path.
  • The state of the target Dropbox location after execution.

Tips:

• Verify that the correct OAuth provider is selected.
• Verify that the Path to create folder points to the intended Dropbox location.
• Use a dedicated test location while developing and testing the workflow.
• Test both the True and False workflow paths.
• Use meaningful folder paths that are easy to identify.
• If the folder path is dynamically determined, verify the resulting path before the create operation executes.
• Place the folder-creation step before downstream activities that depend on the folder.
• Consider connecting the False path to appropriate handling or notification activities.
• Test the workflow after changing the OAuth configuration or folder path.
• Verify the resulting Dropbox folder after workflow execution.
• Avoid assuming a folder was created successfully just because the workflow reaches the next activity; verify the operation result.
• If the workflow may execute repeatedly, consider how repeated folder-creation requests should be handled.
• Do not assume specific Dropbox behavior when the requested folder already exists unless that behavior is confirmed by the FlowWright implementation.
• Do not assume automatic creation of missing parent folders unless this behavior is confirmed by the FlowWright implementation.
• Do not assume specific retry, authorization-error, or recovery behavior unless confirmed by the implementation.

Definition Sample:

You may download the sample definition(s) from the link provided and later import them (drag-and-drop) into your FlowWright Process Definition (XML file) or Form Definition (HTML file) page.

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

• OAuth provider.
• Dropbox folder path.
• Workflow-specific folder-path values.
• Environment-specific OAuth settings.
• Downstream True workflow path.
• Downstream False workflow path.
• Activities that depend on the newly created folder.
• Any required error-handling activities.

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

Click here to download the sample file.