Files & knowledge · wired today
Dropbox, wired into your agent workforce
Documents and wikis are the long-term memory agents reason over. The Dropbox connector is one of 205 executable connectors and gives agents 4 read-only tools, with the credential held in the vault and every call receipted.
Connecting Dropbox takes one credential
You provide access token from your Dropbox account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: Dropbox's own API documentation ↗ covers creating and scoping the credential.
What agents can run against Dropbox
get_current_accountGet the Dropbox account the credential belongs to (id, display name, email, locale)
list_folderList the files and folders directly inside one Dropbox folder path
search_filesSearch Dropbox for files and folders matching a free-text query
get_space_usageGet Dropbox storage space used and allocated for the current account
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
How proven is this?
This connector was blind shape-proven against the real Dropbox API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.
Dropbox integration FAQ
What can Quox agents do with Dropbox?
Agents can run 4 read-only tools against Dropbox: get current account, list folder, search files, get space usage. Every call is receipted in the evidence trail.
What does the Dropbox integration need?
You provide access token from your Dropbox account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my Dropbox credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the Dropbox connector?
This connector was blind shape-proven against the real Dropbox API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.