How to connect Check Cherry to OpenClaw
Connect Check Cherry to OpenClaw with ClawLink: paste your Check Cherry key once and 25 tools work from chat. No MCP server to run, nothing stored on your machine.
Check CherryAPI KEYMCPCheck Cherry is a business management platform for photography and event service companies, with tools for leads, bookings, appointments, offerings, payments, and workflows.. Once connected, OpenClaw can read and act on Check Cherry from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Check Cherry 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 Check Cherry setup: install one ClawHub skill, connect Check Cherry in the browser, and OpenClaw can call real Check Cherry 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 Check Cherry.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Check Cherry
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Check Cherry?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 Check Cherry in the ClawLink dashboard — paste your Check Cherry API key once.
Verify the connection by asking OpenClaw:
Use Check Cherry to check event availability and walk me through the result in plain English.
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:
npx -y @useclawlink/cli loginlogin 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.
Check Cherry MCP for OpenClaw
Looking for a Check Cherry MCP server for OpenClaw? ClawLink connects Check Cherry to OpenClaw and exposes 25 Check Cherry tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Check Cherry integration works the same way.
What the OpenClaw Check Cherry integration can do
25 Check Cherry tools are ready for OpenClaw 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 OpenClaw
| 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 |
Try it: find the Check Cherry tool you need
Browse the 23 Check Cherry tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Check Cherry to check event availability and walk me through the result in plain English.
Pull the relevant data from Check Cherry, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Check Cherry, summarize it in plain English, and point out anything that needs attention.
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 OpenClaw. 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 OpenClaw 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 comparison.
Troubleshooting
OpenClaw installed the Check Cherry skill but can't call the tools
The ClawHub skill teaches OpenClaw about Check Cherry, but the calls run through the ClawLink plugin and your connected account. Make sure Check Cherry 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 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.
FAQ
Is there a OpenClaw Check Cherry integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Check Cherry: link your Check Cherry account once in the browser and OpenClaw can call the Check Cherry API through 25 ready-made tools — no custom code or token handling.
How do I add Check Cherry to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Check Cherry skill from ClawHub, then you click Connect in the dashboard to authorize Check Cherry. OpenClaw calls the tools 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 OpenClaw?
About two minutes. Sign in, click Connect next to Check Cherry in the dashboard, authenticate, and OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Check Cherry working from chat.
OpenClaw installed the Check Cherry skill but can't call the tools
The ClawHub skill teaches OpenClaw about Check Cherry, but the calls run through the ClawLink plugin and your connected account. Make sure Check Cherry 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.
