# How to connect EmailOctopus to OpenClaw (paste one key, 20 tools) > Connect EmailOctopus to OpenClaw with ClawLink: paste your EmailOctopus key once and 20 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/emailoctopus The usual route to EmailOctopus 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 EmailOctopus setup: install one ClawHub skill, connect EmailOctopus in the browser, and OpenClaw can call real EmailOctopus 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 EmailOctopus. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect EmailOctopus** — 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 emailoctopus # connect EmailOctopus (browser OAuth) npx -y @useclawlink/cli actions emailoctopus # list available actions npx -y @useclawlink/cli run emailoctopus --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 EmailOctopus in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your EmailOctopus API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from EmailOctopus, 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once EmailOctopus is connected in the dashboard, that agent calls the same 20 EmailOctopus 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). ## EmailOctopus MCP for OpenClaw Looking for a EmailOctopus MCP server for OpenClaw? ClawLink connects EmailOctopus to OpenClaw and exposes 20 EmailOctopus 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 EmailOctopus integration](https://claw-link.dev/hermes/emailoctopus) works the same way. ## What the OpenClaw EmailOctopus integration can do 20 EmailOctopus tools are ready for OpenClaw once the account is connected. The 16 below are the ones people reach for most; your agent can call all 20. ### 16 of 20 EmailOctopus tools for OpenClaw | Tool | What it does | |---|---| | **Get all lists** `emailoctopus_get_all_lists` | Retrieves all the mailing lists associated with the EmailOctopus account | | **Get contact** `emailoctopus_get_contact` | Retrieve details of a specific contact from an EmailOctopus list | | **Get list** `emailoctopus_get_list` | Retrieves details of a specific mailing list by ID | | **Get recent campaigns** `emailoctopus_get_recent_campaigns` | Retrieves a list of recent campaigns from the EmailOctopus account | | **List contacts** `emailoctopus_list_contacts` | Retrieve contacts from an EmailOctopus list | | **List tags** `emailoctopus_list_tags` | Retrieve all tags from a mailing list | | **Create contact** `emailoctopus_create_contact` | Creates a new contact in EmailOctopus | | **Create field** `emailoctopus_create_field` | Create a new custom field on an EmailOctopus mailing list | | **Create list** `emailoctopus_create_list` | Creates a new mailing list in EmailOctopus for organizing and managing email contacts | | **Create tag** `emailoctopus_create_tag` | Create a new tag on an EmailOctopus mailing list | | **Unsubscribe contact** `emailoctopus_unsubscribe_contact` | Unsubscribes a contact from an EmailOctopus mailing list | | **Update contacts batch** `emailoctopus_update_contacts_batch` | Update multiple contacts in an EmailOctopus list in a single batch operation | | **Update field** `emailoctopus_update_field` | Updates an existing custom field on an EmailOctopus list including its label, tag, type, and | | **Update list** `emailoctopus_update_list` | Update an existing mailing list's name in EmailOctopus | | **Update tag** `emailoctopus_update_tag` | Update an existing tag on a mailing list | | **Upsert contact** `emailoctopus_upsert_contact` | Create or update a contact in EmailOctopus | ## Example prompts **Get All Lists** > Pull the relevant data from EmailOctopus, summarize it in plain English, and point out anything that needs attention. **Get Contact** > Pull the relevant data from EmailOctopus, summarize it in plain English, and point out anything that needs attention. **Get List** > Pull the relevant data from EmailOctopus, summarize it in plain English, and point out anything that needs attention. **Get Recent Campaigns** > Pull the relevant data from EmailOctopus, 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 EmailOctopus working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the EmailOctopus API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected EmailOctopus 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 EmailOctopus. | 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 EmailOctopus actions to the runtime in a format your agent can reliably use. | 20 tools for EmailOctopus are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes EmailOctopus 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 EmailOctopus in the browser, and the 20 tools above work from chat. There is no SDK and no config file, and the EmailOctopus 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 EmailOctopus skill but can't call the tools The ClawHub skill teaches OpenClaw about EmailOctopus, but the calls run through the ClawLink plugin and your connected account. Make sure EmailOctopus 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 EmailOctopus 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 EmailOctopus tools EmailOctopus 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 EmailOctopus 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. ### EmailOctopus 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 EmailOctopus has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw EmailOctopus integration? Yes. ClawLink is the fastest way to connect OpenClaw to EmailOctopus: link your EmailOctopus account once in the browser and OpenClaw can call the EmailOctopus API through 20 ready-made tools — no custom code or token handling. ### How do I add EmailOctopus to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink EmailOctopus skill from ClawHub, then you click Connect in the dashboard to authorize EmailOctopus. OpenClaw calls the tools from the next message — no config files, and the EmailOctopus key you paste is stored server-side instead of in your environment. ### How long does it take to connect EmailOctopus to OpenClaw? About two minutes. Sign in, click Connect next to EmailOctopus in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring EmailOctopus 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 EmailOctopus working from chat. ### OpenClaw installed the EmailOctopus skill but can't call the tools The ClawHub skill teaches OpenClaw about EmailOctopus, but the calls run through the ClawLink plugin and your connected account. Make sure EmailOctopus 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](https://claw-link.dev/openclaw/mailchimp) — Create email campaigns and manage audiences