ChatGPT Connectors for Dropbox
You can get Dropbox files into ChatGPT through file uploads or a custom connector. Here is what each route allows, the permission boundaries to check, and how to keep your reviewed document links.
Updated 5 min read
You can get Dropbox files into a ChatGPT session by uploading them to a conversation or by building a custom connector on the ChatGPT connector platform. There is no first-party Dropbox connector in ChatGPT's standard catalog. Understanding what each route actually gives ChatGPT access to saves time when the connection does not behave as expected. Tools like fenbs can keep the reviewed document links and project decisions in a place that outlasts any single chat session.
This page covers the two main routes, the access each one provides, and the permission boundaries to verify before you rely on either.
Upload Dropbox files to a conversation
The quickest way to use a Dropbox file in ChatGPT is to download it from Dropbox and upload it directly to a ChatGPT conversation. ChatGPT can read PDFs, Word documents, plain text files and spreadsheets you attach. You can 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 the connection is manual and one-way: ChatGPT sees only the file you upload, not the current state of the folder it came from. If the document changes in Dropbox after you upload it, your copy is out of date.
Build a custom connector with the Dropbox API
Dropbox has a REST API with OAuth 2.0. You can build a custom connector that lets ChatGPT search your Dropbox, retrieve file metadata, and download specific files 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 file names and content, read folder structures, and retrieve file content in formats it can process. For the underlying connector mechanics, including OAuth registration, see chatgpt connectors api.
Permission boundaries to check
Dropbox's permission model can affect what a connector sees. Check these before building or testing.
- Account scope: the connector uses the OAuth token of the account that authorized it. It can only see files and folders that account has access to.
- Team folders: in Dropbox Business accounts, team folders have separate permissions. The connector needs explicit access to a team folder to read its contents.
- Shared links: a shared link gives a connector access to a specific file or folder, but not to the broader account.
- File type: Dropbox stores any file, but ChatGPT can only read text-based formats directly. Images, videos and other binaries need conversion.
Keeping reviewed document links and decisions
Reviewing Dropbox files in a ChatGPT session often produces conclusions: this version was approved, that clause needs legal sign-off, the numbers in section three are wrong. Those conclusions belong somewhere outside the chat, not just in a transcript that the next session cannot access. A new session that opens the same Dropbox file has no way of knowing that the previous session already reviewed it and reached a conclusion unless that conclusion was recorded somewhere the new session can read.
fenbs keeps those conclusions as Links and listings (the specific Dropbox documents reviewed and their current status), Decisions and rules (what was accepted or flagged), and task progress (what still needs attention). For privacy considerations when connecting cloud storage to ChatGPT, see chatgpt connectors privacy.
Document review workflows that rely on AI assistance face a specific problem when reviews span more than one session. A session that reviews a contract might flag three clauses as acceptable and note that one section needs legal input. If that finding is only in the chat transcript, the next session starts without it: it may flag the same acceptable clauses again, or miss the one that still needs attention. Storing the per-document findings in fenbs, with each Dropbox document linked and its status noted, means the next session picks up where the last one stopped rather than re-reviewing work that is already done. This matters most for longer reviews where documents are read and revisited over days rather than in one sitting. It also matters when more than one person uses AI to review the same set of documents, since a shared record prevents two reviewers from reaching contradictory conclusions without knowing it.
Track which Dropbox documents were reviewed and what was found
Add each reviewed document as a link in fenbs with its review status and key finding. Write the accepted decisions as Decisions and rules. Connect ChatGPT from Integrations and ask it to read the fenbs context before starting, so it knows which files were already reviewed and what the conclusions were.
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 and the documents under review as tasks or links.
- For each reviewed document, record the finding and outcome in Decisions and rules or as 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 status of documents it reviewed.
fenbs does not connect to Dropbox. It keeps the document links, findings, and project decisions your AI sessions build on. For related connector workflows, see chatgpt connectors and apps and chatgpt connectors not working. For a similar workflow with Google Drive, see give chatgpt access to google drive.