Description:

The Create Folder workflow step creates a folder in OneDrive using the selected OAuth provider and the specified folder path. The operation result is stored in the specified Variable or Global variable.

The step supports:

• Selecting an OAuth provider for the OneDrive operation.
• Specifying the path at which the folder should be created.
• Storing the operation result in a Variable or Global variable.
• Returning a True or False result for subsequent workflow processing.

Usage:

Place the Create Folder step before workflow activities that need a OneDrive folder to exist.

The workflow supplies the OAuth provider and folder path, performs the folder-creation operation, and stores the resulting information in the specified Variable or Global variable.

A typical workflow pattern is:

Determine Folder Path → Create Folder → Use Folder

The newly created folder can then serve as the working location for subsequent workflow activities.

The step can be useful in workflows that:

• Create project-specific OneDrive folders.
• Organize documents by workflow instance.
• Create temporary working locations.
• Prepare folders before uploading files.
• Organize generated reports or documents.
• Create customer- or request-specific document locations.
• Establish a folder structure as part of document management.
• Route the workflow based on whether folder creation succeeds.

To use this step, you must configure OneDrive in FlowWright.

The Windows Live OAuth configuration is included here for reference. 

Typical Workflow Suggestions:

Create a Project Folder

Use the step when a workflow needs a dedicated OneDrive folder for a new project.

Example:

Start Project → Create Folder → Upload Project Documents → Continue

You can determine the folder path from project-related information.

Create a Customer-Specific Folder

Use this step to establish a dedicated folder for documents associated with a customer.

Example:

Get Customer Information → Build Folder Path → Create Folder → Upload Documents

This provides a structured location for subsequent document-processing activities.

Create a Workflow Instance Folder

Use the step to create a folder associated with an individual workflow instance.

Example:

Start Workflow → Build Instance Folder Path → Create Folder → Process Documents

A dynamic folder path lets different workflow instances work in separate OneDrive locations.

Create a Temporary Working Folder

Use the first step in a document-processing workflow to create a temporary location.

Example:

Start → Create Working Folder → Download/Upload Files → Process Files

The resulting folder can then be used by subsequent activities in the workflow.

Prepare a Folder Before Uploading Files

Create the destination folder before performing subsequent file operations.

Example:

Determine Destination → Create Folder → Upload File → Continue

This pattern is useful when the workflow needs to establish a folder before storing documents in it.

Organize Generated Reports

Use the step to create a folder for workflow-generated reports.

Example:

Generate Report Information → Create Report Folder → Save/Upload Report

The folder can provide a dedicated location for the resulting reports.

Create Folders for Document Processing

Use this step to establish a predictable location for documents involved in a workflow.

Example:

Receive Request → Create Document Folder → Process Documents → Complete

This can make the workflow's document organization easier to maintain.

Create an Archive Folder

Use this step before moving or uploading completed documents into an archive structure.

Example:

Complete Processing → Create Archive Folder → Archive Documents → Complete

The surrounding workflow determines the appropriate archive path.

Build a Folder Structure Dynamically

Construct the folder path from workflow information before executing the Create Folder step.

Example:

Get Request Details → Build Folder Path → Create Folder → Upload Documents

This lets one workflow definition create folders for different requests, projects, or instances.

The XML defines Path to create folder as a required string property, but does not specify how dynamic values are resolved or what OneDrive path syntax is supported.

Store the Creation Result

Use the resultJson property to retain the result of the folder-creation operation.

Example:

Create Folder → Store Result → Process Result

The result destination is explicitly defined as a required Variable/Global string property.

Route the Workflow Based on the Result

Use the True and False return paths to create different workflow paths.

Example:

Create Folder
→ True → Upload Files
→ False → Error Handling

The step definition provides both True and False return values.

Create a Folder as Part of a Document Lifecycle

Use the step when a new stage of a document lifecycle requires a dedicated OneDrive location.

Example:

New Request → Create Folder → Upload Source Documents → Approval → Archive

The folder can provide a consistent location throughout the workflow.

