Description:

The GoogleDriveGetFile workflow step downloads a specified file from Google Drive and saves it to a local machine.

The step supports:

• Selecting an OAuth provider.
• Specifying the name of the source file to download.
• Specifying the local destination path.
• Returning a True or False result for subsequent workflow processing.

Usage:

The GoogleDriveGetFile step typically follows a workflow that determines which Google Drive file to retrieve.

A typical workflow pattern is:

Identify File → GoogleDriveGetFile → Process Downloaded File

The step uses the selected OAuth provider, source file name, and local destination path to download the file.

Subsequent workflow activities can then use the downloaded file for supported processing.

Typical uses include:

• Downloading documents for local processing.
• Retrieving reports from Google Drive.
• Obtaining files for document-processing workflows.
• Downloading source files before another workflow activity executes.
• Retrieving files as part of an automated document-management process.
• Downloading files for subsequent conversion or analysis.
• Routing the workflow based on the download result.

A typical workflow pattern is:

Identify/Prepare File → Download File → Process File → Continue

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

A sample Google OAuth configuration is provided here for reference.

Typical Workflow Suggestions:

Download a Document for Processing

Use the step to retrieve a document from Google Drive before processing it locally.

Example:

Identify Document → GoogleDriveGetFile → Process Document

The source file name and local destination path are supplied to the download step.

Download a Report

Use GoogleDriveGetFile to retrieve a report stored in Google Drive.

Example:

Identify Report → GoogleDriveGetFile → Review/Process Report

You can then supply the downloaded report to subsequent workflow activities.

Download a File Before Document Processing

Use the step as the first stage of a local document-processing workflow.

Example:

GoogleDriveGetFile → Document Processing → Update Status

This separates source-file retrieval from the processing that follows.

Retrieve a File for Archiving

Use the step when a workflow needs to retrieve a Google Drive file before performing another archival or storage activity.

Example:

GoogleDriveGetFile → Archive/Store File → Complete

The local destination path specifies where the workflow saves the downloaded file.

Download a File for Conversion

Use GoogleDriveGetFile before a workflow activity that converts or transforms a downloaded document.

Example:

Download File → Convert Document → Save Result

This provides a straightforward retrieval-to-processing workflow.

Download a File for Analysis

Use this step to retrieve a file that another workflow activity will analyze.

Example:

Google Drive File → GoogleDriveGetFile → Analyze File

The download operation provides the local file the downstream activity needs.

Retrieve a File After a Business Event

Use the step after an approval, request, or other business event identifies a document that needs to be processed.

Example:

Approval → GoogleDriveGetFile → Process Approved Document

The workflow can retrieve the appropriate source file and continue with the next stage.

Download Customer Documents

Use the step in customer-oriented workflows where documents are stored in Google Drive.

Example:

Receive Customer Request → Identify Document → GoogleDriveGetFile → Process

The source file name can be supplied based on information available to the workflow.

Download Project Documents

Use the step to retrieve project-related files for downstream processing.

Example:

Identify Project → GoogleDriveGetFile → Process Project Document

This can be useful when a workflow needs a local copy of a project document.

Download a File Before Sending It Elsewhere

Use the step as an intermediate activity before another workflow step sends or transfers the file.

Example:

GoogleDriveGetFile → Prepare/Transfer File → External Process

The file is first downloaded to the configured local destination.

Retrieve a File for a Scheduled Workflow

Use the step in scheduled workflows that periodically retrieve files.

Example:

Scheduled Start → GoogleDriveGetFile → Process File → Complete

This can provide a repeatable workflow pattern for regularly retrieved documents.

Use the Result to Control Workflow Routing

Use the True and False outputs as separate workflow paths.

Example:

Identify File → GoogleDriveGetFile

True → Process Downloaded File

False → Alternate/Error Handling

This makes the download operation an explicit decision point.

Download Multiple Files

Use multiple GoogleDriveGetFile steps when you need to retrieve several files.

Example:

Identify Files → Download Report → Download Supporting Document → Process Files

Each step can specify its own source file and local destination.

Download a File Before Generating a Result

Use the step when a downloaded file provides source information for a later workflow output.

Example:

GoogleDriveGetFile → Read/Process Source → Generate Output

This lets the Google Drive file become an input to the rest of the workflow.

Example:

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

• Create a new process definition named “GoogleDriveGetFileDef” and open it in Designer mode. 
• Drag a “GoogleDriveGetFile” step to the canvas. 
• Connect the dots between the “Start” step and “GoogleDriveGetFile” 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 “GoogleDriveGetFile” step to configure its “Required” properties. Provide a name for the step. Select the Google OAuth provider from the drop-down list. Enter the source file path to download. Enter the path to the local folder where you want to save the file. 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 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 Download File step, FlowWright uses the configured OAuth provider, source file name, and local destination path to perform the download. Verify:
  • The correct OAuth provider was selected.
  • The intended source file was specified.
  • The local destination path is correct.
  • The downloaded file is available at the expected destination.
  • The expected True or False workflow path is followed.
  • Any downstream processing receives the expected local file.

Tips:

• Select the correct OAuth provider before testing the workflow.
• Verify that the source file name identifies the intended Google Drive file.
• Verify the local destination path before executing the workflow.
• Use meaningful and consistent local file names.
• Test the workflow with a representative file before deployment.
• Test both the True and False workflow paths.
• Verify that the destination location is appropriate for the environment where the workflow runs.
• Consider environment-specific OAuth configuration when moving workflows between environments.
• Use logging to simplify download-related workflow troubleshooting.
• Connect the False path to an appropriate alternate or error-handling activity.
• Verify that downstream activities reference the correct local destination.
• Test with representative document types and file sizes used by the workflow.
• Avoid assuming that a source file name alone supports a particular Google Drive folder/path syntax unless confirmed in the FlowWright implementation.
• Verify the destination path when deploying the workflow to another server or environment.
• Ensure that the workflow's local destination convention is consistent across related workflows.
• Verify that the downloaded file is available before executing downstream file-processing activities.
• Keep authentication credentials and access tokens out of workflow logging fields.
• Test the workflow after changes to the Google Drive file organization or naming convention.
• Do not assume behavior for nonexistent files, duplicate file names, permissions, local directory creation, overwrite behavior, or provider-specific file handling unless confirmed by the FlowWright implementation.
• Do not assume the precise runtime meaning of the True and False returns solely from the XML. The XML identifies 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 recommends completing any environment-specific configuration after importing a sample.

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

• OAuth provider.
• Source file name.
• Local destination path.
• Workflow Variable references.
• Environment-specific OAuth settings.
• Local file-system settings.
• Google Drive file organization.
• Downstream True and False workflow paths.

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

Click here to download the sample file.