How to connect Emelia to Hermes Agent
Connect Emelia to Hermes with ClawLink: paste your Emelia key once and 22 tools work from chat. No MCP server to run, nothing stored on your machine.
EmeliaAPI KEYMCPEmelia is an all-in-one B2B prospecting tool offering features like cold-emailing, LinkedIn outreach, email warm-up, email finder, and LinkedIn Sales Navigator scraping.. Once connected, Hermes Agent can read and act on Emelia from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Emelia access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Emelia setup: pair once in the browser and your always-on Hermes agent can act on Emelia for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect Hermes to Emelia.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Emelia
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Emelia?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin # prints an approval link — open it and approve
hermes clawlink finish # after approving in the browser
hermes clawlink testThen connect Emelia in the ClawLink dashboard — paste your Emelia API key once.
Verify the connection by asking Hermes:
Pull the relevant data from Emelia, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The Hermes 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 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.
Emelia MCP for Hermes
Looking for a Emelia MCP server for Hermes Agent? ClawLink connects Emelia to Hermes Agent and exposes 22 Emelia tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Emelia integration works the same way.
What the Hermes Agent Emelia integration can do
22 Emelia tools are ready for Hermes Agent 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 Hermes
| 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 |
Try it: find the Emelia tool you need
Browse the 19 Emelia tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Emelia, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Emelia, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Emelia, summarize it in plain English, and point out anything that needs attention.
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 Hermes Agent. 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 Hermes Agent 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 comparison.
Troubleshooting
Hermes paired but still can't use Emelia
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
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.
FAQ
Is there a Hermes Agent Emelia integration?
Yes. ClawLink is the fastest way to connect Hermes to Emelia: link your Emelia account once in the browser and Hermes Agent can call the Emelia API through 22 ready-made tools — no custom code or token handling.
How do I connect Emelia to Hermes with ClawLink?
Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Emelia in the dashboard and Hermes can use it 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 Hermes Agent?
About two minutes. Sign in, click Connect next to Emelia in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Emelia working from chat.
Hermes paired but still can't use Emelia
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