Create a Folder Before a Batch Operation

Use the step to prepare a destination for a batch of documents.

Example:

Start Batch → Create Folder → Generate Documents → Upload Documents → Complete

This provides a logical grouping for documents produced by the batch.

Example:

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

• Create a new process definition called “OneDriveCreateFolderDef” and open it in Designer mode. 
• Drag a “OneDriveCreateFolder” step to the canvas. 
• Connect the dots between the “Start” step and “OneDriveCreateFolder” 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. 
• Define a variable or a global to store the result.
• Click the “OneDriveCreateFolder” step to configure its “Required” properties. Provide a name for the step. Select “WindowsLive” from the OAuth providers dropdown. Provide the folder's relative file path. Provide a variable or a global to store the result after execution. 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 in the images 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 process step to view its properties. When the workflow reaches the Create Folder step, FlowWright uses the selected OAuth provider and configured folder path for the OneDrive operation. The operation result is stored in the configured Variable or Global variable. Inspect the stored result and the workflow's True or False path to verify the outcome.

Tips:

• Select the appropriate OAuth provider before executing the step.
• Verify the folder path carefully before running the workflow.
• Use a meaningful Variable or Global variable name for the stored result.
• Test the workflow with a representative folder path before deploying it to production.
• Make sure the configured path identifies the intended OneDrive location.
• When using dynamically constructed paths, verify the resulting path before the Create Folder step executes.
• Keep folder-naming conventions consistent across workflows.
• Use meaningful folder names when users or downstream workflow activities will access folders.
• Consider connecting the False path to appropriate error-handling or recovery logic.
• Use the True path to continue with file uploads or other activities that depend on the folder being created.
• If several workflows create folders, establish a consistent folder structure to simplify document management.
• Avoid environment-specific hard-coded paths when the same workflow will be deployed across multiple environments.
• Test the workflow when the target folder already exists.
• Test paths containing workflow-generated values with realistic data.
• Verify the result stored in the configured Variable or Global variable before relying on it in downstream activities.
• Do not assume how an already-existing folder, invalid path, permission failure, or other OneDrive condition is represented by the True or False result unless confirmed by the FlowWright implementation.
• Do not assume that the resultJson property has a particular JSON structure without inspecting the actual implementation result.
• Do not assume parent folders will be created automatically when they do not already exist unless you have confirmed this behavior.
• Do not assume specific folder-name restrictions or OneDrive path-normalization behavior unless the implementation confirms it.
• Keep OAuth configuration and permissions appropriate for the OneDrive operations the workflow performs.
• Avoid exposing sensitive information contained in stored operation results to users or external systems.

Notes:

• The Create Folder step is defined in the OneDrive category with the internal name onedrivecreatefolder, label “Create folder in OneDrive”, and display name “Create Folder.”
• The step is implemented by FlowWright.Workflow.OneDriveCreateFolder in FlowWright.Workflow.dll and is defined as a Process step with 2 incoming connections and 2 outgoing connections.
• The step defines three required properties:
  • selOAuthProvider – Select OAuth provider
  • destinationFilePath – Path to create folder
  • resultJson – Store result in Variable/Global 
• The OAuth provider property uses the SelOAuthProvider data type, implemented by FlowWright.DataTypes.SelOAuthProvider in FlowWright.DataTypes.dll. Its description is “Get oAuth provider list.”
• The folder-path and result-destination properties use the string data type, implemented by FlowWright.DataTypes.ClsTextBox in FlowWright.DataTypes.dll.
• The step provides two return values:
  • False
  • True

Definition Sample:

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

Note: Verify and complete any missing configuration after importing the sample, including:

• OAuth provider.
• OneDrive folder path.
• Variable or Global variable used to store the result.
• Workflow Variable references.
• Environment-specific OAuth settings.
• OneDrive permissions.
• Downstream True and False workflow paths.
• Any preceding logic used to construct the folder path.
• Any downstream activities that depend on the created folder.

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

Click here to download the sample file.