Guide
Dropbox AI Agent: Search, List, and Upload From Chat
If your files live in Dropbox rather than Drive, this is the connection that lets an agent find them and add to them. The mental model is slightly different from Drive, and knowing how saves some back-and-forth.
Dropbox thinks in paths
This is the one structural thing to absorb. Google Drive is a search-first system where files have IDs and folders are almost incidental. Dropbox is a filesystem: every action addresses a file by its path, the way you would on your own machine.
In practice that means an agent working in Dropbox needs to know where before it can do anything, and a request like “save this to my invoices folder” contains a path it has to resolve first. It can do that itself by searching, but the smoother setup is to tell it your handful of common paths once, in its instructions, rather than in every message.
Connect it in three steps
- Open openclawlaunch.com/integrations while signed in.
- Find Dropbox and click Connect, then approve the account whose files you want the agent working with.
- Ask it to find something. No config edit, no restart.
What the agent actually runs
composio search dropbox list folder
composio execute DROPBOX_LIST_FILES_IN_FOLDER '{"path":"/Invoices","limit":50}'DROPBOX_SEARCH_FILE_OR_FOLDER— find something by name when you do not know the pathDROPBOX_LIST_FILES_IN_FOLDERandDROPBOX_LIST_FOLDERS— walk the tree; both take a path and optional recursionDROPBOX_UPLOAD_FILE— put a file at a path; the content is a staged file rather than an inline stringDROPBOX_CREATE_FILE_REQUEST— generate a link someone else can upload into, which is a genuinely underused one
Uploads are a two-step flow
Unlike writing a text file to Drive, Dropbox uploads always go through staging: the file is staged first, and the resulting descriptor is what the upload action receives as its content. The agent handles this — the composio stage-file command exists precisely for it — but it explains something that otherwise looks odd, which is why the upload parameter is an object rather than the text you wanted to save.
The practical consequence: saving a short note into Dropbox is slightly more machinery than saving the same note into Drive. If note-saving is your main use case, that is a small point in Drive's favour. If you are moving real files around, it makes no difference.
Things worth asking for
- “Find the file with last year's tax return in it and tell me where it lives.”
- “What is in my Invoices folder from this quarter?”
- “Upload the screenshot I just sent you to /Design/Inbox.”
- “Create an upload link I can send the accountant for the receipts.”
- “List everything added to the shared folder in the last week.”
Limits and revoking access
100 executed actions a day on free trial and Lite, 1,000 on Pro; searching for the right action does not count against it. Adding your own Composio API key on the integrations page removes the cap and bills usage to your own Composio project. Disconnect from the same page at any time — the agent loses access on its next call.
Frequently asked questions
Dropbox or Google Drive — which should I connect?
Whichever already holds your files; there is no advantage to either on our side and you can connect both. The one practical difference worth knowing is that Drive has a dedicated action for writing text content directly, while Dropbox routes everything through its file upload path. For an agent that mostly saves notes and summaries, Drive is marginally less fiddly. For everything else it is a wash.
Why does the agent keep asking me for the folder path?
Because Dropbox is path-based, not search-first. Actions address files by path, so “put it in my invoices folder” requires the agent to know that path. Two fixes: let it call DROPBOX_SEARCH_FILE_OR_FOLDER to find the path itself, or state the paths you use regularly in your agent instructions once.
Can it read what is inside a file?
It can list and retrieve files, but Dropbox does not offer the built-in text-extraction step that Drive does. For “read this PDF and tell me what it says” workflows, either use Drive's parsing action, or pair Dropbox with a document tool such as MarkItDown in the dashboard tools catalog.
Does one connection cover all my instances?
Yes. Connections belong to your OpenClaw Launch account rather than to a container, so every OpenClaw and Hermes instance you own can use it, including ones you deploy later.