Track new and changed files across all your Google Drive folders

On a schedule, the system scans every folder and subfolder in Google Drive and lists what's new or changed since last time.

How the work actually flows

A straight line. Runs once per each folder and subfolder.

Pattern: Multiple Instances without a priori Run-Time Knowledge (15)

flowchart TD trig(["scheduled drive scan"]):::trigtime s0[["scan each folder and subfolder"]]:::mi s1["compare files to last check"]:::task s2["collect new and changed files"]:::task s3["pass list to next step"]:::task trig --> s0 s0 --> s1 s1 --> s2 s2 --> s3 out[/"list of new and changed files"/]:::out pay{{"team knows what changed without checking manually"}}:::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 itemResultPayoff
Build size
Advanced

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

Business functions
Scheduling & CalendarFile & Cloud Storage
Connects
Google Drive

The problem it solves

Google Drive doesn't make it easy to see what's new or changed across an entire folder tree, so you either check manually or miss updates entirely. Teams relying on shared drives for documents often find out about changes too late to act on them.

Who it fits

Teams and operators who manage shared documents across many Google Drive folders and need to know when something changes.

How it works

  1. On a schedule, the system works through your main folder and every subfolder inside it
  2. Each folder's file list is checked against what was seen last time
  3. New and modified files are collected into a single list
  4. That list is passed along so you can trigger updates, notifications, or backups from it
What you get

Changed files you can act on without checking every folder

You get a single, current list of every new or changed file across all your Drive folders, ready to feed into whatever you do next.

What you get

A list of every new or modified file since the last check, ready to feed into your next step.

What you need

A Google Drive account (Google Workspace or personal).

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