--- title: "Box Integration" description: "Connect AI agents to Box cloud storage. Agents manage the full file and folder lifecycle, control sharing and collaborators, apply metadata, and react to item changes in real time." url: https://flowrunner.ai/integrations/box date_modified: 2026-08-01T02:40:32-07:00 --- # Box [Storage](https://flowrunner.ai/integrations/category/storage) Connect AI agents to Box cloud storage. Agents manage the full file and folder lifecycle, control sharing and collaborators, apply metadata, and react to item changes in real time. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 3 triggers · 49 actions · OAuth · available [Box website](https://box.com/) · [Platform Documentation](https://developer.box.com/reference/) · Capability data verified 2026-08-12 1. A watched Box folder fires an On Folder Event for a new upload 2. Agent reads the file metadata and confirms the document type 3. Agent checks the file against the expected naming and folder rules 4. Agent applies a metadata template and moves the file to its destination folder 5. Agent creates a password-protected, expiring shared link for the recipient 6. Requesting team notified in chat with the shared link 7. External-share requests routed to the data owner for approval before the link is sent ## What This Integration Enables Agents handle the full Box file lifecycle: standard and chunked uploads for large files, downloads into flow storage, and the organize operations of create, move, copy, rename, and delete across files and folders. They manage version history, apply enterprise metadata templates, and run full-text search before acting. On the collaboration side, agents add, update, and remove collaborators, create and revoke shared links, and manage comments and review tasks. Three webhook triggers let a flow react in real time to file, folder, and collaboration changes. Trash operations let agents recover or permanently remove items under a defined guard. ### Without FlowRunner **Manual filing**: Exports and attachments are uploaded and sorted into folders by hand **Sharing without a trail**: Links are created ad hoc with no consistent expiry or access record **Access drift**: Collaborators are added once and rarely reviewed or revoked ### With FlowRunner **Filing happens in the flow**: Documents land in the right folder with metadata applied automatically **Consistent, expiring links**: Shared links are created with password and expiry on a defined policy **Access stays accountable**: Collaborator changes run through the flow with a record of who and why ## Use Case Scenarios ### Generated Document Filing and Delivery A flow generates a signed contract PDF and needs it filed and delivered. The agent calls Upload File to place it in the client's Box folder, applies a metadata instance so the document is searchable by client and contract type, and creates a file shared link with a password and a 14-day expiry. It then posts the link to the account manager. Filing, tagging, and controlled sharing happen as one step instead of three manual ones. ### Large Export Handling A nightly job produces a data export over 50 MB. The agent uses Upload Large File to push it reliably with chunked upload, moves it into the reporting folder, and removes the previous day's version after promoting the current one. The export lands where the finance team expects it without anyone babysitting a slow upload. ### External Share Approval A workflow needs to send a sensitive folder to an outside auditor. The agent prepares the folder shared link but does not release it. It routes the request to the data owner with the folder name and the intended recipient. On approval, the agent creates the link and delivers it; on denial, it logs the decision and stops. External access to sensitive content is a deliberate, recorded decision. ## Human-in-Loop Highlight Sharing content outside the organization is exactly the kind of action that should not happen silently. When an agent is about to create a shared link to an external recipient or grant a collaborator access to a sensitive folder, it pauses and routes to the data owner via Slack: "Request to share folder '\[folder name\]' with \[recipient\] as a viewer. Approve, change the role, or deny?" The owner decides. The agent then creates, adjusts, or cancels the collaboration, and the decision is recorded. Internal filing runs automatically; access that leaves the building gets a human in the loop. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 49 actions ### File Operations 8 - **Upload File** Uploads a file into a Box folder. Used to file generated documents, exports, and attachments without a manual upload. - **Upload Large File** Uploads files over 50 MB reliably using chunked upload. Used for big exports and media that a single-shot upload would fail on. - **Get File Info** Retrieves metadata for a single file. Used to confirm a file's type, size, or location before acting on it. - **Download File** Downloads a Box file into flow storage. Used to pull a document into a flow for parsing or further processing. - **Update File** Updates a file's name, description, or parent folder. Used to rename or relocate a file as part of an organize step. - **Move File** Moves a file to a different folder. Used to route documents to their destination after a validation step. - **Copy File** Copies a file to another folder. Used to distribute a document to multiple destinations without altering the original. - **Delete File** Sends a file to the Box trash. Used in cleanup workflows where the file may still need recovery. ### Versions 4 - **List File Versions** Lists the version history of a file. Used to audit how a document has changed over time. - **Get File Version** Retrieves a specific version of a file. Used to pull a prior revision for comparison or rollback. - **Promote File Version** Promotes an older version to be the current version. Used to roll a document back to a known-good revision. - **Delete File Version** Deletes a specific older version. Used to prune version history under a retention rule. ### Folder Operations 7 - **Create Folder** Creates a new folder. Used to stand up client or project folders on demand. - **Get Folder Info** Retrieves metadata for a folder. Used to confirm a folder's contents or location before filing into it. - **List Folder Items** Lists the files and subfolders inside a folder. Used to enumerate content before a batch operation. - **Update Folder** Updates a folder's name or parent. Used to reorganize structure programmatically. - **Move Folder** Moves a folder to a different parent. Used to restructure project hierarchies. - **Copy Folder** Copies a folder and its contents. Used to clone a template folder structure for a new client. - **Delete Folder** Sends a folder to the Box trash. Used in cleanup workflows with recovery still available. ### Sharing 3 - **Create File Shared Link** Creates a password-protected, expiring shared link for a file. Used to deliver a document with controlled access. - **Create Folder Shared Link** Creates a password-protected, expiring shared link for a folder. Used to grant time-bound access to a set of documents. - **Remove Shared Link** Removes an existing shared link. Used to cut off access once a deliverable is no longer being shared. ### Collaboration 6 - **Add Collaboration** Grants a user or group access to a file or folder. Used to onboard a collaborator into a project space. - **Get Collaboration** Retrieves a single collaboration record. Used to confirm an existing access grant. - **List Folder Collaborations** Lists the collaborators on a folder. Used in access reviews. - **List File Collaborations** Lists the collaborators on a file. Used to audit who can see a specific document. - **Update Collaboration** Changes a collaborator's role. Used to adjust access from editor to viewer or the reverse. - **Remove Collaboration** Revokes a collaborator's access. Used in offboarding and access-review cleanup. ### Comments and Tasks 10 - **Create Comment** Adds a comment to a file. Used to leave context for reviewers on a document. - **List File Comments** Lists comments on a file. Used to gather review feedback into a flow. - **Get Comment** Retrieves a single comment. Used to read a specific note for downstream action. - **Update Comment** Edits an existing comment. Used to correct or extend review notes. - **Delete Comment** Removes a comment. Used to clear resolved review notes. - **Create Task** Creates a review or approval task on a file. Used to assign a document for sign-off. - **List File Tasks** Lists tasks attached to a file. Used to track outstanding reviews. - **Get Task** Retrieves a single task. Used to read the status of a specific review. - **Update Task** Updates a task's status or details. Used to advance a review as it completes. - **Delete Task** Removes a task. Used to clear a review that no longer applies. ### Metadata 4 - **Create Metadata Instance** Applies an enterprise metadata template to a file. Used to tag documents so they are searchable and governable. - **Get Metadata Instance** Reads the metadata applied to a file. Used to drive routing decisions on a document's attributes. - **List Metadata Instances** Lists all metadata instances on a file. Used to audit how a document is classified. - **Delete Metadata Instance** Removes a metadata instance from a file. Used when a classification no longer applies. ### Trash and Account 7 - **List Trashed Items** Lists items currently in the trash. Used to review what is pending permanent deletion. - **Restore File** Recovers a file from the trash. Used to reverse an accidental deletion. - **Restore Folder** Recovers a folder from the trash. Used to reverse an accidental folder deletion. - **Permanently Delete File** Permanently removes a file from the trash. Used under a retention rule with a human guard. - **Permanently Delete Folder** Permanently removes a folder from the trash. Used under a retention rule with a human guard. - **Search Content** Runs a full-text search across an account or enterprise. Used to locate a document before acting on it. - **Get Current User** Retrieves the authenticated Box user. Used to confirm the connected account in a flow. ## Triggers 3 triggers ### Event Triggers 3 - **On File Event** Fires when a watched file is uploaded, deleted, moved, renamed, or otherwise changed. Initiates flows that file, tag, or notify on document changes in real time. - **On Folder Event** Fires when a watched folder is created, renamed, moved, deleted, or has a file uploaded into it. Initiates intake flows that process new content as it lands. - **On Collaboration Event** Fires when collaboration on a watched folder is created, accepted, rejected, updated, or removed. Initiates access-review flows that keep collaborator changes accountable. ## Frequently Asked Questions ### What can FlowRunner do with Box? FlowRunner agents can run Upload File, Get File Info, and Download File in Box, plus 46 more actions. ### Does connecting Box to FlowRunner require OAuth? Yes. Box connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Box trigger a FlowRunner workflow automatically? Yes. Box supports 3 triggers that can start a FlowRunner workflow automatically. **Work at Box?** This integration exposes Box to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/box. Site index: https://flowrunner.ai/llms.txt