Description:

The Google Drive Create Folder workflow step creates a folder in Google Drive at the specified path using the selected OAuth provider.

The step supports:

• Selecting an OAuth provider for the Google Drive operation.
• Specifying the path where the folder should be created.
• Creating Google Drive folders as part of a workflow.
• Using workflow-generated values for the folder path.
• Continuing workflow processing after the folder-creation operation.

Usage:

The Google Drive Create Folder step typically comes after the workflow determines the folder location to create.

The OAuth provider identifies the Google Drive authentication configuration, while the folder path identifies the new folder location.

A typical workflow pattern is:

Determine Folder Path → Google Drive Create Folder → Use Folder

The step can then be incorporated into workflows that:

• Create customer folders.
• Create project folders.
• Create case or ticket folders.
• Establish document-storage locations.
• Prepare folders before uploading files.
• Organize files by workflow instance.
• Create department or business-unit folders.
• Prepare archive locations.
• Build folder structures dynamically.
• Branch into success or error-handling processing.

A typical workflow can be structured as:

To use this step, you must set up a Google Drive connection in the FlowWright application. To create a new OAuth source, go to Integrate > Connections > OAuth. 

A sample Google OAuth configuration is provided here for reference. 

Typical Workflow Suggestions:

Create Customer Folders

Use the step to create a Google Drive folder when a new customer is registered.

Example:

New Customer → Build Customer Folder Path → Google Drive Create Folder → Process Customer Documents

The folder path can be based on customer-associated information.

For example:

Customers/
    Acme Corporation/

Create Project Folders

Use the step to automatically create a Google Drive folder when a new project is initiated.

Example:

New Project → Determine Project Folder → Google Drive Create Folder → Generate Project Documents

A project-specific folder provides a location for subsequent document-processing activities.

Create Case or Ticket Folders

Use the step to establish a dedicated Google Drive location for a case, service request, or ticket.

Example:

Case Created → Build Case Folder Path → Google Drive Create Folder → Store Case Documents

A dynamically generated path can incorporate information such as the case or ticket number.

Prepare a Folder Before Uploading Files

Create the destination folder before a subsequent workflow activity uploads documents.

Example:

Determine Upload Location → Google Drive Create Folder → Upload File(s)

This pattern is useful when a workflow needs to establish a destination before performing additional Google Drive operations.

Create Folders for Workflow Instances

Use workflow information to create a folder associated with an individual process instance.

Example:

Workflow Start → Build Instance Folder Path → Google Drive Create Folder → Generate/Store Files

This provides a logical location for files generated during a particular workflow execution.

Create Department Folders

Use workflow data to create folders based on department or organizational information.

Example:

Read Department → Build Department Folder Path → Google Drive Create Folder → Process Department Files

This can be useful when documents need to be organized according to business-unit information.

Create Archive Folders

Use the step as part of a document archival workflow.

Example:

Document Processing Complete → Determine Archive Location → Google Drive Create Folder → Archive Documents

The workflow can determine the required archive location before creating the folder.

Create Folders from Form Values

Use values collected from a FlowWright form to construct the folder path.

Example:

Form Submission → Read Form Values → Build Folder Path → Google Drive Create Folder

For example, you can incorporate customer, project, or request information collected through a form into the folder location.

Create a Folder for Generated Reports

Create a Google Drive folder before generating or storing workflow reports.

Example:

Collect Results → Determine Report Folder → Google Drive Create Folder → Generate/Save Report

This allows the workflow to establish an appropriate location before downstream report processing.

Build a Folder Structure

Use multiple Google Drive Create Folder steps when a workflow needs to establish multiple folder locations.

Example:

Create Main Folder
       |
       v
Create Subfolder
       |
       v
Create Document Folder
       |
       v
Upload Documents

Branch Based on Folder-Creation Result

Use the True and False connections to separate successful processing from alternative processing.

Example:

             +---- True ----> Upload Files
             |
Create Folder
             |
             +---- False ---> Log / Notify / Handle Error

Prepare Dynamic Folder Locations

Use workflow values to construct a folder path before executing the step.

Example:

Retrieve Business Data → Build Folder Path → Google Drive Create Folder → Continue Processing

This separates destination preparation from the Google Drive operation itself.

Example:

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

• Create a new definition named “GoogleDriveCreateFolderDef” and open it in designer mode. 
• Drag a “GoogleDriveCreateFolder” step to the canvas. 
• Connect the dots between the “Start” step and “GoogleDriveCreateFolder” 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 “GoogleDriveCreateFolder” step to configure its “Required” properties. Provide a name for the step. Select the OAuth provider from the dropdown list. Enter the folder path to create. Click the Save button. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description. 

• The “Logging” configuration is necessary for documentation and to track workflow progress and completion percentage. 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 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 Google Drive folder-creation operation. Verify the resulting workflow path and confirm that the expected folder was created in the configured Google Drive location. The Search Replace String reference follows the same definition → instance → execute → render approach when demonstrating execution of a workflow step.

Tips:

• Select the correct OAuth provider before executing the workflow.
• Verify that the selected OAuth provider has the required Google Drive configuration.
• Make the folder path explicit and easy to troubleshoot.
• Use workflow Variables when the folder location needs to be determined dynamically.
• Build dynamic folder paths in a separate workflow activity when the path contains multiple pieces of workflow data.
• Test the folder path with representative workflow data before deploying the workflow.
• Verify the resulting Google Drive folder after executing the workflow.
• Use meaningful folder naming conventions when creating folders dynamically.
• Keep dynamically generated folder paths consistent across workflow instances.
• Consider how to handle duplicate or already-existing folders when designing the surrounding workflow.
• Connect the False return path to appropriate error-handling or alternative processing.
• Test both the True and False workflow paths.
• Verify the OAuth configuration independently when troubleshooting authentication-related problems.
• Avoid assuming local filesystem path syntax applies to Google Drive paths.
• Do not assume behavior for existing folders, nested paths, duplicate names, permissions, or invalid paths unless confirmed by the FlowWright implementation.
• Test workflows with realistic folder names and paths.
• Verify environment-specific OAuth configuration after importing a sample workflow.
• Avoid placing authentication credentials or other sensitive information in logging messages.
• Keep folder naming conventions maintainable when the workflow is expected to create many folders.
• When creating folders from user-supplied values, validate unexpected characters or formatting before constructing the path.

Notes:

• The Google Drive Create Folder step is defined in the Google Drive category with the internal name googledrivecreatefolder, label Create Folder in Google Drive, and display name Create Folder.
• The step is implemented by FlowWright.Workflow.GoogleDriveCreateFolder in FlowWright.Workflow.dll and is defined as a Process step with 2 incoming connections and 2 outgoing connections.
• The step defines two required properties:
  • selOAuthProvider – Select OAuth provider
  • destinationFilePath – Path to create folder
• The first property uses the SelOAuthProvider data type, implemented by FlowWright.DataTypes.SelOAuthProvider. The data type description is Get oAuth provider list.
• The folder-path property uses the string data type, implemented by FlowWright.DataTypes.ClsTextBox. Its data type description is Get textbox.
• 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.
• Folder path.
• Workflow Variable references.
• Environment-specific Google Drive settings.
• Downstream True and False workflow paths.
• Any required Google Drive authorization configuration.

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

Click here to download the sample file.