ClawLink

How to connect Botdog to OpenClaw

Connect Botdog to OpenClaw with ClawLink: paste your Botdog key once and 12 tools work from chat. No MCP server to run, nothing stored on your machine.

Get started for free
OpenClaw
OpenClaw
ClawLink
ClawLink
Botdog
Botdog
BotdogAPI KEYMCP

Botdog is a LinkedIn outreach platform for managing campaigns, leads, messaging, team analytics, and connected sending accounts.. Once connected, OpenClaw can read and act on Botdog from chat — pairing, token refresh, and tool wiring handled for you.

12 tools

The usual route to Botdog 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 Botdog setup: install one ClawHub skill, connect Botdog in the browser, and OpenClaw can call real Botdog 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 Botdog.

  1. 1

    Install the plugin

    Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:

    openclaw plugins install clawhub:clawlink-plugin
  2. 2

    Connect Botdog

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask OpenClaw: "What can you do with Botdog?"

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:

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 Botdog in the ClawLink dashboard — paste your Botdog API key once.

Verify the connection by asking OpenClaw:

Pull the relevant data from Botdog, 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:

npx -y @useclawlink/cli login

login opens the same browser approval and stores a credential locally. Once Botdog is connected in the dashboard, that agent calls the same 12 Botdog tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

Botdog MCP for OpenClaw

Looking for a Botdog MCP server for OpenClaw? ClawLink connects Botdog to OpenClaw and exposes 12 Botdog tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Botdog integration works the same way.

What the OpenClaw Botdog integration can do

12 Botdog tools are ready for OpenClaw once the account is connected.

All 12 Botdog tools for OpenClaw

ToolWhat it does
Get analytics botdog_get_analyticsReturn outreach analytics for a preset period, either as team/campaign totals or as a per-user
Get campaign botdog_get_campaignReturn one campaign's identity, status, owner, and configured dates by campaign ID
Get campaign sequence botdog_get_campaign_sequenceReturn a campaign's configured workflow steps and branches in graph, tree, readable, or
Get campaign statistics botdog_get_campaign_statisticsReturn invitation, message, profile-visit, and response metrics and rates for one campaign
Get current team botdog_get_current_teamReturn the name and user count of the Botdog team authenticated by the connected API key
Get daily analytics botdog_get_daily_analyticsReturn one outreach-activity row per calendar day plus totals for an explicit date range
List accounts botdog_list_accountsReturn connected LinkedIn sending accounts and their connection health for the authenticated
List campaigns botdog_list_campaignsReturn campaigns in the authenticated Botdog team, optionally filtered by status or owner user
List leads botdog_list_leadsReturn one cursor-controlled page of team leads, optionally filtered by campaign, list
List users botdog_list_usersReturn Botdog users in the authenticated team so their IDs can be used in campaign and
Add leads to campaign botdog_add_leads_to_campaignCreate 1 to 100 lead records from LinkedIn profiles in an existing campaign
Send message botdog_send_messageImmediately send a LinkedIn message to an existing lead conversation, or schedule delivery when

Try it: find the Botdog tool you need

Browse the 12 Botdog tools

Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.

Example prompts

Pull the relevant data from Botdog, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from Botdog, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from Botdog, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from Botdog, summarize it in plain English, and point out anything that needs attention.

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 Botdog working from chat.

ManualClawLink
Credential handlingCollect, validate, store, and rotate the Botdog API key yourself, then make sure every tool call uses the right account.Users complete the hosted ClawLink setup once and the connected Botdog account becomes available to the agent without you building credential management.
Ongoing maintenanceYou own refresh logic, permission debugging, environment config, and every provider-specific edge case for Botdog.ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure.
Agent usabilityYou still need to expose the right Botdog actions to the runtime in a format your agent can reliably use.12 tools for Botdog are already exposed through ClawLink, so the agent can read and act from chat immediately.

Composio also exposes Botdog 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 Botdog in the browser, and the 12 tools above work from chat. There is no SDK and no config file, and the Botdog key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.

Troubleshooting

OpenClaw installed the Botdog skill but can't call the tools

The ClawHub skill teaches OpenClaw about Botdog, but the calls run through the ClawLink plugin and your connected account. Make sure Botdog 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 Botdog 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 Botdog tools

Botdog 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 Botdog 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.

Botdog 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 Botdog has the right scopes or account access. A valid key can still be too limited for some reads or writes.

FAQ

Is there a OpenClaw Botdog integration?

Yes. ClawLink is the fastest way to connect OpenClaw to Botdog: link your Botdog account once in the browser and OpenClaw can call the Botdog API through 12 ready-made tools — no custom code or token handling.

How do I add Botdog to OpenClaw with ClawLink?

Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Botdog skill from ClawHub, then you click Connect in the dashboard to authorize Botdog. OpenClaw calls the tools from the next message — no config files, and the Botdog key you paste is stored server-side instead of in your environment.

How long does it take to connect Botdog to OpenClaw?

About two minutes. Sign in, click Connect next to Botdog in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

Why use ClawLink instead of wiring Botdog 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 Botdog working from chat.

OpenClaw installed the Botdog skill but can't call the tools

The ClawHub skill teaches OpenClaw about Botdog, but the calls run through the ClawLink plugin and your connected account. Make sure Botdog 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.