Description:

The GoogleDriveRenameFolder workflow step renames a specified Google Drive folder.

The step supports:

• Selecting an OAuth provider.
• Specifying the path of the folder to be renamed.
• Providing the new folder name.
• Returning a True or False result for subsequent workflow processing.

Usage:

The GoogleDriveRenameFolder step is typically placed after a workflow identifies or creates a Google Drive folder whose name needs to change.

A typical workflow pattern is:

Identify Folder → GoogleDriveRenameFolder → Continue Process

The step receives the folder path and new name, while the OAuth provider supplies the authentication configuration the step requires.

The step can be used by later workflow activities to:

• Rename folders according to workflow status.
• Apply standardized folder naming.
• Rename folders after completing a business process.
• Organize folders using workflow-generated names.
• Update folder names when business information changes.
• Create separate True and False processing paths after the rename operation.

To use this step, configure Google Drive with Flowwright OAuth connections.

A sample Google OAuth configuration is provided here for reference. 

Typical Workflow Suggestions:

Rename a Newly Created Folder

Use this step after a folder is created when you need to change its initial name.

Example:

Create Folder → GoogleDriveRenameFolder → Continue Process

The workflow supplies the folder path and the desired new name.

Apply a Standard Folder Name

Use the step to standardize folder names according to a workflow convention.

Example:

Identify Folder → GoogleDriveRenameFolder → Continue

For example, a workflow could rename a folder using a consistent business naming convention.

Rename a Folder After Process Completion

Use GoogleDriveRenameFolder at the end of a document-processing workflow.

Example:

Process Documents → GoogleDriveRenameFolder → Complete Workflow

You can rename a folder after the workflow completes its processing activities.

Rename a Folder Based on Workflow Status

Use the step to reflect a workflow status in a folder name.

Example:

Complete Approval → GoogleDriveRenameFolder → Continue

You can change a folder name after an approval stage has completed.

Rename a Folder After Approval

Use the step to distinguish folders associated with approved or completed business processes.

Example:

Approval → GoogleDriveRenameFolder → Archive/Continue

The workflow can supply an appropriate new folder name after the approval activity.

Rename a Folder Using Workflow Values

Use workflow-generated values when constructing the new folder name.

Example:

Get Business Data → GoogleDriveRenameFolder → Continue

For example, the new name could incorporate an identifier, project name, or status value available to the workflow.

The step accepts the new name as a string property, allowing workflow values to be supplied based on the configuration supported by the FlowWright designer.

Rename a Folder After a Business Process

Use the step to update the folder name when a business process reaches a particular stage.

Example:

Process Request → Update Business Status → GoogleDriveRenameFolder → Continue

This can help align the Google Drive folder structure with the current workflow state.

Rename an Active Folder to an Archive Name

Use the step when a workflow transitions documents from active processing to an archival state.

Example:

Complete Processing → GoogleDriveRenameFolder → Archive

The new folder name can represent the folder's new business purpose.

Rename Project Folders

Use the step in project-oriented workflows when project information changes.

Example:

Update Project Information → GoogleDriveRenameFolder → Continue

The folder name can be updated to reflect the current project naming convention.

Rename Customer Folders

Use the step to update customer-related folder names.

Example:

Update Customer Data → GoogleDriveRenameFolder → Continue

The workflow can identify the existing folder and provide the required replacement name.

Use the Result to Control Subsequent Processing

Use the True and False paths as separate workflow routes.

Example:

Identify Folder → GoogleDriveRenameFolder

True → Continue Process

False → Alternate/Error Handling

This makes the rename operation an explicit decision point in the workflow.

Rename Multiple Folders

Use multiple instances of GoogleDriveRenameFolder when different folders require different names.

Example:

Identify Folder A → Rename Folder A → Rename Folder B → Complete

Each step can have its own folder path and new folder name.

Rename a Folder Before a Downstream Integration

Use the step when a subsequent activity expects the folder to have a particular name.

Example:

Prepare Documents → GoogleDriveRenameFolder → External Processing

The rename operation becomes a preparation step for the downstream activity.

Example:

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

• Create a new process definition named “GoogleDriveRenameFolderDef” and open it in Designer mode. 
• Drag a “GoogleDriveRenameFolder” step to the canvas.
• Connect the dots between the “Start” step and “GoogleDriveRenameFolder” 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 “GoogleDriveRenameFolder” step to configure its “Settings” properties. Provide a name for the step. Select the OAuth provider from the drop-down list. Rename the provider's old folder path. Provide the new name. 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 for measuring workflow progress and the percentage 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 process step to view its properties. When the workflow reaches the Rename Folder step, FlowWright uses the configured OAuth provider, folder path, and new folder name for the folder-rename operation. Verify:
  • The correct OAuth provider was selected.
  • The folder path identifies the intended folder.
  • The new folder name is correct.
  • The workflow follows the expected True or False path.
  • Any downstream activity receives the expected workflow state.

Tips:

• Select the correct OAuth provider before testing the workflow.
• Verify that the folder path identifies the intended Google Drive folder.
• Use meaningful and consistent folder naming conventions.
• Test the new folder name with representative workflow data.
• Verify that the new name does not conflict with the workflow's intended folder organization.
• Test both the True and False paths.
• Use workflow-generated values carefully when constructing dynamic folder names.
• Consider environment-specific OAuth configuration when moving workflows between environments.
• Use logging to make folder-rename operations easier to troubleshoot.
• Connect the False path to an appropriate alternate or error-handling activity.
• Test the workflow against representative Google Drive folders before deployment.
• Keep folder naming conventions consistent when multiple workflows manage the same Google Drive structure.
• Verify the folder path after changes to the Google Drive folder hierarchy.
• Review the configured OAuth provider whenever authentication configuration changes.
• Do not place authentication credentials or access tokens in workflow logging fields.
• The XML does not document duplicate-name behavior, handling of nonexistent folders, permission failures, special-character restrictions, or other provider-specific behavior. Validate these scenarios in the FlowWright implementation before depending on them.
• Do not assume the precise runtime meaning of the True and False returns solely from the XML; the XML identifies the outputs but does not define their detailed runtime conditions.

Definition Sample:

You may download the sample definition from the link provided and later import it into the FlowWright Process Definition (XML file) or Form Definition (HTML file) page, following the same approach described in the reference documentation.

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

• OAuth provider.
• Folder path.
• New folder name.
• Workflow Variable references, if used.
• Environment-specific OAuth settings.
• Google Drive folder structure.
• Downstream True and False workflow paths.

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

Click here to download the sample file.