# How to connect DocuSign to Hermes Agent (no API keys) > Connect DocuSign to Hermes with ClawLink in one click — 335 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/hermes/docusign Most guides for giving Hermes Agent DocuSign 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 DocuSign setup: pair once in the browser and your always-on Hermes agent can act on DocuSign for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. **Start here — 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. ## Setup It takes three steps to connect Hermes to DocuSign. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect DocuSign** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **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 docusign # connect DocuSign (browser OAuth) npx -y @useclawlink/cli actions docusign # list available actions npx -y @useclawlink/cli run docusign --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 DocuSign in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking Hermes: > Use DocuSign to add envelope attachments 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 DocuSign is connected in the dashboard, that agent calls the same 335 DocuSign 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). ## DocuSign MCP for Hermes Looking for a DocuSign MCP server for Hermes Agent? ClawLink connects DocuSign to Hermes Agent and exposes 335 DocuSign 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 DocuSign integration](https://claw-link.dev/openclaw/docusign) works the same way. ## What the Hermes Agent DocuSign integration can do 335 DocuSign 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 335. ### 30 of 335 DocuSign tools for Hermes | Tool | What it does | |---|---| | **Add envelope attachments** `docusign_add_envelope_attachments` | Add attachments to a DocuSign envelope | | **Add templates to envelope** `docusign_add_templates_to_envelope` | Add templates to a DocuSign envelope | | **Apply action to bulk send envelopes** `docusign_apply_action_to_bulk_send_envelopes` | Apply actions to bulk send envelopes | | **Create custom fields for envelope** `docusign_create_custom_fields_for_envelope` | Create custom fields for a DocuSign envelope | | **Create envelope from template** `docusign_create_envelope_from_template` | Create a DocuSign envelope from a template | | **Create recipient preview for envelope** `docusign_create_recipient_preview_for_envelope` | Create a recipient preview for a DocuSign envelope | | **Create sender view URL for envelope** `docusign_create_sender_view_url_for_envelope` | Create a sender view URL for a DocuSign envelope | | **Get account password rules** `docusign_get_account_password_rules` | Get DocuSign account password rules | | **Get bulk send lists information** `docusign_get_bulk_send_lists_information` | Get DocuSign bulk send lists | | **Get docusign account contacts** `docusign_get_docusign_account_contacts` | List DocuSign account contacts | | **Get envelope** `docusign_get_envelope` | Get a DocuSign envelope by ID | | **Get envelope document fields** `docusign_get_envelope_document_fields` | Get DocuSign envelope document fields | | **Get envelope lock information** `docusign_get_envelope_lock_information` | Get DocuSign envelope lock info | | **Get envelope notification defaults** `docusign_get_envelope_notification_defaults` | Get DocuSign envelope notification defaults | | **Create bulk send test request** `docusign_create_bulk_send_test_request` | This endpoint creates a Bulk Send Test Request to validate the compatibility between a bulk | | **Create document responsive HTML preview** `docusign_create_document_responsive_html_preview` | Creates a responsive HTML preview for a specific document in an envelope | | **Create preview of responsive HTML** `docusign_create_preview_of_responsive_html` | Creates a preview of the responsive HTML version of a specific template document in DocuSign | | **Create preview of responsive HTML in envelope** `docusign_create_preview_of_responsive_html_in_envelope` | Creates a preview of the responsive HTML versions of all documents in an envelope, allowing | | **Create recipient manual review link** `docusign_create_recipient_manual_review_link` | Creates a URL for manually reviewing a recipient's identity in DocuSign | | **Create recipient view URL** `docusign_create_recipient_view_url` | Creates a URL for embedding the DocuSign recipient view UI within an application, allowing | | **Create template recipient preview URL** `docusign_create_template_recipient_preview_url` | Generate a preview URL showing how a template will appear to recipients | | **Create template responsive HTML preview** `docusign_create_template_responsive_html_preview` | Creates a preview of the responsive HTML versions of all documents associated with a DocuSign | | **Create urlfor template edit view** `docusign_create_urlfor_template_edit_view` | Creates a URL for embedding the DocuSign Template Edit view within an application | | **Export brand to xmlfile** `docusign_export_brand_to_xmlfile` | Exports a DocuSign brand's configuration as an XML string | | **Fetch recipient names for email** `docusign_fetch_recipient_names_for_email` | Retrieves a list of all names associated with a specified email address in DocuSign | | **Generate edit view urlfor envelope** `docusign_generate_edit_view_urlfor_envelope` | Generates a URL for accessing and editing an existing envelope within the DocuSign UI, allowing | | **Generate envelope correction URL** `docusign_generate_envelope_correction_url` | Generates a URL that allows embedding the envelope correction view of the DocuSign UI within an | | **Generate recipient shared view URL** `docusign_generate_recipient_shared_view_url` | Generates a URL for embedding the DocuSign recipient view of a shared envelope in your | | **Get account billing charges list** `docusign_get_account_billing_charges_list` | Retrieves a detailed list of recurring and usage charges for a specified DocuSign account | | **Get account stamp image** `docusign_get_account_stamp_image` | Retrieves the image file for a specific account stamp, signature, or initials in DocuSign | ## Example prompts **Add Envelope Attachments** > Use DocuSign to add envelope attachments and walk me through the result in plain English. **Add Templates To Envelope** > Use DocuSign to add templates to envelope and walk me through the result in plain English. **Apply Action To Bulk Send Envelopes** > Use DocuSign to apply action to bulk send envelopes and walk me through the result in plain English. **Create Custom Fields For Envelope** > Create it in DocuSign for me, then confirm the important fields before you finish. ## 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 DocuSign working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a DocuSign app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect DocuSign 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 DocuSign. | 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 DocuSign actions to the runtime in a format your agent can reliably use. | 335 tools for DocuSign are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes DocuSign 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 DocuSign in the browser, and the 335 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use DocuSign 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 DocuSign 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 DocuSign tools DocuSign 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 DocuSign 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. ### DocuSign 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 DocuSign and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a Hermes Agent DocuSign integration? Yes. ClawLink is the fastest way to connect Hermes to DocuSign: link your DocuSign account once in the browser and Hermes Agent can call the DocuSign API through 335 ready-made tools — no custom code or token handling. ### How do I connect DocuSign 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 DocuSign 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 DocuSign to Hermes Agent? About two minutes. Sign in, click Connect next to DocuSign in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring DocuSign 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 DocuSign working from chat. ### Hermes paired but still can't use DocuSign 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 - [Hermes Moco integration](https://claw-link.dev/hermes/moco) — MOCO is a business management software offering project management, time tracking, and invoicing solutions. - [Hermes ClickUp integration](https://claw-link.dev/hermes/clickup) — Manage tasks, docs, goals, and sprints