ChatGPT Connector for Box: Setup and Document Workflows
You can connect Box to ChatGPT through a custom connector or by uploading specific files to a conversation. Here is what each option gives ChatGPT access to and how to keep your reviewed source links.
Updated 5 min read
You can connect Box to ChatGPT through a custom connector on the ChatGPT connector platform or by downloading files from Box and uploading them to a conversation. There is no first-party Box connector in ChatGPT's standard catalog. Tools like fenbs can keep the project links, reviewed document notes, and accepted findings in a place that lasts beyond any single chat session.
This page covers the two main connection options, the access each one provides, and the permission checks worth running before you rely on either.
Upload Box files to a conversation
The simplest route is to download a document from Box and upload it to a ChatGPT conversation. ChatGPT can read PDFs, Word documents, spreadsheets and plain text files that you attach. You can then ask questions about the document, extract key points, or use the content to draft a response.
This works without any connector setup. The limit is that it is manual: you need to download and re-upload the document for each session, and ChatGPT has no ongoing access to Box. If the document changes in Box, your uploaded copy does not update.
Build a custom connector with the Box API
Box has a REST API with OAuth 2.0 support. You can build a custom connector that lets ChatGPT search Box, retrieve file metadata, and read document content during a conversation. Building a connector requires developer mode in ChatGPT. Which plans include developer mode is OpenAI's to confirm: check OpenAI's help center (opens in a new tab).
With a working connector, ChatGPT can search your Box content, retrieve specific files, read folder structures, and access file metadata such as version history and shared link status. For the underlying connector mechanics, see chatgpt connectors api.
Permission checks to run before you connect
Box has a granular permission model. Before building or using a connector, check the following.
- OAuth app scope: Box OAuth apps can request scopes for reading content, managing files, and reading user info. Request only the scopes your workflow needs.
- Folder permissions: the authenticated account must have at least Viewer access to a folder for the connector to read its contents. Content shared only with other team members is not accessible.
- Managed users: in enterprise Box accounts, access to other users' content requires explicit sharing. A connector authenticated as one user cannot read another user's private folders.
- File type limits: Box can store any file type, but reading content requires a format ChatGPT can process. Binary files, images and non-text formats need conversion first.
Keeping project links and accepted findings
A Box connector gives ChatGPT access to your files, but not to the conclusions your team drew from them. Which version was reviewed, what was accepted, and what questions are still open: those live in chat histories that disappear between sessions.
fenbs keeps those conclusions as Links and listings (the specific Box documents reviewed and their status), Decisions and rules (what was accepted and what was rejected), and task progress (what still needs review). The next AI session reads that record instead of starting blank. For privacy considerations when connecting document tools, see chatgpt connectors privacy.
Box is often used where document provenance matters: legal reviews, compliance checks, financial analysis, and contract workflows. In these cases, knowing not just which document was read but what was concluded from it is as important as the document itself. A ChatGPT session that reviews a Box document might determine that a clause is acceptable, that a signature page is missing, or that the version in the folder is not the one approved at the relevant meeting. Those findings need to be recorded before the session ends.
fenbs is a natural place for that record. A link to the specific Box document, the version reviewed, the key finding, and the next action all belong together. When the next session opens, whether in ChatGPT, Claude, or another connected assistant, it reads that record and knows which documents were already reviewed, what was found, and what still needs attention. This saves time on re-reviewing documents and reduces the risk of a later session treating an already-resolved issue as still open. For teams that use Box for compliance or legal work, this record also provides a clear audit trail of which AI-assisted reviews were conducted, what was found, and what was decided as a result.
Track reviewed documents and accepted findings
Add each reviewed Box document as a link in fenbs with its review status and the key finding. Write the accepted decisions as Decisions and rules. Connect ChatGPT from Integrations and ask it to read the fenbs context before each session, so it knows which documents were already reviewed and what was concluded.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
How to do this with fenbs
- Create a free account. One person is free with no credit card.
- Add your project. Write a short goal description and add the documents under review as tasks or links.
- For each reviewed document, write the key finding and outcome as a Decisions and rules entry or a task note.
- Connect ChatGPT to fenbs from Integrations using the MCP setup guide.
- At the start of each session ask ChatGPT to read the fenbs context. Before stopping, ask it to record any new findings and update the review status of any documents it examined.
fenbs does not connect to Box directly. It keeps the document links, findings, and project decisions that AI sessions work from. For related connector workflows, see chatgpt connectors and apps and chatgpt connectors not working.