# How to connect Linkly to OpenClaw (paste one key, 17 tools) > Connect Linkly to OpenClaw with ClawLink: paste your Linkly key once and 17 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/linkly The usual route to Linkly 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 Linkly setup: install one ClawHub skill, connect Linkly in the browser, and OpenClaw can call real Linkly 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 Linkly. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Linkly** — 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 linkly # connect Linkly (browser OAuth) npx -y @useclawlink/cli actions linkly # list available actions npx -y @useclawlink/cli run linkly --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 Linkly in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Linkly API key once. Verify the connection by asking OpenClaw: > Use Linkly to export links 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 Linkly is connected in the dashboard, that agent calls the same 17 Linkly 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). ## Linkly MCP for OpenClaw Looking for a Linkly MCP server for OpenClaw? ClawLink connects Linkly to OpenClaw and exposes 17 Linkly 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 Linkly integration](https://claw-link.dev/hermes/linkly) works the same way. ## What the OpenClaw Linkly integration can do 17 Linkly tools are ready for OpenClaw once the account is connected. The 15 below are the ones people reach for most; your agent can call all 17. ### 15 of 17 Linkly tools for OpenClaw | Tool | What it does | |---|---| | **Export links** `linkly_export_links` | Export all links in a workspace as JSON or CSV | | **Get click counters** `linkly_get_click_counters` | Retrieve click analytics grouped by a specific dimension (counter) | | **Get clicks** `linkly_get_clicks` | Retrieve click analytics for a workspace | | **Get link** `linkly_get_link` | Retrieve detailed information about a specific link by its ID | | **Get link by ID** `linkly_get_link_by_id` | Retrieve details for a specific link by ID | | **List domains** `linkly_list_domains` | Retrieve all custom domains configured for a workspace | | **List link webhooks** `linkly_list_link_webhooks` | Retrieve all webhook subscriptions for a specific link | | **List links** `linkly_list_links` | Get a paginated list of all links in a workspace | | **List workspace webhooks** `linkly_list_workspace_webhooks` | List all webhook subscriptions for a specific workspace | | **List workspaces** `linkly_list_workspaces` | Retrieve all workspaces the authenticated user has access to | | **Create or update link** `linkly_create_or_update_link` | Create a new shortened link or update an existing one in Linkly | | **Subscribe webhook to link** `linkly_subscribe_webhook_to_link` | Subscribe a webhook URL to receive notifications when a specific link is clicked | | **Subscribe webhook to workspace** `linkly_subscribe_webhook_to_workspace` | Subscribe a webhook URL to receive click notifications from a Linkly workspace | | **Unsubscribe webhook from link** `linkly_unsubscribe_webhook_from_link` | Remove a webhook subscription from a link | | **Unsubscribe webhook from workspace** `linkly_unsubscribe_webhook_from_workspace` | Remove a webhook subscription from a workspace | ## Example prompts **Export Links** > Use Linkly to export links and walk me through the result in plain English. **Get Click Counters** > Pull the relevant data from Linkly, summarize it in plain English, and point out anything that needs attention. **Get Clicks** > Pull the relevant data from Linkly, summarize it in plain English, and point out anything that needs attention. **Get Link** > Pull the relevant data from Linkly, 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 Linkly working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Linkly API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Linkly 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 Linkly. | 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 Linkly actions to the runtime in a format your agent can reliably use. | 17 tools for Linkly are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Linkly 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 Linkly in the browser, and the 17 tools above work from chat. There is no SDK and no config file, and the Linkly 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 Linkly skill but can't call the tools The ClawHub skill teaches OpenClaw about Linkly, but the calls run through the ClawLink plugin and your connected account. Make sure Linkly 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 Linkly 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 Linkly tools Linkly 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 Linkly 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. ### Linkly 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 Linkly has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Linkly integration? Yes. ClawLink is the fastest way to connect OpenClaw to Linkly: link your Linkly account once in the browser and OpenClaw can call the Linkly API through 17 ready-made tools — no custom code or token handling. ### How do I add Linkly to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Linkly skill from ClawHub, then you click Connect in the dashboard to authorize Linkly. OpenClaw calls the tools from the next message — no config files, and the Linkly key you paste is stored server-side instead of in your environment. ### How long does it take to connect Linkly to OpenClaw? About two minutes. Sign in, click Connect next to Linkly in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Linkly 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 Linkly working from chat. ### OpenClaw installed the Linkly skill but can't call the tools The ClawHub skill teaches OpenClaw about Linkly, but the calls run through the ClawLink plugin and your connected account. Make sure Linkly 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 - [OpenClaw Benchmark Email integration](https://claw-link.dev/openclaw/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [Mailchimp tools](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences