# How to connect Payhip to OpenClaw (paste one key, 9 tools) > Connect Payhip to OpenClaw with ClawLink: paste your Payhip key once and 9 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/payhip The usual route to Payhip 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 Payhip setup: install one ClawHub skill, connect Payhip in the browser, and OpenClaw can call real Payhip 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 Payhip. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Payhip** — 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 payhip # connect Payhip (browser OAuth) npx -y @useclawlink/cli actions payhip # list available actions npx -y @useclawlink/cli run payhip --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 Payhip in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Payhip API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Payhip, 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 Payhip is connected in the dashboard, that agent calls the same 9 Payhip 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). ## Payhip MCP for OpenClaw Looking for a Payhip MCP server for OpenClaw? ClawLink connects Payhip to OpenClaw and exposes 9 Payhip 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 Payhip integration](https://claw-link.dev/hermes/payhip) works the same way. ## What the OpenClaw Payhip integration can do 9 Payhip tools are ready for OpenClaw once the account is connected. The 8 below are the ones people reach for most; your agent can call all 9. ### 8 of 9 Payhip tools for OpenClaw | Tool | What it does | |---|---| | **Get coupon** `payhip_get_coupon` | Retrieve a coupon with the given ID | | **Verify coupon** `payhip_verify_coupon` | Verify a Payhip coupon code | | **Webhook event paid** `payhip_webhook_event_paid` | Process Payhip's paid webhook event | | **Webhook event refunded** `payhip_webhook_event_refunded` | Process Payhip's refunded webhook event | | **Webhook event subscription created** `payhip_webhook_event_subscription_created` | Process Payhip's subscription.created webhook event | | **Webhook event subscription deleted** `payhip_webhook_event_subscription_deleted` | Process Payhip's 'subscription.deleted' webhook event | | **Create coupon** `payhip_create_coupon` | Create a coupon for discounts in Payhip | | **Update coupon** `payhip_update_coupon` | Edit an existing coupon in Payhip | ## Example prompts **Get Coupon** > Pull the relevant data from Payhip, summarize it in plain English, and point out anything that needs attention. **Verify Coupon** > Use Payhip to verify coupon and walk me through the result in plain English. **Webhook Event Paid** > Use Payhip to webhook event paid and walk me through the result in plain English. **Webhook Event Refunded** > Use Payhip to webhook event refunded and walk me through the result in plain English. ## 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 Payhip working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Payhip API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Payhip 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 Payhip. | 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 Payhip actions to the runtime in a format your agent can reliably use. | 9 tools for Payhip are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Payhip 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 Payhip in the browser, and the 9 tools above work from chat. There is no SDK and no config file, and the Payhip 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 Payhip skill but can't call the tools The ClawHub skill teaches OpenClaw about Payhip, but the calls run through the ClawLink plugin and your connected account. Make sure Payhip 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 Payhip 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 Payhip tools Payhip 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 Payhip 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. ### Payhip 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 Payhip has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Payhip integration? Yes. ClawLink is the fastest way to connect OpenClaw to Payhip: link your Payhip account once in the browser and OpenClaw can call the Payhip API through 9 ready-made tools — no custom code or token handling. ### How do I add Payhip to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Payhip skill from ClawHub, then you click Connect in the dashboard to authorize Payhip. OpenClaw calls the tools from the next message — no config files, and the Payhip key you paste is stored server-side instead of in your environment. ### How long does it take to connect Payhip to OpenClaw? About two minutes. Sign in, click Connect next to Payhip in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Payhip 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 Payhip working from chat. ### OpenClaw installed the Payhip skill but can't call the tools The ClawHub skill teaches OpenClaw about Payhip, but the calls run through the ClawLink plugin and your connected account. Make sure Payhip 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 - [Cloudcart tools](https://claw-link.dev/openclaw/cloudcart) — CloudCart is an e-commerce platform that enables businesses to create and manage online stores efficiently. - [Wix](https://claw-link.dev/openclaw/wix) — Manage sites, products, orders, and bookings - [Connect Baselinker](https://claw-link.dev/openclaw/baselinker) — BaseLinker is a comprehensive e-commerce management platform that integrates with various marketplaces, online stores, carriers, and accounting systems to streamline order processing, inventory management, and sales automation.