Google Drive and AI agents
Google Drive is the folder where «final_v2_FINAL_client_approved» lives, with three near-identical neighbours beside it. An agent works in the folders you shared with it: it puts what arrives where it belongs, under a name you'll still find in six months, and tells you which version is current instead of leaving you to work that out from timestamps.
What an agent does in Google Drive
- Works in the folders you shared with it, and the rest of the drive doesn't exist for it.
- Answers «which of these is the current one» from the trail, not from the file name.
- Files what arrives: the right folder, and a name that can be found by searching for it.
- Keeps an eye on share links: who a file is open to, and how long it has been open.
- Notices what is about to be lost — the file nobody has opened since the project ended.
Processes that run themselves
A playbook isn't a button — it's a process with a condition that starts it. In Google Drive that condition comes from the storage itself: a file lands in a shared folder, a link goes out to a client, a project closes.
A file lands in a shared folder
Someone drops a file into a shared folder
- Work out which project and which stage it belongs to
- Move it to the right folder and rename it by your convention
- Check it against what's already sitting there: a new version or a duplicate
- Ask you when the file itself gives nothing away about where it goes
A link goes out to a client
A file or folder is shared by link with a client
- Check that what's open is what you meant to open
- Flag it when access is wider than it needs to be: anyone with the link rather than the person you sent it to
- Record who got the link and when, so there's somewhere to look it up
- Bring you the list of open links without touching anyone's access
A project closes
A project moves to finished
- Gather the final files into one folder, named so they can be found
- List the links that stayed open after handover
- Mark the files nobody has opened since the project ended
- Hand you the list: what to close, what to keep, what to archive
Where the agent stops
- It works in the folders you shared with it. The rest of the drive isn't there for it.
- It never deletes and never overwrites: a new version goes beside the old one, not on top of it.
- An over-permissive share link is shown to you — it doesn't quietly change anyone else's access.
- Where a file holds personal data or something a client considers theirs, what may be shared is your decision.
FAQ
Will the agent get access to my whole drive?
No. Access is given folder by folder: you share specific folders, and what's inside them becomes visible. The agent sees exactly what the connected account sees, not one file more. You can change that list at any point.
Will it tidy up and delete the duplicates?
No — deleting isn't its job. It files what arrives and points out what looks like a duplicate, but the choice between two near-identical files stays with you. Tidying to its own taste is the fastest way to lose the version you needed.
How does it know which version is current?
Not from the file name: a «FINAL» in the title means nothing. It looks at what was uploaded last, what the link sent to the client pointed at, and which file was being discussed when it was approved. When there's no trail, it says it can't tell rather than choosing for you.
Does this work with a shared drive or only with mine?
With both — the difference is who grants the access. Your own folders you share yourself; a folder on a shared drive is opened by whoever administers it. After that the setup is a conversation, with no permissions to wire up by hand.
Where this shows up
Walkthroughs where Google Drive carries part of the process.