# How to connect DocuSeal to Hermes Agent (paste one key, 22 tools) > Connect DocuSeal to Hermes with ClawLink: paste your DocuSeal key once and 22 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/docuseal Most guides for giving Hermes Agent DocuSeal 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 DocuSeal setup: pair once in the browser and your always-on Hermes agent can act on DocuSeal 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 DocuSeal. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect DocuSeal** — 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 docuseal # connect DocuSeal (browser OAuth) npx -y @useclawlink/cli actions docuseal # list available actions npx -y @useclawlink/cli run docuseal --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 DocuSeal in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your DocuSeal API key once. Verify the connection by asking Hermes: > Pull the relevant data from DocuSeal, summarize it in plain English, and point out anything that needs attention. ### 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 DocuSeal is connected in the dashboard, that agent calls the same 22 DocuSeal 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). ## DocuSeal MCP for Hermes Looking for a DocuSeal MCP server for Hermes Agent? ClawLink connects DocuSeal to Hermes Agent and exposes 22 DocuSeal 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 DocuSeal integration](https://claw-link.dev/openclaw/docuseal) works the same way. ## What the Hermes Agent DocuSeal integration can do 22 DocuSeal tools are ready for Hermes Agent once the account is connected. ### All 22 DocuSeal tools for Hermes | Tool | What it does | |---|---| | **Get submission** `docuseal_get_submission` | Retrieve detailed information about a specific submission | | **Get submission documents** `docuseal_get_submission_documents` | Retrieve documents for a submission | | **Get submitter** `docuseal_get_submitter` | Retrieve detailed information about a submitter by ID | | **Get template** `docuseal_get_template` | Retrieve details of a specific template by its unique identifier | | **List submissions** `docuseal_list_submissions` | List document submissions with filtering and cursor-based pagination | | **List submitters** `docuseal_list_submitters` | Retrieve a paginated list of submitters with optional filtering | | **List templates2** `docuseal_list_templates2` | Retrieve a list of available document templates with pagination and filtering | | **Archive submission** `docuseal_archive_submission` | Archive a submission by its unique identifier | | **Clone template2** `docuseal_clone_template2` | Clone an existing template into a new template with optional custom name, folder, and | | **Create submission** `docuseal_create_submission` | Create signature requests (submissions) from an existing document template and send them to | | **Create submission from docx** `docuseal_create_submission_from_docx` | Create a one-off submission (signature request) from a DOCX document with dynamic content | | **Create submission from HTML** `docuseal_create_submission_from_html` | Create a one-off submission request from HTML content with embedded field tags rendered as a | | **Create submission from PDF** `docuseal_create_submission_from_pdf` | Create a one-off submission (signature request) from a PDF file | | **Create submissions from emails** `docuseal_create_submissions_from_emails` | Create submissions for a document template and send them to specified email addresses | | **Create template from docx** `docuseal_create_template_from_docx` | Create a fillable document template from a Microsoft Word DOCX file | | **Create template from html2** `docuseal_create_template_from_html2` | Create a fillable document template from HTML content with pre-defined fields | | **Create template from PDF** `docuseal_create_template_from_pdf` | Create a fillable document template from a PDF file | | **Merge templates** `docuseal_merge_templates` | Merge multiple DocuSeal templates into a single combined template | | **Update submitter** `docuseal_update_submitter` | Update submitter details, pre-fill or update field values, re-send signature request emails, or | | **Update template2** `docuseal_update_template2` | Update a document template by moving it to a different folder, changing its name, updating | | **Archive template** `docuseal_archive_template` | Archive a specific template by its unique identifier | | **Update template documents** `docuseal_update_template_documents` | Add, remove, or replace documents in a template with provided PDF/DOCX file or HTML content | ## Example prompts **Get Submission** > Pull the relevant data from DocuSeal, summarize it in plain English, and point out anything that needs attention. **Get Submission Documents** > Pull the relevant data from DocuSeal, summarize it in plain English, and point out anything that needs attention. **Get Submitter** > Pull the relevant data from DocuSeal, summarize it in plain English, and point out anything that needs attention. **Get Template** > Pull the relevant data from DocuSeal, 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 DocuSeal working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the DocuSeal API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected DocuSeal 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 DocuSeal. | 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 DocuSeal actions to the runtime in a format your agent can reliably use. | 22 tools for DocuSeal are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes DocuSeal 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 DocuSeal in the browser, and the 22 tools above work from chat. There is no SDK and no config file, and the DocuSeal 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 DocuSeal 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 DocuSeal 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 DocuSeal tools DocuSeal 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 DocuSeal 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. ### DocuSeal 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 DocuSeal 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 DocuSeal integration? Yes. ClawLink is the fastest way to connect Hermes to DocuSeal: link your DocuSeal account once in the browser and Hermes Agent can call the DocuSeal API through 22 ready-made tools — no custom code or token handling. ### How do I connect DocuSeal 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 DocuSeal in the dashboard and Hermes can use it from the next message — no config files, and the DocuSeal key you paste is stored server-side instead of in your environment. ### How long does it take to connect DocuSeal to Hermes Agent? About two minutes. Sign in, click Connect next to DocuSeal in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring DocuSeal 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 DocuSeal working from chat. ### Hermes paired but still can't use DocuSeal 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 - [Connect GitHub](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture tools](https://claw-link.dev/hermes/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.