Google Drive File Intake Agent with Codex
The instruction defining this agent is an admission: it cannot open a file. Name, type, size, owner, timestamps and the folder it landed in are the whole of the evidence, and it has to record in the comment that a match came from the file name alone. Codex follows a concrete instruction like that cleanly, and matching an invoice number or a client code against a pattern is precise work of the kind it is strong on.
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 Codex
Preselected for this page — connect your Codex 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 Codex for this agent
Matches on the pattern, says which
The comment records the exact part of the name or metadata that matched, so a filing decision is auditable rather than mysterious six months later.
Quick per file
Metadata reads and one move are a small unit of work, and a fast harness keeps the intake folder emptying at the pace files arrive in it.
Before you fork
Six months on, how do I find out why a file is where it is?
The comment on the file was written for exactly that moment. It records where the file came from, where it went, which rule matched and the part of the name that triggered it, and it travels with the file rather than living in a log somewhere. NoClick's run history holds the underlying tool calls if you need more than that.
Run it with a different agent
Put Google Drive File Intake Agent to work on Codex
Free to start. Guided setup, a test run against staged conversations, and it's live.