Google Drive File Intake Agent with Hermes

This is a small classification problem repeated forever: given a file name, a type, a size and a folder, decide which of your rules applies. The reasoning is shallow, the vocabulary is your own, and no code appears anywhere in it. Hermes fits that comfortably, with your Drive and Slack connected as tools and an open model doing the sorting.
Loading preview…
Free to start · guided setup · switch agents any time.

Live demo

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.

What you'll need

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 Hermes

    Preselected for this page — connect your Hermes 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.

A considered pairing

Why Hermes for this agent

Judgement without depth

Working out that INV-2026-0417 is an invoice for a named client is reasoning a general model handles well, and your rules supply the destination.

The refusal is built in

When metadata matches nothing cleanly it moves nothing and asks who the file belongs to, so the model's confidence is not what protects your folder structure.

Good to know

Before you fork

Does this need somebody technical to keep running?

No. The thing needing attention is your filing rules, and they are a paragraph in plain English naming the intake folder, the destinations and what deserves a Slack line. The person who knows where documents belong is the right owner, and no engineer has to be involved after setup.

Other editions

Run it with a different agent

claude-codeClaude CodeOpenAICodexopencodeopenclawMore Hermes agents

Make it yours

Put Google Drive File Intake Agent to work on Hermes.

Free to start. Guided setup, a staged test run, and a workflow you can change at every step.