Google Drive New File to SharePoint Archive

Overview

This flow centralizes Google Drive uploads into governed Microsoft 365 storage. On a schedule it polls a watched Google Drive folder, copies each new file into a structured SharePoint library (organized by date), sets the file's Title metadata, records the migration in a Dataverse ledger, and notifies the owner in a Teams channel.

Why it matters: Files scattered in Google Drive are hard to govern. Mirroring them to SharePoint - with a durable migration ledger - makes them searchable, retained, backed up, and idempotently de-duplicated across polls.

Status: Built and verified (Flow Checker 0 errors / 0 warnings). Ships Off; going live requires only connection authorization and env-var configuration.

Use Case

A team receives files in Google Drive that must live in SharePoint for governance, retention, and discoverability. IT/Operations want an unattended, repeatable bridge that never double-archives the same file and leaves an audit trail of what was migrated and when.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Google Drive	shared_googledrive	ListFolder GetFileContent
SharePoint	shared_sharepointonline	CreateFile ODataStylePatchFileItem
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord
Microsoft Teams

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Poll interval

Change the Recurrence frequency/interval (e.g. every 5 minutes for faster archiving).

Folder structure

Edit flowlibs_ArchivePathDateFormat (e.g. yyyy/MM/dd) or extend Compose Target Folder to include the source folder name.

Richer metadata

ODataStylePatchFileItem uses a plain (non-dynamic-schema) item object, so you can add custom library columns (e.g. DriveFileId, SourceSystem) without Flow Checker errors once those columns exist in the target library.

Export format

For Google-native files, branch on MediaType and choose an export MIME before download.

Dedupe by hash

Store an ETag/hash column and compare to detect content changes, not just new ids.

Notification target

Swap the Teams post for Outlook SendEmailV2 to email the owner, or include an adaptive card.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@concat(variables('varLibraryPath'), '/', formatDateTime(utcNow(), parameters('EnvVar_PathDateFormat')))

@equals(items('Apply_to_each_File')?['IsFolder'], false)

@{concat('flowlibs_drivefileid eq ''', items('Apply_to_each_File')?['Id'], '''')}

@equals(length(outputs('Check_Existing_Log')?['body/value']), 0)

@body('Create_SharePoint_File')?['ItemId']

@{guid()}

Customize & download