Keep files in sync between SharePoint and Google Drive automatically

Checks SharePoint for new or changed files and copies them into Google Drive, keeping a record of what's synced.

How the work actually flows

It branches. Exactly one path is taken; runs once per each file.

Pattern: Multiple Instances with a priori Design-Time Knowledge (13) · Exclusive Choice (4) · Simple Merge (5)

flowchart TD trig(["scheduled sync check"]):::trigtime s0["check sharepoint for files"]:::task s1[["compare against synced record"]]:::mi s2[("download and upload file")]:::store s3[("mark file as synced")]:::store trig --> s0 s0 -->|"one per each file"| s1 s2 --> s3 gx{"× is file new or changed"}:::gate s1 --> gx p00["download and upload file"]:::task gx -->|"changed"| p00 p10["skip file"]:::task gx -->|"unchanged"| p10 jn{"○ mark as synced"}:::gate p00 --> jn p10 --> jn jn --> s2 out[/"drive mirrors sharepoint files"/]:::out pay{{"no manual copying no stale files"}}:::pay s3 --> out out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itA stepRuns once per itemA record or sheetOne path onlyPaths rejoinResultPayoff
Build size
Advanced

A larger build with multiple systems, AI reasoning, and custom rules.

Business functions
Knowledge Base & RAGSpreadsheet & Database OpsFile & Cloud Storage
Connects
SharePointGoogle DriveSupabase

The problem it solves

When files live in more than one system, someone has to remember to copy new documents over, and it's easy to end up with outdated versions in one place and current ones in another. Keeping two file libraries in sync by hand eats up time and invites mistakes.

Who it fits

Businesses that manage documents across SharePoint and Google Drive and need both to stay current.

How it works

  1. Runs on a set schedule to check SharePoint for files
  2. Compares each file against a record of what's already been synced
  3. Downloads any file that's new or has changed
  4. Uploads it to the matching folder in Google Drive
  5. Marks the file as synced so it isn't copied again
What you get

Files that show up in both places

Your SharePoint files stay mirrored in Google Drive automatically as they change.

What you get

An up-to-date mirror of your SharePoint files in Google Drive with no duplicate copies.

What you need

A Microsoft SharePoint account, a Google Drive account, and a database to track synced files.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Back to the AI Playbook