# How to connect Payhere to OpenClaw (paste one key, 13 tools) > Connect Payhere to OpenClaw with ClawLink: paste your Payhere key once and 13 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/payhere The usual route to Payhere 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 Payhere setup: install one ClawHub skill, connect Payhere in the browser, and OpenClaw can call real Payhere 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 Payhere. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Payhere** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw 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 payhere # connect Payhere (browser OAuth) npx -y @useclawlink/cli actions payhere # list available actions npx -y @useclawlink/cli run payhere --input '' # execute (add --confirm for writes) ``` ### 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: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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 Payhere in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Payhere API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Payhere, 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Payhere is connected in the dashboard, that agent calls the same 13 Payhere 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). ## Payhere MCP for OpenClaw Looking for a Payhere MCP server for OpenClaw? ClawLink connects Payhere to OpenClaw and exposes 13 Payhere 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 Hermes instead? The [Hermes Payhere integration](https://claw-link.dev/hermes/payhere) works the same way. ## What the OpenClaw Payhere integration can do 13 Payhere tools are ready for OpenClaw once the account is connected. The 12 below are the ones people reach for most; your agent can call all 13. ### 12 of 13 Payhere tools for OpenClaw | Tool | What it does | |---|---| | **Get current company** `payhere_get_current_company` | Fetch company information for the currently authenticated user | | **Get current company stats** `payhere_get_current_company_stats` | Fetch payment statistics for the last 30 days with comparison data from the preceding 30-day | | **Get user** `payhere_get_user` | Fetch information on the currently authenticated user | | **List customers** `payhere_list_customers` | List all customers from Payhere, ordered chronologically with most recent first | | **List hooks** `payhere_list_hooks` | List all active REST hooks subscriptions for the authenticated company | | **List payments** `payhere_list_payments` | List all payments ordered chronologically, most recent first | | **List plans** `payhere_list_plans` | List all plans in your PayHere account | | **List subscriptions** `payhere_list_subscriptions` | List all subscriptions ordered chronologically by most recent payment first | | **Create hook** `payhere_create_hook` | Subscribe to a REST hook for receiving webhook events | | **Create plan** `payhere_create_plan` | Create a new payment plan in PayHere | | **Update current company** `payhere_update_current_company` | Update the company information for the currently authenticated user | | **Update plan** `payhere_update_plan` | Update an existing plan's configuration and settings | ## Example prompts **Get Current Company** > Pull the relevant data from Payhere, summarize it in plain English, and point out anything that needs attention. **Get Current Company Stats** > Pull the relevant data from Payhere, summarize it in plain English, and point out anything that needs attention. **Get User** > Pull the relevant data from Payhere, summarize it in plain English, and point out anything that needs attention. **List Customers** > List the relevant items in Payhere, group them by priority, and recommend what OpenClaw should do next. ## 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 Payhere working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Payhere API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Payhere 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 Payhere. | 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 Payhere actions to the runtime in a format your agent can reliably use. | 13 tools for Payhere are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Payhere 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 Payhere in the browser, and the 13 tools above work from chat. There is no SDK and no config file, and the Payhere 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. ### OpenClaw installed the Payhere skill but can't call the tools The ClawHub skill teaches OpenClaw about Payhere, but the calls run through the ClawLink plugin and your connected account. Make sure Payhere 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 Payhere 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 Payhere tools Payhere 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 Payhere 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. ### Payhere 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 Payhere has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Payhere integration? Yes. ClawLink is the fastest way to connect OpenClaw to Payhere: link your Payhere account once in the browser and OpenClaw can call the Payhere API through 13 ready-made tools — no custom code or token handling. ### How do I add Payhere to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Payhere skill from ClawHub, then you click Connect in the dashboard to authorize Payhere. OpenClaw calls the tools from the next message — no config files, and the Payhere key you paste is stored server-side instead of in your environment. ### How long does it take to connect Payhere to OpenClaw? About two minutes. Sign in, click Connect next to Payhere in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Payhere 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 Payhere working from chat. ### OpenClaw installed the Payhere skill but can't call the tools The ClawHub skill teaches OpenClaw about Payhere, but the calls run through the ClawLink plugin and your connected account. Make sure Payhere 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 - [Connect Stripe](https://claw-link.dev/openclaw/stripe) — Manage payments, customers, and invoices - [Zoho Books tools](https://claw-link.dev/openclaw/zoho-books) — Organize finances, invoices, bills, and accounting - [Ramp](https://claw-link.dev/openclaw/ramp) — Read cards, transactions, bills, and reimbursements, and file receipts