Box Legal Workflow Automation & Approvals
Run Box on autopilot. Keep the veto.
286 actions20 triggers
Sign requests, file versions, and retention policies fire inside Box before you've had a chance to review them; Rills proposes each action and waits for your call.
Interactive. No signup. 14 days free · approvals always free.
Most automation fires first, asks later. Rills shows you the change before it ships.
Every consequential legal action from Box arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.
Queue 3
Apply retention policy to 6 newly uploaded contract files?
6 files added to /Legal/Contracts in the past 4 hours
Same folder pattern as last quarter's retention batch
2 files flagged as pending sign request; hold may conflict
Free to wait. Free to think.
Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.
Approve from your phone in five seconds.
Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, no 3am stomach-drop wondering what shipped while you slept.
Routine cases graduate themselves.
Every approval feeds a confidence score for that exact workflow shape. The obvious cases (the ones you've green-lit fifty times) start running on their own. The judgment calls still come to you.
About Box automation
Legal documents move fast inside Box: sign requests change state, new file versions upload over old ones, and retention policies activate on folders you haven't looked at yet.
When Box runs unsupervised
A single missed review in a legal content workflow can produce changes that are hard to walk back. These are the moments where unsupervised Box automation tends to break things.
- BOX_SIGN_REQUEST_STATUS_CHANGED_TRIGGER: A sign request status flips and downstream actions fire before anyone confirms the counterparty actually signed.
- BOX_FILE_VERSION_UPLOADED_TRIGGER: A new file version uploads over a prior draft that was still under legal review, making the old version the recovery job.
- BOX_NEW_FOLDER_COLLABORATION_CREATED_TRIGGER: A collaboration posts to a restricted folder and an outside party gains access before the permission level has been verified.
- BOX_TASK_ASSIGNMENT_STATE_CHANGED_TRIGGER: A task state changes and a retention policy or hold assignment runs against the wrong document set.
- BOX_TRASHED_FILE_STATE_CHANGED_TRIGGER: A file moves to trash and a permanent removal job starts without confirming whether the file is under a legal hold.
What Rills does inside Box
Rills watches your Box triggers and queues a proposal before any operation runs. When a sign request status changes, before it creates a retention policy or uploads a replacement file version, the proposed action sits in your queue waiting for a decision.
The document still gets filed; you just see exactly what's happening before it goes out.
When Box events should and shouldn't act on their own
Not every Box event carries the same risk. Some are routine enough to graduate toward autonomous action over time; others should always wait for a human in a legal context.
- BOX_NEW_FILE_ADDED_TRIGGER: Routine enough to auto-approve for approve Box intake folders once the pattern is confirmed across several cycles.
- BOX_FILE_COMMENT_ADDED_TRIGGER: Low-stakes enough to graduate; comments rarely carry direct legal consequence.
- BOX_FOLDER_ITEM_ADDED_TRIGGER: Routine file organization can run autonomously once the destination folder is confirmed as non-restricted.
- BOX_SIGN_REQUEST_STATUS_CHANGED_TRIGGER: Always needs a human; a status change in a legal sign workflow can trigger irreversible downstream actions.
- BOX_TRASHED_FILE_STATE_CHANGED_TRIGGER: Always needs a human; permanent file removal under an active legal hold is the kind of consequence Box automation should never reach on its own.
- BOX_NEW_FOLDER_COLLABORATION_CREATED_TRIGGER: Always needs a human; outside access to legal folders is a judgment call, not a pattern match.
What wakes Rills up in Box
When these events fire, Rills proposes the next move and waits for your call.
BOX FILE COMMENT ADDED
Fires when someone adds a new comment to a file. Use this to track file discussions and feedback.
BOX FILE VERSION UPLOADED
Fires when a new version of a file is uploaded. Use this to track file updates and version history.
BOX NEW FILE ADDED
Fires when a new file is uploaded to a folder. Use this to respond to new content being added.
BOX NEW FOLDER COLLABORATION CREATED
Fires when someone is added as a collaborator on a folder. Use this to track new sharing and access grants.
BOX NEW SIGN REQUEST CREATED
Fires when a new signature request is created in Box. Use this to start workflows when documents are sent for signing.
BOX NEW TASK CREATED
Fires when someone creates a new task on a file. Use this to respond to new work items being assigned on your files.
What Rills can do in Box
4 of 286 actions across reads, writes, and updates.
- 01
Create collaboration
Grant specific people or groups access to your files and folders on Box with customizable permission levels. This enables you to collaborate securely without sharing broader account access.
- 02
Create folder
Create a new folder in Box to organize and structure your file storage. Use this to build a logical folder hierarchy for managing documents, projects, and team resources.
- 03
Add shared link to file
Creates a shareable link for a file, allowing you to distribute it to clients, collaborators, or the public without needing to grant them direct Box account access.
- 04
Create task
Create a task attached to a file in Box to track action items, reviews, or deliverables that need attention. Tasks help organize work and ensure important file-related items don't get overlooked.