# How to connect redirect.pizza to OpenClaw (paste one key, 14 tools) > Connect redirect.pizza to OpenClaw with ClawLink: paste your redirect.pizza 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/redirect-pizza The usual route to redirect.pizza 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 redirect.pizza setup: install one ClawHub skill, connect redirect.pizza in the browser, and OpenClaw can call real redirect.pizza 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 redirect.pizza. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect redirect.pizza** — 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 redirect-pizza # connect redirect.pizza (browser OAuth) npx -y @useclawlink/cli actions redirect-pizza # list available actions npx -y @useclawlink/cli run redirect-pizza --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 redirect.pizza in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your redirect.pizza API key once. Verify the connection by asking OpenClaw: > Use redirect.pizza to generate qr 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 redirect.pizza is connected in the dashboard, that agent calls the same 14 redirect.pizza 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). ## redirect.pizza MCP for OpenClaw Looking for a redirect.pizza MCP server for OpenClaw? ClawLink connects redirect.pizza to OpenClaw and exposes 14 redirect.pizza 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 redirect.pizza integration](https://claw-link.dev/hermes/redirect-pizza) works the same way. ## What the OpenClaw redirect.pizza integration can do 14 redirect.pizza tools are ready for OpenClaw once the account is connected. The 13 below are the ones people reach for most; your agent can call all 14. ### 13 of 14 redirect.pizza tools for OpenClaw | Tool | What it does | |---|---| | **Generate qr code** `redirect_pizza_generate_qr_code` | Generate a QR code for an HTTP or HTTPS URL as JSON-embedded PNG data or a downloadable PNG | | **Get domain** `redirect_pizza_get_domain` | Retrieve one domain's required DNS records, verification status, security settings, and SSL | | **Get redirect** `redirect_pizza_get_redirect` | Retrieve one redirect and its sources, destination, domains, options, and current pause state | | **Get team** `redirect_pizza_get_team` | Return the connected token's team identity and hostname, hit, and user quota usage | | **List domains** `redirect_pizza_list_domains` | List domains created by redirects, including DNS requirements, verification, automatic-DNS | | **List redirects** `redirect_pizza_list_redirects` | List redirects visible to the connected API token, including source, destination, state, and | | **Test redirect URL** `redirect_pizza_test_redirect_url` | Test one HTTP redirect hop for a public URL and return status, redirect details, timing | | **Check domain dns** `redirect_pizza_check_domain_dns` | Ask redirect.pizza to re-check DNS propagation for a domain and return its refreshed DNS and | | **Create redirect** `redirect_pizza_create_redirect` | Create a new redirect from one or more source hostnames or URLs to a fixed destination URL | | **Set redirect paused** `redirect_pizza_set_redirect_paused` | Pause or resume all source URLs belonging to one redirect | | **Set redirect source paused** `redirect_pizza_set_redirect_source_paused` | Pause or resume one source URL within a redirect without changing its other sources | | **Update redirect** `redirect_pizza_update_redirect` | Replace a redirect's configurable sources, fixed destination, redirect type, and options | | **Upsert redirect** `redirect_pizza_upsert_redirect` | Create a redirect or update the uniquely matching redirect while retaining that redirect's | ## Example prompts **Generate Qr Code** > Use redirect.pizza to generate qr code and walk me through the result in plain English. **Get Domain** > Pull the relevant data from redirect.pizza, summarize it in plain English, and point out anything that needs attention. **Get Redirect** > Pull the relevant data from redirect.pizza, summarize it in plain English, and point out anything that needs attention. **Get Team** > Pull the relevant data from redirect.pizza, 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 redirect.pizza working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the redirect.pizza API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected redirect.pizza 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 redirect.pizza. | 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 redirect.pizza actions to the runtime in a format your agent can reliably use. | 14 tools for redirect.pizza are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes redirect.pizza 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 redirect.pizza in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the redirect.pizza 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 redirect.pizza skill but can't call the tools The ClawHub skill teaches OpenClaw about redirect.pizza, but the calls run through the ClawLink plugin and your connected account. Make sure redirect.pizza 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 redirect.pizza 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 redirect.pizza tools redirect.pizza 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 redirect.pizza 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. ### redirect.pizza 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 redirect.pizza has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw redirect.pizza integration? Yes. ClawLink is the fastest way to connect OpenClaw to redirect.pizza: link your redirect.pizza account once in the browser and OpenClaw can call the redirect.pizza API through 14 ready-made tools — no custom code or token handling. ### How do I add redirect.pizza to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink redirect.pizza skill from ClawHub, then you click Connect in the dashboard to authorize redirect.pizza. OpenClaw calls the tools from the next message — no config files, and the redirect.pizza key you paste is stored server-side instead of in your environment. ### How long does it take to connect redirect.pizza to OpenClaw? About two minutes. Sign in, click Connect next to redirect.pizza in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring redirect.pizza 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 redirect.pizza working from chat. ### OpenClaw installed the redirect.pizza skill but can't call the tools The ClawHub skill teaches OpenClaw about redirect.pizza, but the calls run through the ClawLink plugin and your connected account. Make sure redirect.pizza 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 - [Connect 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