Monitor & Auto-Download Changed Google Drive Files

This n8n workflow automatically monitors a specified Google Drive folder for new or modified files, downloading only those changed since the previous execution. It uses a control file 'n8n_last_run.txt' stored in Google Drive to track the last run timestamp. If the file is missing, it defaults to the last 24 hours. The workflow runs on a customizable schedule, lists files modified after the timestamp, downloads them locally or to another destination, and updates the timestamp file for the next run.

Key components include a Schedule Trigger, Google Drive nodes for reading the timestamp, listing files, downloading changes, and writing the new timestamp. A Code node handles timestamp logic, while Merge and NoOp nodes ensure clean data flow. The design is modular with sticky notes for clarity, making it easy to extend for additional processing like notifications or backups.

Benefits include preventing duplicate downloads, handling edge cases like missing timestamps, and saving significant time on manual file checks. Ideal use cases: team collaboration folders, automated backups from shared drives, content pipelines for developers, or syncing project assets without full rescans. Perfect for IT teams managing document repositories or developers tracking code/file updates.