Google Drive File Intake Agent
Files each new upload into the right folder from its name, type and metadata, comments on the file explaining what matched, and leaves anything it cannot place exactly where it is.
A shared Drive folder becomes a dumping ground within a month, and the cost of that lands on whoever needs the invoice at quarter end. This agent picks up each new file, reads its name, type and metadata, moves it into the folder your rules name, and records on the file itself which rule put it there. It works from metadata alone because it genuinely cannot open your documents, so anything it cannot place with confidence stays exactly where it is with a question attached.
## What people use it for
- **Keep the intake folder empty** - Scanned invoices, signed contracts and exports move where they belong as they arrive. Nobody blocks out a Friday afternoon to file three hundred things by hand.
- **Know why a file moved** - Every move leaves a comment naming the rule that matched and the piece of the file name behind it. Months later that is the difference between trusting the folder structure and checking it again.
- **Bad names get caught early** - A file called Scan 2026-08-11.pdf waits in the intake folder with a comment asking who it belongs to. The uploading habit gets fixed while the file is still findable.
- **No deletions, no permission changes** - Moving, searching and commenting is the entire list of what it can do. Sharing settings and the trash are untouched, so any mistake is one drag away from being put right.
## Before you fork
**Can it read what is inside my files?**
No, and it says so rather than pretending otherwise. It sees the file name, type, size, owner, timestamps and the folder tree around it, which is enough to sort by naming pattern, client code or file type, and not enough to sort by what a document actually contains. If your uploads are all called Scan 2026-08-11.pdf, fix the naming first or it will keep asking who they belong to.
**What happens when it files something in the wrong place?**
A move is reversible and the comment on the file records where it came from, so putting it back takes seconds. The genuinely damaging case, a confident guess on ambiguous metadata, is the one it refuses: unclear files are left untouched with a question. Point it at a copied folder for a week if you want to watch it before it touches the real tree.
**How much does it run on a busy folder?**
One short run per file change, so a team dropping forty files a week is forty runs, and a scanner that saves three hundred pages as separate PDFs is three hundred. Nothing runs while the folder is quiet. If the volume is heavy, watch the intake folder only rather than the whole drive, since every change in the watched tree counts.
