Track every file change in a Google Drive folder automatically

Checks a Google Drive folder on a schedule and logs every added, changed, or deleted file into a database.

How the work actually flows

It repeats. Repeats next scheduled check runs.

Pattern: Structured Loop (21)

flowchart TD trig(["runs on a schedule"]):::trigtime s0["compare files to snapshot"]:::task s1["identify added changed deleted files"]:::task s2[("update database record")]:::store trig --> s0 s0 --> s1 s1 --> s2 lp{"runs every scheduled interval"}:::gate s2 --> lp lp -. "next scheduled check runs" .-> s0 lp -->|"finished"| out out[/"up to date change log"/]:::out pay{{"audit trail without manual checks"}}:::pay 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 stepA record or sheetRepeat or finishResultPayoff
Build size
Advanced

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

Business functions
Spreadsheet & Database OpsScheduling & CalendarFile & Cloud Storage
Connects
Google DrivePostgresSupabase
Featured in

The problem it solves

When a shared Drive folder has multiple people adding and editing files, it's hard to know what's changed without opening every file yourself. You need a reliable record of what was added, updated, or removed, and when.

Who it fits

Operations teams that need an audit trail of changes to a shared Drive folder.

How it works

  1. The automation checks a Google Drive folder on a set schedule
  2. It compares the current files against what was tracked before
  3. Added, modified, and deleted files are identified
  4. The database updates to reflect exactly what changed
What you get

Changes you can trace back after the fact

You get a running log of every file added, changed, or deleted in a shared Drive folder.

What you get

An up-to-date database record of every file added, changed, or removed from the folder.

What you need

A Google Drive account and a Postgres or Supabase database.

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