# How to connect CalendarHero to Hermes Agent (paste one key, 38 tools) > Connect CalendarHero to Hermes with ClawLink: paste your CalendarHero key once and 38 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/calendarhero Most guides for giving Hermes Agent CalendarHero 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 CalendarHero setup: pair once in the browser and your always-on Hermes agent can act on CalendarHero 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 CalendarHero. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect CalendarHero** — 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 calendarhero # connect CalendarHero (browser OAuth) npx -y @useclawlink/cli actions calendarhero # list available actions npx -y @useclawlink/cli run calendarhero --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 CalendarHero in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your CalendarHero API key once. Verify the connection by asking Hermes: > Pull the relevant data from CalendarHero, 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 CalendarHero is connected in the dashboard, that agent calls the same 38 CalendarHero 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). ## CalendarHero MCP for Hermes Looking for a CalendarHero MCP server for Hermes Agent? ClawLink connects CalendarHero to Hermes Agent and exposes 38 CalendarHero 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 CalendarHero integration](https://claw-link.dev/openclaw/calendarhero) works the same way. ## What the Hermes Agent CalendarHero integration can do 38 CalendarHero 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 38. ### 30 of 38 CalendarHero tools for Hermes | Tool | What it does | |---|---| | **Fetch contact** `calendarhero_fetch_contact` | Fetch Contact | | **Fetch meeting details** `calendarhero_fetch_meeting_details` | Fetch details for meetings within a specified timeframe | | **Fetch user profile** `calendarhero_fetch_user_profile` | Fetch the profile details of the authenticated user | | **Get assistant message** `calendarhero_get_assistant_message` | Retrieve a reply message from the CalendarHero assistant | | **Get contact count** `calendarhero_get_contact_count` | Get the total count of contacts in CalendarHero | | **Get meeting categories** `calendarhero_get_meeting_categories` | Retrieves the user's meeting categories' stats for a specified time period | | **Get meeting tasks** `calendarhero_get_meeting_tasks` | Retrieves the user's meeting requests/tasks from CalendarHero | | **Get search result** `calendarhero_get_search_result` | Get a search result by ID | | **Get user directory** `calendarhero_get_user_directory` | Retrieve a user's directory by its unique identifier | | **Get user organization** `calendarhero_get_user_organization` | Retrieve the authenticated user's organization details | | **Get user savings** `calendarhero_get_user_savings` | Retrieve the authenticated user's savings information from CalendarHero | | **Get webhook** `calendarhero_get_webhook` | Get webhook configuration for a specific event type | | **Get webhook sample** `calendarhero_get_webhook_sample` | Retrieve a sample webhook payload for a specific event type | | **List meeting templates** `calendarhero_list_meeting_templates` | Retrieves all meeting templates (reusable meeting configurations) for the authenticated user | | **List meeting types** `calendarhero_list_meeting_types` | Retrieves all meeting types configured for the authenticated CalendarHero user | | **List user calendars** `calendarhero_list_user_calendars` | List all calendar integrations connected to a user's CalendarHero account | | **List user directories** `calendarhero_list_user_directories` | Retrieve all directories configured for a user | | **Search contact** `calendarhero_search_contact` | Search for existing contacts | | **Search integrations** `calendarhero_search_integrations` | Search across all user integrations for a query term | | **Add calendar connection** `calendarhero_add_calendar_connection` | Add a new calendar directory/connection to the user's CalendarHero account | | **Create contact** `calendarhero_create_contact` | Creates a new contact in CalendarHero with the provided contact information | | **Create meeting request v2** `calendarhero_create_meeting_request_v2` | Create a new meeting request in CalendarHero | | **Create webhook** `calendarhero_create_webhook` | Creates or updates a webhook for a specific event type in CalendarHero | | **Send assistant message** `calendarhero_send_assistant_message` | Send a user's message into the CalendarHero assistant | | **Send reminder** `calendarhero_send_reminder` | Sends an email reminder to all contacts/participants about a scheduled meeting request | | **Update contact** `calendarhero_update_contact` | Updates an existing contact in CalendarHero with new information | | **Update meeting types** `calendarhero_update_meeting_types` | Update meeting type configurations for the authenticated CalendarHero user | | **Update restricted apps** `calendarhero_update_restricted_apps` | Update the authenticated user's restricted apps settings | | **Update user** `calendarhero_update_user` | Update the authenticated user's profile information | | **Update user address** `calendarhero_update_user_address` | Update the authenticated user's address settings by providing latitude and longitude coordinates | ## Example prompts **Fetch Contact** > Pull the relevant data from CalendarHero, summarize it in plain English, and point out anything that needs attention. **Fetch Meeting Details** > Pull the relevant data from CalendarHero, summarize it in plain English, and point out anything that needs attention. **Fetch User Profile** > Pull the relevant data from CalendarHero, summarize it in plain English, and point out anything that needs attention. **Get Assistant Message** > Pull the relevant data from CalendarHero, 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 CalendarHero working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the CalendarHero API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected CalendarHero 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 CalendarHero. | 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 CalendarHero actions to the runtime in a format your agent can reliably use. | 38 tools for CalendarHero are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes CalendarHero 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 CalendarHero in the browser, and the 38 tools above work from chat. There is no SDK and no config file, and the CalendarHero 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 CalendarHero 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 CalendarHero 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 CalendarHero tools CalendarHero 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 CalendarHero 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. ### CalendarHero 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 CalendarHero 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 CalendarHero integration? Yes. ClawLink is the fastest way to connect Hermes to CalendarHero: link your CalendarHero account once in the browser and Hermes Agent can call the CalendarHero API through 38 ready-made tools — no custom code or token handling. ### How do I connect CalendarHero 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 CalendarHero in the dashboard and Hermes can use it from the next message — no config files, and the CalendarHero key you paste is stored server-side instead of in your environment. ### How long does it take to connect CalendarHero to Hermes Agent? About two minutes. Sign in, click Connect next to CalendarHero in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring CalendarHero 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 CalendarHero working from chat. ### Hermes paired but still can't use CalendarHero 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 Cal.com integration](https://claw-link.dev/hermes/cal) — Schedule and manage bookings through Cal.com - [Hermes Bookingmood integration](https://claw-link.dev/hermes/bookingmood) — Bookingmood provides flexible, commission-free booking software for rental businesses of all sizes, enabling seamless integration with your website. - [Eventbrite](https://claw-link.dev/hermes/eventbrite) — Create and manage events, tickets, and attendees