Description:

Upload File enables a FlowWright workflow to upload a source file to Box using a configured OAuth provider, a specified Box destination path or folder ID, and a Variable or Global variable to store the operation result. 

The Upload File workflow step uploads a file from a specified source location to a destination in Box.

The step supports:

• Selecting an OAuth provider for the Box operation.
• Specifying the source file path to upload.
• Specifying a Box destination path or folder ID.
• Storing the operation result in a Variable or Global variable.
• Continuing the workflow through the True return path when the operation succeeds.
• Using the False return path for an alternative workflow path or error handling.

Usage:

The Upload File step is typically placed after a workflow has generated, retrieved, or otherwise obtained a file that needs to be uploaded to Box.

The workflow supplies the OAuth provider, source file path, and Box destination. The upload result is then stored in the configured Variable or Global variable.

A typical workflow pattern is:

Generate/Retrieve File → Upload File → Continue Process

The resulting value can then be used by later workflow steps to:

• Record the result of the upload.
• Continue document-processing activities.
• Trigger subsequent workflow processing.
• Log or process the Box upload result.
• Route the workflow through success or failure paths.

To use this step, you must first configure Dropbox in FlowWright. Then, go to the Integrate > Connections > OAuth page to create a new OAuth source. 

A sample OAuth configuration is provided for reference. 

Typical Workflow Suggestions:

Upload a Generated Report to Box

Use this step after a workflow generates a report that needs to be stored in Box.

Example:

Generate Report → Upload File → Notify User

The generated report path is the source file, and the desired Box folder is the destination.

Archive Workflow Documents in Box

Use this step to upload workflow-generated documents to a designated Box location.

Example:

Create Document → Upload File → Complete Process

The workflow can use a configured Box folder or Folder ID as the destination for the document.

Upload a Form Attachment to Box

Use this step when a workflow needs to transfer a file obtained from another workflow activity into Box.

Example:

Get Form Attachment → Upload File → Process Result

You can supply the retrieved attachment as the source file, and store the upload result in a Variable or Global variable.

Store Files in Different Box Folders

Use this step when the workflow determines the appropriate Box destination based on process information.

Example:

Determine Destination → Upload File → Continue Process

The destination path or Folder ID can be supplied dynamically through workflow data.

Route Processing After a Box Upload

Use the True and False return paths to control processing after attempting to upload a file.

Example:

Upload File → True: Continue Process / False: Handle Upload Failure

The success path can continue downstream processing, while the False path can connect to appropriate error-handling or notification activities.

Example

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

• Create a new process definition named “BoxSendFileDef” and open it in designer mode. 
• Drag a “BoxSendFile” step to the canvas.
• Connect the dots between the “Start” and “BoxSendFile” step 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.
• Define a variable or a global to store the result.
• Click the "BoxSendFile" step to configure its "Required" properties. Provide a name for the step. Select the “Box” OAuth connection provider. Specify the source file path to upload. Specify the target folder path. Specify a variable or global reference to store the result after execution. Click the Save button. Note: Click the "AI Predict" button for 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. This is achieved by configuring the step state and percent fields individually, as shown below. Configure the “Logging” using the following properties.

• Save the Process Definition, create a new process instance, and execute it. When the workflow reaches the Upload File step, FlowWright uses the configured OAuth provider to upload the source file to the specified Box destination. The operation result is stored in the configured Variable or Global variable. The workflow continues through the appropriate return path.

Tips:

• Configure the correct OAuth provider before executing the step.
• Verify that the source file exists and is accessible to the FlowWright process.
• Use a meaningful Box destination path or Folder ID.
• Verify that the configured destination represents the intended Box location.
• Use a meaningful Variable or Global name for the upload result.
• Test the OAuth configuration before deploying the workflow.
• Test uploads with representative file types and sizes used by the workflow.
• Connect the True path to the next activity when the upload succeeds.
• Connect the False path to appropriate error-handling or notification logic.
• Verify the stored upload result before using it in downstream activities.
• Avoid hard-coding environment-specific file paths when workflow configuration can be used.
• Test destination paths or Folder IDs carefully when deploying the workflow across environments.

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 the import, verify and complete any missing configurations, such as file path references and database connections. Then, save the definition to confirm the changes. 

Click here to download the sample file.