How to connect Dropbox to Hermes Agent

Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.

Reconnect Dropbox from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

Dropbox tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Dropbox call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.

Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.

The dominant Dropbox failure on the ClawLink runtime. The agent passed a local file path (like /home/user/.openclaw/media/inbound/report.pdf) to dropbox_upload_file, but the file never left your machine, so there is nothing to upload. The server needs the file's bytes attached to the call, or a URL it can fetch that is publicly accessible on the internet. Ask the agent to attach the file itself rather than naming a path; if it is working from a link, the link must not require login or a localhost address. The error names the offending s3key, so check whether the agent invented it from a path on your disk.

Ask the agent to diagnose it:

Retry the Dropbox upload, but attach the actual file bytes to the content argument instead of passing a filesystem path. Show me the arguments you plan to send before you send them.

The agent guessed a tool name that does not exist. The real tool is dropbox_list_files_in_folder; dropbox_list_folder_continue is the pagination tool that follows a has_more cursor. ClawLink returns a "Did you mean" line on every miss, so ask the agent to read it and retry with the suggested name, or list the Dropbox catalog first and pick from it.

Ask the agent to diagnose it:

List the available Dropbox tools, show me the real names, and retry with `dropbox_list_files_in_folder`.

Another guessed name: Dropbox tools write through dropbox_upload_file (bytes attached, up to ~150MB) rather than a generic create-file tool. If the goal was a folder, dropbox_create_folder is the real name. Read the "Did you mean" line and retry with a real tool.

Ask the agent to diagnose it:

Retry with `dropbox_upload_file` and the file attached, or `dropbox_create_folder` if I asked for a folder.

Dropbox writes are confirmation-gated: the runtime refuses to run dropbox_upload_file until the user confirms the call. This is by design, not an error. Approve the confirmation prompt when it appears, or tell the agent to confirm the upload target with you before calling. The same gate applies to other write tools such as dropbox_share_folder.

Ask the agent to diagnose it:

Tell me the exact path and file name you plan to upload before calling dropbox_upload_file again.

A real prod error: the agent called a Dropbox tool (in the recorded case, an upload-adjacent call) without the path argument. Dropbox addresses everything by path or folder ID, so the agent needs the target folder path (like /invoices) before writing. Run dropbox_list_files_in_folder with a folder ID or root path first to get real references, then retry with the path filled in.

Ask the agent to diagnose it:

List the target folder with dropbox_list_files_in_folder, then retry the failing call with the real path.

Dropbox permissions are per item, so a single 403 with other calls working means the connected account lacks permission on that specific file or folder. The causes, in Dropbox terms: the account is not the owner, the item is in a shared folder the account can view but not edit, a Dropbox Business admin restricted the app or the folder, or the agent passed a placeholder id instead of a real one. Run a list or search tool and retry with a real path or folder ID from the results. If the account genuinely lacks access, share the item to the connected account's email or ask the owner to grant edit access.

Ask the agent to diagnose it:

Run dropbox_search_file_or_folder or dropbox_list_files_in_folder and show me the real paths. Then retry the failing action with a real path, and tell me who owns the file.

Try reconnecting Dropbox and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.

Yes. ClawLink is the fastest way to connect Hermes to Dropbox: link your Dropbox account once in the browser and Hermes Agent can call the Dropbox API through 111 ready-made tools — no custom code or token handling.

Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Dropbox in the dashboard and Hermes can use it from the next message — no config files or API keys to manage.

About two minutes. Sign in, click Connect next to Dropbox in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Dropbox working from chat.

No. The manual route for a Hermes-Dropbox connection is a Dropbox app: register one in the Dropbox App Console, enable scoped access, generate a token, and handle refresh yourself. ClawLink's Dropbox app is already registered, so you connect your account in the browser and the tools work without you ever generating or storing a token. Dropbox has no static machine-to-machine keys at all, so "no API keys" here means exactly that; what the connection uses is an OAuth grant, and revoking it in your Dropbox account settings (connected apps) ends the access immediately.

111 tools. The tabulated 30 are the ones people reach for most: upload, create folder, copy and move, create shared links, list folder contents, read files, search, file revisions, and space usage. The rest of the catalog covers batch operations, account info, save-from-URL, and export. Dropbox's own MCP server covers a narrower read-and-search surface, so most of what an agent does with a Dropbox account from chat, like uploading or sharing, is only available through a connection like this one.

The AI Overview answers this with prompt-injection warnings from files and over-privileged access. Both apply here, with a hosted-flow control the manual guides never mention: there is no token on your machine to leak. The grant lives on the ClawLink side, is scoped to your Dropbox account, and can be revoked at any time from your Dropbox connected-apps settings. The file-content warning is still real: files an agent reads can contain instructions, so keep untrusted documents out of the folders the agent works in, or review what it does with their contents.

Dropbox permissions are per file and per folder, not per connection. The usual causes, in Dropbox terms: the connected account is not the owner of the file or folder, the file lives in a shared folder the account can see but not modify, a Dropbox Business admin has restricted the app or the folder, or the agent sent a placeholder id instead of a real one. Run a list or search tool first to get real file and folder references, and check ownership on the item before blaming the connection.

Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.