Box File Intake Agent with Hermes
Every new file in a watched folder is a run, which makes folder choice the whole cost decision. A contracts tree plus a vendor intake folder is a few dozen runs a week, while a migration dropping four thousand files is four thousand runs in an afternoon. Hermes runs on an open model foundation, so the per file figure is one you set when you fork it.
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.
MSA_Executed_Vantage-Kliniken-GmbH_2026-08-11.pdf
PDF, 1.8 MB, uploaded 16:42 CET through the e-signature connector. Four other files here begin with MSA_Executed_ and carry a counterparty and a date in the same shape. The folder is collaborated on by the legal group only.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Box
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
What each kind of document is called in your Box and where it is supposed to live - the folders you watch, the naming patterns that identify contracts, invoices, onboarding forms and the rest, what each class still needs before it counts as complete, and who gets pinged for which.
Runs on Hermes
Preselected for this page — connect your Hermes 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 Hermes for this agent
The watched folder is the budget
Scoping to the trees where a misfile actually costs something, rather than to the enterprise root, is the difference between a predictable weekly figure and an unbounded one.
Pause before a migration
A planned bulk move is the one event that turns this expensive, and it is also the one you can see coming. Switching the workflow off for the afternoon is the whole mitigation.
Before you fork
Does a stronger model classify names any better?
Only marginally, because the input is short: a file name, a path, a folder listing. Where it earns its place is the awkward middle, a name that half matches two classes, where the valuable behaviour is declining to match and naming the deciding fact instead. Try both against the nameless vendor document before you settle.
Run it with a different agent
Put Box File Intake Agent to work on Hermes
Free to start. Guided setup, a test run against staged conversations, and it's live.