# How to connect CertSeal to Hermes Agent (paste one key, 21 tools) > Connect CertSeal to Hermes with ClawLink: paste your CertSeal key once and 21 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/cert-seal Most guides for giving Hermes Agent CertSeal 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 CertSeal setup: pair once in the browser and your always-on Hermes agent can act on CertSeal 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 CertSeal. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect CertSeal** — 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 cert-seal # connect CertSeal (browser OAuth) npx -y @useclawlink/cli actions cert-seal # list available actions npx -y @useclawlink/cli run cert-seal --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 CertSeal in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your CertSeal API key once. Verify the connection by asking Hermes: > Pull the relevant data from CertSeal, 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 CertSeal is connected in the dashboard, that agent calls the same 21 CertSeal 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). ## CertSeal MCP for Hermes Looking for a CertSeal MCP server for Hermes Agent? ClawLink connects CertSeal to Hermes Agent and exposes 21 CertSeal 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 CertSeal integration](https://claw-link.dev/openclaw/cert-seal) works the same way. ## What the Hermes Agent CertSeal integration can do 21 CertSeal tools are ready for Hermes Agent once the account is connected. The 19 below are the ones people reach for most; your agent can call all 21. ### 19 of 21 CertSeal tools for Hermes | Tool | What it does | |---|---| | **Get batch** `cert_seal_get_batch` | Get one active or archived certificate batch by ID | | **Get certificate** `cert_seal_get_certificate` | Look up an issued certificate using either its human-readable certificate ID or its | | **Get current workspace** `cert_seal_get_current_workspace` | Verify the connected CertSeal API key and return the workspace ID and username it belongs to | | **Get recipient** `cert_seal_get_recipient` | Get one issued certificate recipient record by batch ID and recipient ID | | **Get webhook subscription** `cert_seal_get_webhook_subscription` | Get one webhook subscription by ID | | **List batches** `cert_seal_list_batches` | Return one newest-first page of certificate batches in the connected workspace, optionally | | **List designs** `cert_seal_list_designs` | Return one newest-first page of reusable certificate designs | | **List recipients** `cert_seal_list_recipients` | Return one page of issued certificate recipients in a batch, optionally filtered by email | | **List webhook subscriptions** `cert_seal_list_webhook_subscriptions` | Return one newest-first page of webhook subscriptions | | **Create batch** `cert_seal_create_batch` | Create a persistent certificate batch from an existing CertSeal design and optional email | | **Create webhook subscription** `cert_seal_create_webhook_subscription` | Create a persistent webhook subscription for selected certificate events | | **Issue certificates** `cert_seal_issue_certificates` | Atomically issue certificates without sending email for 1-100 recipients in one active batch | | **Set batch archived** `cert_seal_set_batch_archived` | Idempotently archive or unarchive a batch | | **Update recipient** `cert_seal_update_recipient` | Partially update an issued certificate recipient | | **Issue and send certificates** `cert_seal_issue_and_send_certificates` | Atomically issue certificates for 1-100 recipients and queue email delivery for every created | | **Rotate webhook signing secret** `cert_seal_rotate_webhook_signing_secret` | Immediately invalidate a webhook subscription's current signing secret and replace it | | **Send certificate emails** `cert_seal_send_certificate_emails` | Sequentially queue real certificate emails for 1-25 existing recipients in one active batch | | **Send recipient certificate email** `cert_seal_send_recipient_certificate_email` | Queue asynchronous certificate email delivery to one recipient | | **Test webhook subscription** `cert_seal_test_webhook_subscription` | Enqueue one synthetic signed event through CertSeal's normal webhook dispatcher | ## Example prompts **Get Batch** > Pull the relevant data from CertSeal, summarize it in plain English, and point out anything that needs attention. **Get Certificate** > Pull the relevant data from CertSeal, summarize it in plain English, and point out anything that needs attention. **Get Current Workspace** > Pull the relevant data from CertSeal, summarize it in plain English, and point out anything that needs attention. **Get Recipient** > Pull the relevant data from CertSeal, 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 CertSeal working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the CertSeal API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected CertSeal 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 CertSeal. | 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 CertSeal actions to the runtime in a format your agent can reliably use. | 21 tools for CertSeal are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes CertSeal 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 CertSeal in the browser, and the 21 tools above work from chat. There is no SDK and no config file, and the CertSeal 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 CertSeal 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 CertSeal 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 CertSeal tools CertSeal 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 CertSeal 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. ### CertSeal 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 CertSeal 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 CertSeal integration? Yes. ClawLink is the fastest way to connect Hermes to CertSeal: link your CertSeal account once in the browser and Hermes Agent can call the CertSeal API through 21 ready-made tools — no custom code or token handling. ### How do I connect CertSeal 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 CertSeal in the dashboard and Hermes can use it from the next message — no config files, and the CertSeal key you paste is stored server-side instead of in your environment. ### How long does it take to connect CertSeal to Hermes Agent? About two minutes. Sign in, click Connect next to CertSeal in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring CertSeal 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 CertSeal working from chat. ### Hermes paired but still can't use CertSeal 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 - [Hermes GitHub integration](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.