Description:

The GoogleDriveRenameFile workflow step renames a specified file in Google Drive.

The step supports:

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

Usage:

The GoogleDriveRenameFile step typically follows a workflow that identifies a Google Drive file whose name needs to change.

A typical workflow pattern is:

Identify File → GoogleDriveRenameFile → Continue Process

The step receives the file path and new file name, while the selected OAuth provider provides the configured authentication context for the operation.

The resulting workflow can use the step to:

• Apply standardized file names.
• Rename generated documents.
• Reflect workflow status in file names.
• Rename files after approval or processing.
• Organize files according to business naming conventions.
• Prepare a file for subsequent workflow activities.
• Route execution through different paths based on the operation result.

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 Generated Document

Use the step after another workflow activity creates or prepares a document.

Example:

Generate Document → GoogleDriveRenameFile → Continue Process

For example, a workflow may initially generate a file using a temporary or generic name and then rename it to a business-specific name.

Apply a Standard File Naming Convention

Use GoogleDriveRenameFile to apply a consistent naming convention to workflow-managed files.

Example:

Identify File → GoogleDriveRenameFile → Continue

For example:

Invoice_12345_Temporary.pdf → Invoice_12345_Final.pdf

The new name is supplied through the Rename File to property.

Rename a File After Approval

Use the step after an approval activity to indicate the file's new status.

Example:

Submit Document → Approval → GoogleDriveRenameFile → Complete

You can rename a file to reflect that it has been approved.

For example:

Contract_1001_Draft.pdf → Contract_1001_Approved.pdf

Rename a File After Processing

Use the step to indicate that a file has completed a particular processing stage.

Example:

Process File → GoogleDriveRenameFile → Continue

A workflow could rename a file after successful processing to distinguish it from files still awaiting processing.

Rename a File Based on Workflow Status

Use workflow-generated values when the new file name needs to reflect the current process state.

Example:

Process Request → Determine Status → GoogleDriveRenameFile → Continue

For example:

Request_1045.pdf → Request_1045_Completed.pdf

The step accepts the new file name as a required string property.

Rename Customer or Project Documents

Use the step when a customer- or project-related file needs to follow a standardized naming convention.

Example:

Get Customer/Project Data → GoogleDriveRenameFile → Continue

For example:

Document.pdf → Acme_Project_1045_Document.pdf

This can make files easier to identify within a shared Google Drive structure.

Rename Files After a Business Process

Use this step when a business process reaches a defined stage.

Example:

Process Request → Update Status → GoogleDriveRenameFile → Continue

The new file name can represent the current state of the business process.

Rename an Active File to an Archive Name

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

Example:

Complete Processing → GoogleDriveRenameFile → Archive

For example:

Report_2026.xlsx → Report_2026_Archived.xlsx

Rename Files Before Downstream Processing

Use the step as a preparation activity when a subsequent workflow activity expects a particular file name.

Example:

Prepare File → GoogleDriveRenameFile → Downstream Processing

The rename operation can become an explicit preparation stage before another activity operates on the file.

Rename Multiple Files

Use multiple GoogleDriveRenameFile steps when several files require different names.

Example:

Identify Files → Rename Report → Rename Supporting Document → Continue

Each step can specify its own file path and new file name.

Use the Result to Control Workflow Routing

Use the True and False outputs as separate workflow paths.

Example:

Identify File → GoogleDriveRenameFile

True → Continue Process

False → Alternate/Error Handling

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

Use Workflow Variables for Dynamic File Names

When the workflow configuration supports it, you can incorporate values generated earlier in the process into the file path or new file name.

Example:

Get Customer Data → Build File Name → GoogleDriveRenameFile → Continue

For example, the workflow could construct a name based on a customer, project, request, or status value and supply it to Rename File.

The step itself defines both the source file path and new name as string inputs.

Rename Files in a Document Management Workflow

Use the step as part of a larger document lifecycle.

Example:

Upload File → Review → Approval → GoogleDriveRenameFile → Complete

This provides a simple way to reflect a document's workflow state through its file name.

Rename Files After Form Submission

Use the step after a form-driven workflow has collected the information needed to identify and name a document.

Example:

Form Submission → Generate Document → GoogleDriveRenameFile → Process Request

The resulting file name can follow the organization's document naming convention.

Example:

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

• Create a new process definition named “GoogleDriveRenameFileDef” and open it in designer mode. 
• Drag a “GoogleDriveRenameFile” step to the canvas. 
• Connect the dots between the “Start” step and “GoogleDriveRenameFile” 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 “GoogleDriveRenameFile” step to configure its “Required” properties. Provide a name for the step. Select the OAuth provider from the dropdown list. Enter the file path to rename. Enter the new file name. 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 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 File step, FlowWright uses the configured OAuth provider, source file path, and new file name for the rename operation. Verify:
  • The correct OAuth provider was selected.
  • The file path identifies the intended Google Drive file.
  • The new file name is correct.
  • The file has the expected new name.
  • The workflow follows the expected True or False path.
  • Any downstream workflow activity executes as expected.

Tips:

• Select the correct OAuth provider before testing the workflow.
• Verify that the file path identifies the intended Google Drive file.
• Use meaningful, consistent file-naming conventions.
  • Test the new file name with representative workflow data.
• Avoid unnecessarily ambiguous file names.
• Test both the True and False workflow paths.
• Use workflow-generated values carefully when constructing dynamic file names.
• Verify environment-specific OAuth configuration when moving a workflow between environments.
• Use logging to make file-rename operations easier to troubleshoot.
• Connect the False path to an appropriate alternate or error-handling activity.
• Test the workflow against representative Google Drive files before deployment.
• Keep naming conventions consistent when multiple workflows manage the same Google Drive document structure.
• Verify the configured file path after changes to the Google Drive folder structure.
• Review the selected OAuth provider whenever authentication configuration changes.
• Keep authentication credentials and access tokens out of workflow logging fields.
• Test file names containing spaces, numbers, and other representative characters used by your organization's naming convention.
• Verify that downstream activities use the expected file name after the rename operation.
• Test the workflow after changing the file naming convention.
• When using dynamically constructed names, verify that all expected workflow values are available before the step executes.
• Do not assume duplicate-name behavior, nonexistent-file handling, permission handling, special-character restrictions, or other Google Drive provider-specific behavior unless it has been confirmed in the FlowWright implementation.
• Do not assume the precise runtime meaning of the True and False returns solely from the XML. The XML defines the two outputs but does not document 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. The reference page also recommends completing any environment-specific configuration after importing a sample.

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

• OAuth provider.
• File path.
• New file name.
• Workflow Variable references.
• Environment-specific OAuth settings.
• Google Drive folder/file structure.
• Downstream True and False workflow paths.

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

Click here to download the sample file.