# How to connect Dub to OpenClaw (no API keys) > Connect Dub to OpenClaw with ClawLink in one click — hosted OAuth, no API keys, no manual setup. Run real actions straight from chat. Web version: https://claw-link.dev/openclaw/dub The usual route to Dub 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 Dub setup: install one ClawHub skill, connect Dub in the browser, and OpenClaw can call real Dub actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Dub MCP for OpenClaw Looking for a Dub MCP server for OpenClaw? ClawLink connects Dub to OpenClaw and exposes 0 Dub 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 Dub integration](https://claw-link.dev/hermes/dub) works the same way. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/dub ## Setup It takes three steps to connect OpenClaw to Dub. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Dub** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **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 dub # connect Dub (browser OAuth) npx -y @useclawlink/cli actions dub # list available actions npx -y @useclawlink/cli run dub --input '' # execute (add --confirm for writes) ``` ## What the OpenClaw Dub integration can do - **Marketing** — tools appear after Dub is connected. ## Example prompts No example prompts are available yet. ## 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 Dub working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Dub API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Dub 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 Dub. | 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 Dub actions to the runtime in a format your agent can reliably use. | 0 tools for Dub are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Dub 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 Dub in the browser, and the connected Dub account works from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Dub skill but can't call the tools The ClawHub skill teaches OpenClaw about Dub, but the calls run through the ClawLink plugin and your connected account. Make sure Dub 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 Dub 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 Dub tools Dub 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 Dub 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. ### Dub 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 Dub has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Dub integration? Yes. ClawLink is the fastest way to connect OpenClaw to Dub: link your Dub account once in the browser and OpenClaw can call the Dub API through ready-made tools — no custom code or token handling. ### How do I add Dub to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Dub skill from ClawHub, then you click Connect in the dashboard to authorize Dub. OpenClaw calls the tools from the next message — no config files or API keys. ### How long does it take to connect Dub to OpenClaw? About two minutes. Sign in, click Connect next to Dub in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Dub 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 Dub working from chat. ### OpenClaw installed the Dub skill but can't call the tools The ClawHub skill teaches OpenClaw about Dub, but the calls run through the ClawLink plugin and your connected account. Make sure Dub 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 - [Mailchimp](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences - [OpenClaw ActiveCampaign integration](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [OpenClaw Kit integration](https://claw-link.dev/openclaw/kit) — Email marketing and audience growth for creators