Box File Intake Agent

In an enterprise Box the expensive mistake is not an untidy folder, it is a signed agreement sitting where legal never looks, or an onboarding pack missing the one form an auditor asks for. This agent reads each new file's name, path, size and neighbours, writes on the file which class it matched and what is still owed, and pings the people your rules name when something has landed in the wrong place. It never opens a document and changes nothing in Box, which is usually the only basis on which an agent gets near a legal folder at all.

What people use it for

• Signed contracts get noticed today - An executed agreement is worth hearing about on the day it arrives rather than at renewal. The comment records the counterparty and date its name carries, and legal gets a line in the same minute.
• Documents in the wrong room - A countersigned statement of work in a deal room shared with the vendor is a permissions problem dressed as a filing problem. Path counts as evidence, so a contract class outside the contracts tree always raises a flag.
• A record that outlives the uploader - The reasoning stays in a comment on the file, inside Box, where somebody reviewing it years later is actually looking. It survives staff leaving and channels being archived.
• It cannot open your documents - Classification is built from name, extension, size, path and neighbours alone. For legal and finance material that boundary is the whole appeal: nothing inside a contract is ever read, forwarded, or written into a summary.

Before you fork

What permissions does it actually need in Box?

A connection that can read file and folder metadata in the folders you watch, run search, and add comments, plus the event trigger and a Slack channel. It needs nothing that moves, deletes or manages collaborators, and an account scoped to a few folders rather than the enterprise root is the sensible setup. Your filing rules go in as a variable.

Can it file things into the right folder for us?

Not in this template, and that is on purpose. It classifies and records, a person moves what needs moving, and your retention policies and folder permissions keep behaving the way your admins configured them. In practice the slow part was never dragging the file, it was noticing that a contract had landed in the wrong place at all.

What happens when somebody bulk uploads four thousand files?

Each new file in a watched folder is one run, so a migration like that is four thousand of them. Watch the folders where classification earns its keep, the contracts tree, vendor intake, whatever auditors ask about, rather than everything, and pause the workflow before a planned bulk move. Normal weeks are a few dozen runs.