# How to connect Hookdeck to Hermes Agent (paste one key, 105 tools) > Connect Hookdeck to Hermes with ClawLink: paste your Hookdeck key once and 105 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/hookdeck Most guides for giving Hermes Agent Hookdeck 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 Hookdeck setup: pair once in the browser and your always-on Hermes agent can act on Hookdeck 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 Hookdeck. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Hookdeck** — 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 hookdeck # connect Hookdeck (browser OAuth) npx -y @useclawlink/cli actions hookdeck # list available actions npx -y @useclawlink/cli run hookdeck --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 Hookdeck in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Hookdeck API key once. Verify the connection by asking Hermes: > Use Hookdeck to add custom domain 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 Hookdeck is connected in the dashboard, that agent calls the same 105 Hookdeck 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). ## Hookdeck MCP for Hermes Looking for a Hookdeck MCP server for Hermes Agent? ClawLink connects Hookdeck to Hermes Agent and exposes 105 Hookdeck 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 Hookdeck integration](https://claw-link.dev/openclaw/hookdeck) works the same way. ## What the Hermes Agent Hookdeck integration can do 105 Hookdeck 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 105. ### 30 of 105 Hookdeck tools for Hermes | Tool | What it does | |---|---| | **Add custom domain** `hookdeck_add_custom_domain` | Add a custom domain to the Hookdeck project | | **Bulk cancel events** `hookdeck_bulk_cancel_events` | Create a bulk cancellation job for events | | **Bulk retry events** `hookdeck_bulk_retry_events` | Initiate a bulk retry for multiple events matching the specified filters | | **Cancel event** `hookdeck_cancel_event` | Cancel all future delivery attempts for a Hookdeck event | | **Count connections** `hookdeck_count_connections` | Count Hookdeck connections with optional filters | | **Count destinations** `hookdeck_count_destinations` | Count Hookdeck destinations with optional filters | | **Count sources** `hookdeck_count_sources` | Count Hookdeck sources with optional filters | | **Generate event bulk cancel plan** `hookdeck_generate_event_bulk_cancel_plan` | Generate a preview plan for bulk event cancellation | | **Generate event bulk retry plan** `hookdeck_generate_event_bulk_retry_plan` | Generate an events bulk retry plan | | **Generate ignored event bulk retry plan** `hookdeck_generate_ignored_event_bulk_retry_plan` | Generate an ignored events bulk retry plan to estimate the scope before execution | | **Generate request bulk retry plan** `hookdeck_generate_request_bulk_retry_plan` | Generate a requests bulk retry plan | | **Get attempt2** `hookdeck_get_attempt2` | Retrieve a specific Hookdeck delivery attempt by ID | | **Get attempts** `hookdeck_get_attempts` | Lists delivery attempts for your Hookdeck account | | **Get attempts metrics** `hookdeck_get_attempts_metrics` | Query aggregated attempt metrics with time-based grouping and filtering | | **Get bookmark** `hookdeck_get_bookmark` | Retrieve a single bookmark by its ID | | **Get bookmark raw body** `hookdeck_get_bookmark_raw_body` | Retrieve the raw body data of a bookmarked request | | **Get connection** `hookdeck_get_connection` | Retrieves details of a specific Hookdeck connection by its ID | | **Get connections** `hookdeck_get_connections` | List Hookdeck connections | | **Get destination** `hookdeck_get_destination` | Retrieve details of a specific Hookdeck destination by ID | | **Get destinations** `hookdeck_get_destinations` | List Hookdeck destinations | | **Get event** `hookdeck_get_event` | Retrieve a specific Hookdeck event by ID | | **Get event bulk cancel** `hookdeck_get_event_bulk_cancel` | Retrieve the status of a bulk event cancellation operation | | **Get event bulk cancels** `hookdeck_get_event_bulk_cancels` | List event bulk cancel operations for your Hookdeck account | | **Get event bulk retries** `hookdeck_get_event_bulk_retries` | Retrieve bulk retry operations for Hookdeck events | | **Get event bulk retry** `hookdeck_get_event_bulk_retry` | Retrieve the status of a bulk event retry operation | | **Get event raw body** `hookdeck_get_event_raw_body` | Retrieve the raw body data of an event | | **Get events** `hookdeck_get_events` | List events for your Hookdeck account | | **Get events by issue metrics** `hookdeck_get_events_by_issue_metrics` | Query event metrics grouped by individual issue IDs | | **Get events metrics** `hookdeck_get_events_metrics` | Query aggregated event metrics with time-based grouping and filtering | | **Get events pending timeseries metrics** `hookdeck_get_events_pending_timeseries_metrics` | Query aggregated events pending timeseries metrics with time-based grouping and filtering | ## Example prompts **Add Custom Domain** > Use Hookdeck to add custom domain and walk me through the result in plain English. **Bulk Cancel Events** > Use Hookdeck to bulk cancel events and walk me through the result in plain English. **Bulk Retry Events** > Use Hookdeck to bulk retry events and walk me through the result in plain English. **Cancel Event** > Use Hookdeck to cancel event and walk me through the result in plain English. ## 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 Hookdeck working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Hookdeck API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Hookdeck 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 Hookdeck. | 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 Hookdeck actions to the runtime in a format your agent can reliably use. | 105 tools for Hookdeck are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Hookdeck 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 Hookdeck in the browser, and the 105 tools above work from chat. There is no SDK and no config file, and the Hookdeck 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 Hookdeck 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 Hookdeck 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 Hookdeck tools Hookdeck 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 Hookdeck 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. ### Hookdeck 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 Hookdeck 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 Hookdeck integration? Yes. ClawLink is the fastest way to connect Hermes to Hookdeck: link your Hookdeck account once in the browser and Hermes Agent can call the Hookdeck API through 105 ready-made tools — no custom code or token handling. ### How do I connect Hookdeck 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 Hookdeck in the dashboard and Hermes can use it from the next message — no config files, and the Hookdeck key you paste is stored server-side instead of in your environment. ### How long does it take to connect Hookdeck to Hermes Agent? About two minutes. Sign in, click Connect next to Hookdeck in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Hookdeck 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 Hookdeck working from chat. ### Hermes paired but still can't use Hookdeck 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 - [Connect SafetyCulture](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.