Description:

The GoogleDriveSendFile workflow step uploads a specified source file using the selected OAuth provider.

The step supports:

• Selecting an OAuth provider.
• Specifying the source file to upload.
• Specifying the destination path.
• Storing the relative file path in a Variable or Global variable.
• Returning a True or False result for subsequent workflow processing.

Usage:

The GoogleDriveSendFile step is typically placed after a workflow has generated, received, or otherwise prepared a file to upload.

A typical workflow pattern is:

Create/Get File → GoogleDriveSendFile → Continue Process

Subsequent workflow activities can then reference the uploaded file using the configured path or stored relative path.

Typical uses include:

• Uploading workflow-generated documents.
• Storing completed files in a Google Drive destination.
• Archiving workflow output.
• Uploading reports.
• Uploading documents generated from templates.
• Moving workflow-generated files into an external document-storage workflow.
• Retaining the relative path for subsequent processing.

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

A sample Google OAuth configuration is provided here for reference.

Typical Workflow Suggestions:

Upload a Generated Document

Use the step after another workflow activity creates a document.

Example:

Generate Document → GoogleDriveSendFile → Continue Process

You can supply the generated document via the source file path to upload.

Upload a Workflow Report

Use GoogleDriveSendFile to upload a report generated during workflow execution.

Example:

Generate Report → GoogleDriveSendFile → Complete Workflow

This pattern is useful when a workflow produces a report that needs to go to the configured destination.

Upload a Completed Document

Use the step when a document has completed a workflow process and needs to be uploaded.

Example:

Document Processing → GoogleDriveSendFile → Update Status

The upload can become the final document-storage operation before the workflow updates its status.

Upload a Form-Generated File

Use a file generated or collected as part of a form-driven workflow.

Example:

Form Submission → Generate File → GoogleDriveSendFile → Continue

You can supply the source file path to the upload step using the workflow's available values.

Archive Workflow Output

Use the step in an archival workflow.

Example:

Complete Processing → GoogleDriveSendFile → Archive Complete

You can configure the destination path for where the file should be saved.

Upload Multiple Workflow Outputs

Use multiple GoogleDriveSendFile steps when a workflow produces multiple files that need to be uploaded.

Example:

Generate Files → Upload Report → Upload Supporting Document → Complete

Each step can use its own source and destination path.

Store the Relative Path for Later Use

Configure a Variable/Global to store the relative path when a later workflow activity needs it.

Example:

GoogleDriveSendFile → Store Relative Path → Subsequent Processing

The XML specifically provides this optional destination property.

Use the Upload Result to Control Workflow Routing

Connect the True and False outputs to different downstream activities.

Example:

Prepare File → GoogleDriveSendFile

True → Continue Process

False → Alternate/Error Handling

This allows the workflow to treat the upload operation as a decision point.

Upload a Standardized Set of Documents

Use the step in workflows that repeatedly upload the same categories of generated documents.

Example:

Generate Invoice → GoogleDriveSendFile → Generate Receipt → GoogleDriveSendFile → Complete

Consistent destination-path conventions can make these workflows easier to maintain.

Upload a File Before Subsequent Processing

Use the upload step as an intermediate activity when later processing depends on the file having been uploaded.

Example:

Prepare File → GoogleDriveSendFile → Continue with Uploaded File

You can use the optional relative-path Variable/Global when subsequent activities need that value.

Use a Configured OAuth Provider

Select the appropriate OAuth provider in the step configuration.

Example:

Prepare File → GoogleDriveSendFile → Continue

The OAuth provider is a required input and uses FlowWright's SelOAuthProvider property type.

Upload Files Produced by Scheduled Workflows

Use the step in scheduled workflows that periodically generate files.

Example:

Scheduled Start → Generate Report → GoogleDriveSendFile → Complete

This can provide a repeatable workflow pattern for generated reports or other recurring outputs.

Example:

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

• Create a new process definition named “GoogleDriveSendFileDef” and open it in Designer mode. 
• Drag a “GoogleDriveSendFile” step to the canvas. 
• Connect the dots between the “Start” step and “GoogleDriveSendFile” 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 “GoogleDriveSendFile” step to configure its “Required” properties. Provide a name for the step. Select the OAuth provider from the dropdown list. Enter the source file path to upload. Enter the target file path where the file will be stored. Click the Save button. Note: Click the "AI Predict" button to have Copilot add new process steps that match your process description. 

• Click the “GoogleDriveSendFile” step to configure its “Optional” properties. Provide a variable or global reference to store the relative file path during execution. Then click the Save button. 

• The “Logging” configuration is necessary for documentation and for measuring 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 Upload File step, FlowWright processes the configured source file using the selected OAuth provider and destination configuration. If configured, it stores the relative path in the specified Variable or Global variable. Verify:
  • The correct OAuth provider was selected.
  • The source file path identifies the intended file.
  • The destination path is correct.
  • The relative-path Variable/Global is populated when configured.
  • The workflow follows the expected True or False path.

Tips:

• Select the correct OAuth provider before testing the workflow.
• Verify that the source file exists and that the configured source path identifies the intended file.
• Use meaningful Variable or Global names when storing the relative path.
• Verify the destination path before deploying the workflow.
• Test the upload with a representative file before using the workflow in production.
• Test both the True and False workflow paths.
• Use consistent destination-path conventions when multiple workflows upload related files.
• Store the relative path when subsequent workflow activities need to reference the uploaded file.
• Review environment-specific OAuth configuration when moving a workflow between environments.
• Keep authentication credentials and sensitive OAuth information out of workflow logs.
• Use logging to simplify upload-related workflow troubleshooting.
• Verify the resulting Variable or Global value before passing it to downstream activities.
• Consider connecting the False path to an appropriate alternate or error-handling workflow.
• Test workflows with different file sizes and representative document types.
• Avoid assuming the destination-path property behaves beyond the label supplied by the FlowWright step definition.
• The XML does not document file-overwrite behavior, duplicate-file handling, folder-creation behavior, or the precise semantics of the returned True/False values. Validate these behaviors in the FlowWright implementation before depending on them.
• Do not assume the selected OAuth provider's authentication or authorization behavior solely from this step definition; the XML only identifies the provider-selection property.

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.
• Source file path.
• Destination path.
• Variable or Global variable used to store the relative path.
• Workflow Variable references.
• Environment-specific OAuth settings.
• File-system-specific source configuration.
• Downstream True and False workflow paths.

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

Click here to download the sample file.