How to connect Boldsign to Hermes Agent
Connect Boldsign to Hermes with ClawLink in one click — 14 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
BoldsignOAUTH2MCPSend, sign, and manage electronic documents and agreements. Once connected, Hermes Agent can read and act on Boldsign from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Boldsign 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 Boldsign setup: pair once in the browser and your always-on Hermes agent can act on Boldsign for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into Hermes to install the plugin and pair your account.
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. It prints an approval link, so show me the link and stop, don't wait:
hermes clawlink begin
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.Setup
It takes three steps to connect Hermes to Boldsign.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Boldsign
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Boldsign?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
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 testThen connect Boldsign in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking Hermes:
Use Boldsign to brand get 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Boldsign is connected in the dashboard, that agent calls the same 14 Boldsign tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Boldsign MCP for Hermes
Looking for a Boldsign MCP server for Hermes Agent? ClawLink connects Boldsign to Hermes Agent and exposes 14 Boldsign tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Boldsign integration works the same way.
What the Hermes Agent Boldsign integration can do
14 Boldsign tools are ready for Hermes Agent once the account is connected.
All 14 Boldsign tools for Hermes
| Tool | What it does |
|---|---|
Brand get boldsign_brand_get | Get brand details by brand ID |
Brand list boldsign_brand_list | List all brands in the account |
Document behalf list boldsign_document_behalf_list | List documents sent on behalf of users |
Document list boldsign_document_list | List documents in My Documents with filters |
Document team list boldsign_document_team_list | List team documents |
Plan get API credits count boldsign_plan_get_api_credits_count | Get remaining BoldSign API credits count |
Custom field create boldsign_custom_field_create | Create a brand-scoped custom field |
Custom field edit boldsign_custom_field_edit | Edit an existing custom field |
Document edit beta boldsign_document_edit_beta | Edit a draft or sent document |
Document extend expiry boldsign_document_extend_expiry | Extend a document's expiry date |
Document send boldsign_document_send | Send a document for eSignature |
Embedded request create link boldsign_embedded_request_create_link | Create an embedded request link |
File upload boldsign_file_upload | Helper action to upload a file to R2 temp via the Composio file pipeline, returning a key that |
Document remove authentication boldsign_document_remove_authentication | Remove authentication from a document |
Try it: find the Boldsign tool you need
Browse the 14 Boldsign tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use Boldsign to brand get and walk me through the result in plain English.
Use Boldsign to brand list and walk me through the result in plain English.
Use Boldsign to document behalf list and walk me through the result in plain English.
Use Boldsign to document list and walk me through the result in plain English.
ClawLink vs. building it yourself
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 Boldsign working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Boldsign app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Boldsign through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Boldsign. | 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 Boldsign actions to the runtime in a format your agent can reliably use. | 14 tools for Boldsign are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Boldsign 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 Boldsign in the browser, and the 14 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
Hermes paired but still can't use Boldsign
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 Boldsign 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 Boldsign tools
Boldsign 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 Boldsign 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.
Boldsign 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.
OAuth finished in the browser but the account is still missing
Try reconnecting Boldsign and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a Hermes Agent Boldsign integration?
Yes. ClawLink is the fastest way to connect Hermes to Boldsign: link your Boldsign account once in the browser and Hermes Agent can call the Boldsign API through 14 ready-made tools — no custom code or token handling.
How do I connect Boldsign 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 Boldsign in the dashboard and Hermes can use it from the next message — no config files or API keys to manage.
How long does it take to connect Boldsign to Hermes Agent?
About two minutes. Sign in, click Connect next to Boldsign in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Boldsign up myself?
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 Boldsign working from chat.
Hermes paired but still can't use Boldsign
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.
