Box File Intake Agent with Codex

One arriving file is a metadata read, a search for the same counterparty elsewhere in Box, a single comment written onto the file, and sometimes one line into Slack. Four calls with clear edges and a fixed output shape. Codex is quick and dependable on bounded API work of precisely that kind.
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.

MSA_Executed_Vantage-Kliniken-GmbH_2026-08-11.pdf

Priya Raghunathan, Legal Operations/Legal/Contracts/2026/Executed

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.

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 Box

    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

    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.

  4. Runs on Codex

    Preselected for this page — connect your Codex 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 Codex for this agent

One comment, occasionally one line

Ordinary intake happens in silence and only the conditions your rules escalate reach a channel. Keeping those two outputs separate is what stops the Slack side becoming a log nobody reads.

The counterparty search is one call

Looking the counterparty up elsewhere in Box is what lets the comment say whether this is their first document or their ninth, and it costs a single search per file.

Good to know

Before you fork

Who can see the comment it writes?

Anyone with access to the file, external collaborators included, so a comment on a document sitting in a deal room shared with a vendor is visible to that vendor. That is precisely why escalations go to Slack instead. Watch the deal room case in the Test Run before pointing this at externally shared folders.

Other editions

Run it with a different agent

claude-codeClaude CodeopencodeopenclawhermesMore Codex agents

Make it yours

Put Box File Intake Agent to work on Codex.

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