Box
otherOverview
The Box connector connects RunMyProcess workflows to content stored in Box. A process can upload a file, download a file and list a folder, so documents move between the workflow and your content repository automatically, with Box's own permissions and retention still applying to what is stored.
Workflows use it to pick up documents submitted to a folder, pass them to extraction or review steps, and store the approved or generated results back in Box, keeping one controlled copy of each document instead of attachments scattered across email.
Common use cases
- Download documents submitted to a Box folder and send them to review or data extraction.
- Upload the generated or approved version of a document back to the case folder.
- List a folder to confirm that every required document is present before approval.
- Keep a single controlled copy of each contract or report in Box instead of email attachments.
Available Connectors
Security & Compliance
This integration is verified by RunMyProcess and supports OAuth2 authentication. Data is encrypted in transit and at rest.
Frequently asked questions
What can the Box connector do in a RunMyProcess workflow?
+
It uploads a file to a Box folder, downloads a file so a later step can work with it, and lists what a folder contains. Each operation is a step of the process, and the file and folder come from the case data.
Can a workflow file the documents it generates in Box?
+
Yes. A contract, report or signed document produced earlier in the process can be uploaded to the folder of the customer, project or case it belongs to, so the team finds it where it already keeps its files.
How does a workflow know which files are waiting in a folder?
+
The List Folder operation returns the folder's contents. A process can use it to pick up the files dropped into an intake folder, download each one and pass it to review, extraction or approval.
Need help connecting your systems?
Our integration team can help you map this connector into your existing workflows.