Dropbox
Upload, download, and manage files and folders in Dropbox.
About
Dropbox ships in the w6w first-party pack. It declares 12 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.dropbox- Version
- 0.2.2
- Author
- w6w
- Licence
- MIT
- Categories
- Storage
Overview
Dropbox gives a workflow full file and folder management — uploading and downloading files, listing a folder’s contents, and copying, moving and deleting both files and folders as part of a larger process.
Search covers finding a file or folder by name across an account without already knowing its path, and file metadata can be read on its own when a workflow needs to check size, modification time or existence before acting on a file.
Useful for moving files between Dropbox and another system — archiving an upload, distributing a generated document, or syncing a folder’s contents as part of a broader automation — without building direct integration against Dropbox’s own SDK.
Build with Dropbox
Three routes to the same 12 actions. The Workflow tab is generated from Dropbox's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Upload File
upload-file Upload text content to a path in Dropbox. Uses the content endpoint; the parent folder must exist.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Dropbox's real ids.
{
"manifestVersion": "2",
"name": "dropbox-example",
"steps": [
{
"id": "copy-file",
"uses": {
"app": "io.w6w.dropbox",
"action": "copy-file",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"fromPath": "<fromPath>",
"toPath": "<toPath>"
}
}
]
}Here are some of the things you can do
-
Copy File
performcopy-file -
Copy Folder
performcopy-folder -
Create Folder
performcreate-folder -
Download File
readdownload-file -
Get File Metadata
readget-file-metadata
+7 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Dropbox, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Dropbox. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "upload-file",
payload: {
path: "<value>",
content: "<value>",
// mode: "<value>",
// autorename: "<value>",
// mute: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action upload-file --payload '{"path":"<value>","content":"<value>"}'Give an AI agent Dropbox — without giving it Dropbox's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.dropbox#copy-file",
"input": {
"fromPath": "<fromPath>",
"toPath": "<toPath>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Dropbox connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Dropbox's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Dropbox itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Dropbox declares its own checks, so its health is a property of the app rather than something the host guesses at.
Dropbox platform status
Atlassian Statuspage rollup for status.dropbox.com, with per-component detail. Unauthenticated and unsigned.