How to connect Campayn to OpenClaw
Connect Campayn to OpenClaw with ClawLink: paste your Campayn key once and 14 tools work from chat. No MCP server to run, nothing stored on your machine.
CampaynAPI KEYMCPCampayn is an email marketing platform that allows users to create, send, and manage email campaigns.. Once connected, OpenClaw can read and act on Campayn from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Campayn 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 Campayn setup: install one ClawHub skill, connect Campayn in the browser, and OpenClaw can call real Campayn 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 Campayn.
1Install 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
Connect Campayn
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Campayn?"
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-pluginThen 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 Campayn in the ClawLink dashboard — paste your Campayn API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Campayn, 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 loginlogin opens the same browser approval and stores a credential locally. Once Campayn is connected in the dashboard, that agent calls the same 14 Campayn tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Campayn MCP for OpenClaw
Looking for a Campayn MCP server for OpenClaw? ClawLink connects Campayn to OpenClaw and exposes 14 Campayn tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Campayn integration works the same way.
What the OpenClaw Campayn integration can do
14 Campayn tools are ready for OpenClaw once the account is connected. The 11 below are the ones people reach for most; your agent can call all 14.
11 of 14 Campayn tools for OpenClaw
| Tool | What it does |
|---|---|
Get contact campayn_get_contact | Retrieve a specific contact by ID |
Get contacts campayn_get_contacts | Retrieves all contacts from a specific contact list in Campayn |
Get lists campayn_get_lists | Retrieve all contact lists |
Get message campayn_get_message | Retrieve engagement statistics for a specific email message by ID |
Get messages campayn_get_messages | Retrieve all email messages |
Get reports campayn_get_reports | Retrieve report URLs and metadata for sent and scheduled emails |
Get webform campayn_get_webform | Retrieve details of a specific webform by ID |
Get webforms campayn_get_webforms | Retrieve all webforms for a specific contact list |
Create contact campayn_create_contact | Create a new contact in a specific list |
Update list campayn_update_list | Update a contact list |
Unsubscribe contact campayn_unsubscribe_contact | Unsubscribe contacts from a list by contact id or email address |
Try it: find the Campayn tool you need
Browse the 11 Campayn 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 Campayn, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Campayn, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Campayn, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Campayn, 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 Campayn working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Campayn API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Campayn 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 Campayn. | 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 Campayn actions to the runtime in a format your agent can reliably use. | 14 tools for Campayn are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Campayn 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 Campayn in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the Campayn 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 Campayn skill but can't call the tools
The ClawHub skill teaches OpenClaw about Campayn, but the calls run through the ClawLink plugin and your connected account. Make sure Campayn 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 Campayn 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 Campayn tools
Campayn 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 Campayn 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.
Campayn 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 Campayn 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 Campayn integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Campayn: link your Campayn account once in the browser and OpenClaw can call the Campayn API through 14 ready-made tools — no custom code or token handling.
How do I add Campayn to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Campayn skill from ClawHub, then you click Connect in the dashboard to authorize Campayn. OpenClaw calls the tools from the next message — no config files, and the Campayn key you paste is stored server-side instead of in your environment.
How long does it take to connect Campayn to OpenClaw?
About two minutes. Sign in, click Connect next to Campayn in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Campayn 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 Campayn working from chat.
OpenClaw installed the Campayn skill but can't call the tools
The ClawHub skill teaches OpenClaw about Campayn, but the calls run through the ClawLink plugin and your connected account. Make sure Campayn 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.
