# How to connect Check Cherry to Hermes Agent (paste one key, 25 tools)

> Connect Check Cherry to Hermes with ClawLink: paste your Check Cherry key once and 25 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/hermes/check-cherry

Most guides for giving Hermes Agent Check Cherry 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 Check Cherry setup: pair once in the browser and your always-on Hermes agent can act on Check Cherry 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 Check Cherry.

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect Check Cherry** — 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 check-cherry  # connect Check Cherry (browser OAuth)
npx -y @useclawlink/cli actions check-cherry  # list available actions
npx -y @useclawlink/cli run check-cherry <action> --input '<json>'  # 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 Check Cherry in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Check Cherry API key once.

Verify the connection by asking Hermes:

> Use Check Cherry to check event availability 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 Check Cherry is connected in the dashboard, that agent calls the same 25 Check Cherry 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).

## Check Cherry MCP for Hermes

Looking for a Check Cherry MCP server for Hermes Agent? ClawLink connects Check Cherry to Hermes Agent and exposes 25 Check Cherry 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 Check Cherry integration](https://claw-link.dev/openclaw/check-cherry) works the same way.

## What the Hermes Agent Check Cherry integration can do

25 Check Cherry tools are ready for Hermes Agent once the account is connected. The 23 below are the ones people reach for most; your agent can call all 25.

### 23 of 25 Check Cherry tools for Hermes

| Tool | What it does |
|---|---|
| **Check event availability** `check_cherry_check_event_availability` | Check whether a package can be booked on one date or across a date range |
| **Get appointment** `check_cherry_get_appointment` | Return full guest, scheduling, and assignment details for one appointment |
| **Get event** `check_cherry_get_event` | Return full details for one proposal or confirmed booking by event ID |
| **Get lead** `check_cherry_get_lead` | Return full details for one lead by ID |
| **Get questionnaire** `check_cherry_get_questionnaire` | Return one questionnaire with its questions, current answers, and completion state |
| **Get report** `check_cherry_get_report` | Return one time-bucketed Check Cherry business report for bookings, leads, payments, proposals |
| **List appointment slots** `check_cherry_list_appointment_slots` | Return available appointment times for one staff member and appointment calendar on a selected |
| **List appointments** `check_cherry_list_appointments` | Search staff appointments by date, assignee, brand, cancellation state, time direction, or |
| **List event bookings** `check_cherry_list_event_bookings` | List package bookings attached to events within an optional event-date range, returning one |
| **List events** `check_cherry_list_events` | Search proposals and confirmed bookings with date, status, client, staff, payment, and workflow |
| **List expense categories** `check_cherry_list_expense_categories` | Return the expense categories available for classifying business expenses |
| **List expenses** `check_cherry_list_expenses` | Search business expenses by event, category, payment date, text, and sort order, returning one |
| **List leads** `check_cherry_list_leads` | Search leads by exact email or contact and event text, returning one page of CRM records |
| **List offerings** `check_cherry_list_offerings` | List one Check Cherry catalog resource: services, package groups, packages, or add-ons |
| **List payments** `check_cherry_list_payments` | List event payment records, including received payments and refunds, by event or payment date |
| **List questionnaire templates** `check_cherry_list_questionnaire_templates` | Return questionnaire templates that can be attached to an event booking |
| **List questionnaires** `check_cherry_list_questionnaires` | List questionnaires attached to one event booking |
| **Attach questionnaire** `check_cherry_attach_questionnaire` | Copy a questionnaire template onto a proposal or confirmed booking |
| **Create appointment** `check_cherry_create_appointment` | Create a staff appointment for a guest at a specific date, time, and duration; this changes the |
| **Create expense** `check_cherry_create_expense` | Record a business expense with its payment date, amount, reference, payee, and optional event |
| **Update expense** `check_cherry_update_expense` | Change selected fields on an existing business expense |
| **Remove questionnaire** `check_cherry_remove_questionnaire` | Detach one questionnaire from its event booking and delete its collected answers; the source |
| **Update questionnaire answers** `check_cherry_update_questionnaire_answers` | Update answers on a standard questionnaire |

## Example prompts

**Check Event Availability**

> Use Check Cherry to check event availability and walk me through the result in plain English.

**Get Appointment**

> Pull the relevant data from Check Cherry, summarize it in plain English, and point out anything that needs attention.

**Get Event**

> Pull the relevant data from Check Cherry, summarize it in plain English, and point out anything that needs attention.

**Get Lead**

> Pull the relevant data from Check Cherry, 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 Check Cherry working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Check Cherry API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Check Cherry 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 Check Cherry. | 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 Check Cherry actions to the runtime in a format your agent can reliably use. | 25 tools for Check Cherry are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Check Cherry 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 Check Cherry in the browser, and the 25 tools above work from chat. There is no SDK and no config file, and the Check Cherry 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 Check Cherry
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 Check Cherry 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 Check Cherry tools
Check Cherry 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 Check Cherry 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.

### Check Cherry 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 Check Cherry 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 Check Cherry integration?
Yes. ClawLink is the fastest way to connect Hermes to Check Cherry: link your Check Cherry account once in the browser and Hermes Agent can call the Check Cherry API through 25 ready-made tools — no custom code or token handling.

### How do I connect Check Cherry 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 Check Cherry in the dashboard and Hermes can use it from the next message — no config files, and the Check Cherry key you paste is stored server-side instead of in your environment.

### How long does it take to connect Check Cherry to Hermes Agent?
About two minutes. Sign in, click Connect next to Check Cherry in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

### Why use ClawLink instead of wiring Check Cherry 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 Check Cherry working from chat.

### Hermes paired but still can't use Check Cherry
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 HubSpot integration](https://claw-link.dev/hermes/hubspot) — Manage contacts, deals, and pipelines
- [CentralStationCRM](https://claw-link.dev/hermes/centralstationcrm) — CentralStationCRM is an easy-to-use CRM software focusing on collaboration and long-term customer relationships.
- [Hermes Salesforce integration](https://claw-link.dev/hermes/salesforce) — Manage CRM data and workflows