# How to connect Dropbox Sign to Hermes Agent (paste one key, 56 tools) > Connect Dropbox Sign to Hermes with ClawLink: paste your Dropbox Sign key once and 56 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/dropbox-sign Most guides for giving Hermes Agent Dropbox Sign access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Dropbox Sign setup: pair once in the browser and your always-on Hermes agent can act on Dropbox Sign for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect Hermes to Dropbox Sign. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Dropbox Sign** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect dropbox-sign # connect Dropbox Sign (browser OAuth) npx -y @useclawlink/cli actions dropbox-sign # list available actions npx -y @useclawlink/cli run dropbox-sign --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect Dropbox Sign in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Dropbox Sign API key once. Verify the connection by asking Hermes: > Use Dropbox Sign to download signature request files and walk me through the result in plain English. ### Using a different agent? The Hermes plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Dropbox Sign is connected in the dashboard, that agent calls the same 56 Dropbox Sign tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Dropbox Sign MCP for Hermes Looking for a Dropbox Sign MCP server for Hermes Agent? ClawLink connects Dropbox Sign to Hermes Agent and exposes 56 Dropbox Sign tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw Dropbox Sign integration](https://claw-link.dev/openclaw/dropbox-sign) works the same way. ## What the Hermes Agent Dropbox Sign integration can do 56 Dropbox Sign tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 56. ### 30 of 56 Dropbox Sign tools for Hermes | Tool | What it does | |---|---| | **Download signature request files** `dropbox_sign_download_signature_request_files` | Download files for a signature request as PDF (merged) or ZIP (individual documents) | | **Get account** `dropbox_sign_get_account` | Retrieves detailed information about a Dropbox Sign account including quotas, payment status | | **Get API app** `dropbox_sign_get_api_app` | Retrieve information about an API App by its client ID | | **Get bulk send job** `dropbox_sign_get_bulk_send_job` | Retrieve the status of a bulk send job | | **Get current team** `dropbox_sign_get_current_team` | Get the current team membership status and details | | **Get embedded sign URL** `dropbox_sign_get_embedded_sign_url` | Retrieves an embedded signing URL for a specific signer's signature | | **Get embedded template edit URL** `dropbox_sign_get_embedded_template_edit_url` | Generate an edit URL for embedded template editing | | **Get fax line area codes** `dropbox_sign_get_fax_line_area_codes` | Retrieve available fax line area codes for a given country, state/province, and city | | **Get signature request** `dropbox_sign_get_signature_request` | Retrieves the current status and complete details of a signature request by ID | | **Get signature request files as data uri** `dropbox_sign_get_signature_request_files_as_data_uri` | Download signature request files as a base64-encoded data URI | | **Get signature request files as file URL** `dropbox_sign_get_signature_request_files_as_file_url` | Retrieves a copy of the current documents and returns a JSON object with a URL to the file | | **Get team info** `dropbox_sign_get_team_info` | Retrieves information about a Dropbox Sign team, including team name, member count, and | | **Get template** `dropbox_sign_get_template` | Return the specified template | | **Get template files** `dropbox_sign_get_template_files` | Download documents associated with a template | | **Get template files as data uri** `dropbox_sign_get_template_files_as_data_uri` | Retrieve template documents as base64-encoded data URI | | **Get template files as file URL** `dropbox_sign_get_template_files_as_file_url` | Retrieve a copy of template documents and return a JSON object with a URL to the file (PDFs | | **List API apps** `dropbox_sign_list_api_apps` | List API Apps | | **List bulk send jobs** `dropbox_sign_list_bulk_send_jobs` | List bulk send jobs | | **List fax lines** `dropbox_sign_list_fax_lines` | List fax lines and their properties | | **List faxes** `dropbox_sign_list_faxes` | List faxes and their properties | | **List signature requests** `dropbox_sign_list_signature_requests` | List signature requests | | **List sub teams** `dropbox_sign_list_sub_teams` | Lists all sub-teams belonging to a parent team with pagination support | | **List team members** `dropbox_sign_list_team_members` | Lists all members and their roles for a specific team | | **List teams** `dropbox_sign_list_teams` | Lists all Dropbox Sign teams accessible to the authenticated user, including the current team | | **List templates** `dropbox_sign_list_templates` | List templates | | **O auth authorize** `dropbox_sign_o_auth_authorize` | Generate an OAuth authorization URL | | **Verify account** `dropbox_sign_verify_account` | Verify whether a Dropbox Sign account exists for the given email | | **Add user to team** `dropbox_sign_add_user_to_team` | Invite a user to your Team | | **Add user to template** `dropbox_sign_add_user_to_template` | Grant a specified account access to a template | | **Bulk create embedded sig req with template** `dropbox_sign_bulk_create_embedded_sig_req_with_template` | Create a BulkSendJob for embedded templated signature requests | ## Example prompts **Download Signature Request Files** > Use Dropbox Sign to download signature request files and walk me through the result in plain English. **Get Account** > Pull the relevant data from Dropbox Sign, summarize it in plain English, and point out anything that needs attention. **Get Api App** > Pull the relevant data from Dropbox Sign, summarize it in plain English, and point out anything that needs attention. **Get Bulk Send Job** > Pull the relevant data from Dropbox Sign, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key 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 Sign working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Dropbox Sign API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Dropbox Sign account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Dropbox Sign. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Dropbox Sign actions to the runtime in a format your agent can reliably use. | 56 tools for Dropbox Sign are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Dropbox Sign to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Hermes Agent users instead. You install the plugin once, connect Dropbox Sign in the browser, and the 56 tools above work from chat. There is no SDK and no config file, and the Dropbox Sign key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Dropbox Sign 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`. ### Connection succeeds but no tools appear Reconnect Dropbox Sign from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Dropbox Sign tools Dropbox Sign 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 Sign 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. ### Dropbox Sign returns 403 or "permission denied" on one action while others work 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. ### API key setup works but results look incomplete Double-check that the API key for Dropbox Sign has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a Hermes Agent Dropbox Sign integration? Yes. ClawLink is the fastest way to connect Hermes to Dropbox Sign: link your Dropbox Sign account once in the browser and Hermes Agent can call the Dropbox Sign API through 56 ready-made tools — no custom code or token handling. ### How do I connect Dropbox Sign to Hermes with ClawLink? 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 Sign in the dashboard and Hermes can use it from the next message — no config files, and the Dropbox Sign key you paste is stored server-side instead of in your environment. ### How long does it take to connect Dropbox Sign to Hermes Agent? About two minutes. Sign in, click Connect next to Dropbox Sign in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Dropbox Sign up myself? The alternative to ClawLink is usually manual API key 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 Sign working from chat. ### Hermes paired but still can't use Dropbox Sign 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`. ## Related - [Trello](https://claw-link.dev/hermes/trello) — Manage boards, lists, and cards - [Moco](https://claw-link.dev/hermes/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions. - [ClickUp](https://claw-link.dev/hermes/clickup) — Manage tasks, docs, goals, and sprints