# How to connect Piggy to OpenClaw (paste one key, 14 tools) > Connect Piggy to OpenClaw with ClawLink: paste your Piggy key once and 14 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/piggy The usual route to Piggy 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 Piggy setup: install one ClawHub skill, connect Piggy in the browser, and OpenClaw can call real Piggy 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 Piggy. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Piggy** — 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 piggy # connect Piggy (browser OAuth) npx -y @useclawlink/cli actions piggy # list available actions npx -y @useclawlink/cli run piggy --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 Piggy in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Piggy API key once. Verify the connection by asking OpenClaw: > Use Piggy to find voucher by code 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Piggy is connected in the dashboard, that agent calls the same 14 Piggy 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). ## Piggy MCP for OpenClaw Looking for a Piggy MCP server for OpenClaw? ClawLink connects Piggy to OpenClaw and exposes 14 Piggy 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 Piggy integration](https://claw-link.dev/hermes/piggy) works the same way. ## What the OpenClaw Piggy integration can do 14 Piggy tools are ready for OpenClaw once the account is connected. ### All 14 Piggy tools for OpenClaw | Tool | What it does | |---|---| | **Find voucher by code** `piggy_find_voucher_by_code` | Find a voucher by its unique code | | **Get contact auth token** `piggy_get_contact_auth_token` | Get an auth token for a Contact | | **Get contacts credit balance** `piggy_get_contacts_credit_balance` | Get a Contact's credit balance | | **List forms** `piggy_list_forms` | List all forms in the Piggy account | | **List perks** `piggy_list_perks` | List all available perks in Piggy | | **Claim anonymous contact** `piggy_claim_anonymous_contact` | Claim an anonymous contact by associating it with a real email address | | **Create contact attribute** `piggy_create_contact_attribute` | Create a custom Contact Attribute | | **Create credit reception** `piggy_create_credit_reception` | Create a credit reception for a contact | | **Create vouchers batch** `piggy_create_vouchers_batch` | Create a batch of vouchers for a promotion | | **Find or create products** `piggy_find_or_create_products` | Find an existing product by external_identifier or create a new one if it doesn't exist | | **Send contact verification email** `piggy_send_contact_verification_email` | Send a verification email to a Piggy contact for identity verification | | **Update bookings** `piggy_update_bookings` | Update an existing booking in Piggy | | **Update contact identifiers** `piggy_update_contact_identifiers` | Update a contact identifier in Piggy | | **Merge contacts** `piggy_merge_contacts` | Merges a source contact into a destination contact in Piggy's CRM | ## Example prompts **Find Voucher By Code** > Use Piggy to find voucher by code and walk me through the result in plain English. **Get Contact Auth Token** > Pull the relevant data from Piggy, summarize it in plain English, and point out anything that needs attention. **Get Contacts Credit Balance** > Pull the relevant data from Piggy, summarize it in plain English, and point out anything that needs attention. **List Forms** > List the relevant items in Piggy, 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 Piggy working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Piggy API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Piggy 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 Piggy. | 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 Piggy actions to the runtime in a format your agent can reliably use. | 14 tools for Piggy are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Piggy 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 Piggy in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the Piggy 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 Piggy skill but can't call the tools The ClawHub skill teaches OpenClaw about Piggy, but the calls run through the ClawLink plugin and your connected account. Make sure Piggy 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 Piggy 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 Piggy tools Piggy 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 Piggy 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. ### Piggy 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 Piggy has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Piggy integration? Yes. ClawLink is the fastest way to connect OpenClaw to Piggy: link your Piggy account once in the browser and OpenClaw can call the Piggy API through 14 ready-made tools — no custom code or token handling. ### How do I add Piggy to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Piggy skill from ClawHub, then you click Connect in the dashboard to authorize Piggy. OpenClaw calls the tools from the next message — no config files, and the Piggy key you paste is stored server-side instead of in your environment. ### How long does it take to connect Piggy to OpenClaw? About two minutes. Sign in, click Connect next to Piggy in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Piggy 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 Piggy working from chat. ### OpenClaw installed the Piggy skill but can't call the tools The ClawHub skill teaches OpenClaw about Piggy, but the calls run through the ClawLink plugin and your connected account. Make sure Piggy 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 - [ActiveCampaign](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [Benchmark Email](https://claw-link.dev/openclaw/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [OpenClaw Mailchimp integration](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences