Google Apps Script automation · Iterative · partially validated
Google Drive Automation Center v3
A Google Apps Script project that reorganizes a cluttered Drive into a defined folder taxonomy, in logged, dry-run-first batches.
What this shows: I build automation safety-first: dry runs, audit logs, and staged batches checked after each run.
Challenge
Drive content was spread across loose, nested, and duplicate folders, which made business documents, renewal files, and automation records hard to find and maintain.
My role
I specified the folder taxonomy and automation requirements, iterated the Apps Script code, reviewed execution logs, and controlled when changes ran.
Approach
- Defined a seven-category folder structure with 34 subfolders.
- Designed safety features: dry-run first, move history with rollback, duplicate detection, audit logging, health and permission checks, filename standardization, and weekly reporting.
- Ran moves in staged batches and checked the run logs after each one.
- Accounted for Drive and Apps Script constraints, including protected or non-movable files and missing destinations.
Tools
Google Apps Script, Google Drive, JavaScript, Audit logging
Result
Repeatable, logged batches of file organization. Two recorded batches moved 20 items (37 remaining), then 17 items (0 remaining), with 0 blocked in either batch.
Limitations
- The Drive is not fully cleaned or deduplicated; a later review found remaining loose and duplicate folders.
- Several designed features (rollback, duplicate detection, weekly reporting) still need individual validation in code.
Technical depth
- Designed for deep folder scanning with continuation across runs.
- Dry-run-first design: intended moves are reviewed before anything changes.
- Built to account for failed operations such as protected files and missing destinations.