# How to connect Emelia to OpenClaw (paste one key, 22 tools) > Connect Emelia to OpenClaw with ClawLink: paste your Emelia key once and 22 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/emelia The usual route to Emelia 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 Emelia setup: install one ClawHub skill, connect Emelia in the browser, and OpenClaw can call real Emelia 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 Emelia. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Emelia** — 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 emelia # connect Emelia (browser OAuth) npx -y @useclawlink/cli actions emelia # list available actions npx -y @useclawlink/cli run emelia --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 Emelia in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Emelia API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Emelia, 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 Emelia is connected in the dashboard, that agent calls the same 22 Emelia 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). ## Emelia MCP for OpenClaw Looking for a Emelia MCP server for OpenClaw? ClawLink connects Emelia to OpenClaw and exposes 22 Emelia 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 Emelia integration](https://claw-link.dev/hermes/emelia) works the same way. ## What the OpenClaw Emelia integration can do 22 Emelia tools are ready for OpenClaw once the account is connected. The 19 below are the ones people reach for most; your agent can call all 22. ### 19 of 22 Emelia tools for OpenClaw | Tool | What it does | |---|---| | **Get campaign activities** `emelia_get_campaign_activities` | Retrieve activities for a specific email campaign | | **Get find email result** `emelia_get_find_email_result` | Retrieve the result of a previously initiated email find job | | **Get find phone result** `emelia_get_find_phone_result` | Retrieve the outcome of a previously initiated phone-find job | | **Get linkedin campaign activities** `emelia_get_linkedin_campaign_activities` | Retrieve activities for a campaign | | **Get verify email result** `emelia_get_verify_email_result` | Get the result of an email verification job | | **List campaign contacts** `emelia_list_campaign_contacts` | List contacts in a specific email campaign | | **List campaigns** `emelia_list_campaigns` | Retrieve all email campaigns | | **List email providers** `emelia_list_email_providers` | Retrieve all configured email providers | | **List linkedin campaigns** `emelia_list_linkedin_campaigns` | List all LinkedIn campaigns | | **List webhooks** `emelia_list_webhooks` | Retrieve all webhooks | | **Add contact to blacklist** `emelia_add_contact_to_blacklist` | Add a contact to the email blacklist | | **Add contact to campaign** `emelia_add_contact_to_campaign` | Add a contact to an email campaign | | **Create campaign** `emelia_create_campaign` | Create a new email campaign | | **Create linkedin campaign** `emelia_create_linkedin_campaign` | Create a new LinkedIn campaign | | **Create webhook** `emelia_create_webhook` | Create a new webhook for campaign events | | **Find email single contact** `emelia_find_email_single_contact` | Initiate a job to find the email address of a specific contact | | **Initiate email verification job** `emelia_initiate_email_verification_job` | Initiate an asynchronous email verification job." | | **Initiate phone find job** `emelia_initiate_phone_find_job` | Initiate a phone-find job for a single contact | | **Remove contact from blacklist** `emelia_remove_contact_from_blacklist` | Remove a contact or domain from the email blacklist | ## Example prompts **Get Campaign Activities** > Pull the relevant data from Emelia, summarize it in plain English, and point out anything that needs attention. **Get Find Email Result** > Pull the relevant data from Emelia, summarize it in plain English, and point out anything that needs attention. **Get Find Phone Result** > Pull the relevant data from Emelia, summarize it in plain English, and point out anything that needs attention. **Get Linkedin Campaign Activities** > Pull the relevant data from Emelia, 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 Emelia working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Emelia API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Emelia 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 Emelia. | 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 Emelia actions to the runtime in a format your agent can reliably use. | 22 tools for Emelia are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Emelia 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 Emelia in the browser, and the 22 tools above work from chat. There is no SDK and no config file, and the Emelia 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 Emelia skill but can't call the tools The ClawHub skill teaches OpenClaw about Emelia, but the calls run through the ClawLink plugin and your connected account. Make sure Emelia 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 Emelia 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 Emelia tools Emelia 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 Emelia 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. ### Emelia 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 Emelia has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Emelia integration? Yes. ClawLink is the fastest way to connect OpenClaw to Emelia: link your Emelia account once in the browser and OpenClaw can call the Emelia API through 22 ready-made tools — no custom code or token handling. ### How do I add Emelia to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Emelia skill from ClawHub, then you click Connect in the dashboard to authorize Emelia. OpenClaw calls the tools from the next message — no config files, and the Emelia key you paste is stored server-side instead of in your environment. ### How long does it take to connect Emelia to OpenClaw? About two minutes. Sign in, click Connect next to Emelia in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Emelia 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 Emelia working from chat. ### OpenClaw installed the Emelia skill but can't call the tools The ClawHub skill teaches OpenClaw about Emelia, but the calls run through the ClawLink plugin and your connected account. Make sure Emelia 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 - [Connect ActiveCampaign](https://claw-link.dev/openclaw/activecampaign) — Marketing automation, CRM, and email marketing - [Benchmark Email tools](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