Google Drive File Intake Agent with OpenCode
A run is a few metadata reads, at most one move and one comment, so filing cost tracks how many files land rather than how large the drive has grown. That makes it worth being deliberate about which folder you watch, since every change in the watched tree counts as an event. OpenCode is a light way to run it and lets you match the model to how complicated your naming rules really are.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
INV-2026-0417 Halvorsen Marine.pdf
Added by Ibrahim Diallo
PDF, 214 KB, single page, uploaded at 09:12 from the office scanner app. Created and modified timestamps match. Owned by the uploader and shared with the finance group. Eleven other files in the tree already begin with INV-2026, and a client folder named Halvorsen Marine AS sits two levels down under Clients.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Google Drive
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Filing rules
Which folder is the intake, how you want files sorted from their names and types, the exact destination folder for each kind of file, and which uploads are worth a Slack ping.
Runs on OpenCode
Preselected for this page — connect your OpenCode account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why OpenCode for this agent
Watch the intake, not the drive
Pointing it at the folder uploads land in keeps the run count equal to the number of new files. Watching an entire shared drive counts every edit anybody makes anywhere in it.
Simple rules, smaller model
Sorting by prefix and file type asks very little of a model. Save the stronger one for rule sets full of exceptions and client specific destinations.
Before you fork
How do I see its filing decisions before it touches the real tree?
Use the staged uploads that ship with the template. Timestamp Only Scan is the one worth reading, because a file called Scan 2026-08-11 14-33-02.pdf is precisely where a filing agent either asks a question or invents a client. You see the move it would make and the comment it would write, with nothing moved in Drive.
Run it with a different agent
Put Google Drive File Intake Agent to work on OpenCode
Free to start. Guided setup, a test run against staged conversations, and it's live.