Docs & knowledge
Give your agents access to your Box files.
Agents search your Box content, read and upload files, comment on files, share them, send them for signature, and keep folders organized. Box webhook events in a folder you choose start an agent when files and folders change, someone comments or gets access, a shared link appears, metadata changes, a task is assigned, or a Box Sign request moves forward.
5,000 free credits to start.
Agent reach
Box API 2.0
The full surface, searched at run time.
Connect with
- API key
- Your own OAuth app
Paste the client ID and secret of a Box Server app that uses Client Credentials Grant, which acts as its service account or a managed user. Or sign in through your own Box User app with OAuth 2.0.
Event triggers
Yes · 6 events
Plus manual, schedule, and signed webhook.
What the agent can do
What agents do with Box
Helios searches the Box API 2.0 at run time. The agent finds the endpoint the task needs and calls it.
- Call Box API 2.0 operations allowed by the connected account and app scopes.
- Search files and folders by name and content.
- Read and download files, and upload new files and versions.
- Comment on files and reply to comments.
- Create shared links and manage collaborators.
- Create folders, and rename, copy, and move files and folders.
- Send Box Sign requests and ask Box AI about files.
- Start a run on file, folder, comment, collaboration, shared link, metadata, task, and Box Sign events in a folder you choose.
Examples
Tasks you can hand to a Box agent
Route every file that lands in an intake folder
When a file is uploaded, the agent reads it, moves it to the right folder, and tells the owner.
When a file lands in `Intake`, file it by type and tell the owner in Slack.
- box·read `Acme renewal notice.txt`
- box·move it to `Customers/Acme`
- slack·message the account owner
Renewal notice filed
- Moved to `Customers/Acme`
- Renewal date and price change sent to the owner
Answer questions in file comments
When someone asks a question in a comment, the agent reads the file and replies in the same thread.
When a comment asks the agent a question, answer it on the same file.
- box·read the comment and the file
- box·reply to the comment
Replied on `Q3 plan.md`
- The launch moved to the second week of November
- Quoted the section that says so
Share files on request
Ask in plain words for a file, and the agent finds it, creates a shared link, and sends it where you need it.
Find the latest security questionnaire and send a view-only link to #sales.
- box·search for `security questionnaire`
- box·create a shared link
- slack·post the link to #sales
Link shared
- Found the newest of three versions
- Link posted to #sales
Event triggers
Start a run on Box events
Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too.
| Event | What it means |
|---|---|
file.uploaded | A file lands in the watched folder - the moment to read it, file it, or tell someone. |
folder.created | A new folder appears, such as one for each customer or project, ready to be set up. |
comment.created | Someone comments on a file, so an agent can answer or follow up. |
collaboration.created | Someone is invited to a folder. Filter by folder name or role. |
shared_link.created | A file or folder gets a shared link. Filter by link access to catch open links. |
sign_request.completed | Every signer has signed, so an agent can file the document and tell the team. |
Works with
Box works with the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox.
FAQ
Questions, answered
Put an agent on Box.
Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook.