# How to connect CertSeal to OpenClaw (paste one key, 21 tools) > Connect CertSeal to OpenClaw 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/openclaw/cert-seal The usual route to CertSeal access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical CertSeal setup: install one ClawHub skill, connect CertSeal in the browser, and OpenClaw can call real CertSeal actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to CertSeal. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect CertSeal** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw 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 setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect CertSeal in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your CertSeal API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from CertSeal, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The OpenClaw 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 OpenClaw Looking for a CertSeal MCP server for OpenClaw? ClawLink connects CertSeal to OpenClaw 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 Hermes instead? The [Hermes CertSeal integration](https://claw-link.dev/hermes/cert-seal) works the same way. ## What the OpenClaw CertSeal integration can do 21 CertSeal tools are ready for OpenClaw 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 OpenClaw | 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 OpenClaw. 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 OpenClaw 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. ### OpenClaw installed the CertSeal skill but can't call the tools The ClawHub skill teaches OpenClaw about CertSeal, but the calls run through the ClawLink plugin and your connected account. Make sure CertSeal is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### 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 OpenClaw CertSeal integration? Yes. ClawLink is the fastest way to connect OpenClaw to CertSeal: link your CertSeal account once in the browser and OpenClaw can call the CertSeal API through 21 ready-made tools — no custom code or token handling. ### How do I add CertSeal to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink CertSeal skill from ClawHub, then you click Connect in the dashboard to authorize CertSeal. OpenClaw calls the tools 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 OpenClaw? About two minutes. Sign in, click Connect next to CertSeal in the dashboard, authenticate, and OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want CertSeal working from chat. ### OpenClaw installed the CertSeal skill but can't call the tools The ClawHub skill teaches OpenClaw about CertSeal, but the calls run through the ClawLink plugin and your connected account. Make sure CertSeal is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [GitHub tools](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [OpenClaw PagerDuty integration](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [Connect SafetyCulture](https://claw-link.dev/openclaw/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.