Google Drive File Intake Agent with Claude Code

The damaging outcome from a filing agent is a confident guess: contract-final-v3.pdf dropped into the wrong client folder and found by an auditor a year later. This template refuses that by working only from metadata it can genuinely see and leaving anything ambiguous exactly where it landed. The temperament this job wants is one that studies the evidence before touching anything, which is where Claude Code sits.

Loading preview…
Free to start · guided setup

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:

  1. Connect Google Drive

    One sign-in. The agent acts through your account, scoped to what this template uses.

  2. Connect Slack

    One sign-in. The agent acts through your account, scoped to what this template uses.

  3. 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.

  4. Runs on Claude Code

    Preselected for this page — connect your Claude Code account during setup, or switch to NoClick's built-in models with one click.

  5. Watch it handle a test run

    A staged conversation against a simulated world — then it’s live.

Why Claude Code for this agent

Checks the destination exists

It cannot create folders, so it searches and lists to confirm the target before moving anything, then names the folder your rules asked for when that folder turns out to be missing.

Files beside the siblings

Before the move it looks for existing files under the same client or project, so a new invoice lands with its family instead of starting a second pile nobody knows about.

Before you fork

Our scanner saves a three hundred page batch as separate PDFs. What then?

Three hundred file changes and three hundred short runs, each leaving its own comment. The volume is real and so is the cost, so batch scanning is the case to think about before turning this on. Scanning into a folder outside the watched tree and moving the finished batch across in one go is the usual way around it.

Run it with a different agent

Put Google Drive File Intake Agent to work on Claude Code

Free to start. Guided setup, a test run against staged conversations, and it's live.