How to connect Wachete to OpenClaw
Connect Wachete to OpenClaw with ClawLink: paste your Wachete key once and 11 tools work from chat. No MCP server to run, nothing stored on your machine.
WacheteAPI KEYMCPWachete is a web monitoring service that allows users to track changes on web pages and receive notifications based on specified criteria.. Once connected, OpenClaw can read and act on Wachete from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Wachete 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 Wachete setup: install one ClawHub skill, connect Wachete in the browser, and OpenClaw can call real Wachete 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 Wachete.
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 Wachete
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Wachete?"
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 Wachete in the ClawLink dashboard — paste your Wachete API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Wachete, 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Wachete is connected in the dashboard, that agent calls the same 11 Wachete tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Wachete MCP for OpenClaw
Looking for a Wachete MCP server for OpenClaw? ClawLink connects Wachete to OpenClaw and exposes 11 Wachete tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Wachete integration works the same way.
What the OpenClaw Wachete integration can do
11 Wachete tools are ready for OpenClaw once the account is connected. The 9 below are the ones people reach for most; your agent can call all 11.
9 of 11 Wachete tools for OpenClaw
| Tool | What it does |
|---|---|
Get crawler pages wachete_get_crawler_pages | Retrieves all pages monitored by a crawler watcher (portal monitor) |
Get data history wachete_get_data_history | Retrieve history for a wachet (monitor) |
Get folder content wachete_get_folder_content | Retrieves the contents of a Wachete folder, including subfolders and watcher tasks |
Get watcher wachete_get_watcher | Retrieve complete watcher (monitor) definition by ID |
List notifications wachete_list_notifications | Retrieves notifications from Wachete watchers |
List watchers wachete_list_watchers | List all monitoring watchers (tasks) configured in your Wachete account |
Create update folder wachete_create_update_folder | Create a new folder or update an existing folder in Wachete |
Create watcher wachete_create_watcher | Create or update a Wachete watcher to monitor web page changes |
Move items to folder wachete_move_items_to_folder | Move tasks (watchers) and folders to a specified destination folder |
Try it: find the Wachete tool you need
Browse the 9 Wachete tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Wachete, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Wachete, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Wachete, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Wachete, 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 Wachete working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Wachete API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Wachete 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 Wachete. | 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 Wachete actions to the runtime in a format your agent can reliably use. | 11 tools for Wachete are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Wachete 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 Wachete in the browser, and the 11 tools above work from chat. There is no SDK and no config file, and the Wachete 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 Wachete skill but can't call the tools
The ClawHub skill teaches OpenClaw about Wachete, but the calls run through the ClawLink plugin and your connected account. Make sure Wachete 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 Wachete 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 Wachete tools
Wachete 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 Wachete 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.
Wachete 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 Wachete 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 Wachete integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Wachete: link your Wachete account once in the browser and OpenClaw can call the Wachete API through 11 ready-made tools — no custom code or token handling.
How do I add Wachete to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Wachete skill from ClawHub, then you click Connect in the dashboard to authorize Wachete. OpenClaw calls the tools from the next message — no config files, and the Wachete key you paste is stored server-side instead of in your environment.
How long does it take to connect Wachete to OpenClaw?
About two minutes. Sign in, click Connect next to Wachete in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Wachete 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 Wachete working from chat.
OpenClaw installed the Wachete skill but can't call the tools
The ClawHub skill teaches OpenClaw about Wachete, but the calls run through the ClawLink plugin and your connected account. Make sure Wachete 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
Manage repositories, issues, pull requests, and workflows
PagerDuty
Manage incidents, on-call schedules, and services
OpenClaw SafetyCulture integration
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.