# How to connect Lemlist to Hermes Agent (paste one key, 54 tools) > Connect Lemlist to Hermes with ClawLink: paste your Lemlist key once and 54 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/lemlist Most guides for giving Hermes Agent Lemlist 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 Lemlist setup: pair once in the browser and your always-on Hermes agent can act on Lemlist for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. **Start here — paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. ## Setup It takes three steps to connect Hermes to Lemlist. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Lemlist** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Alternative for any agent (no plugin needed):** if the Hermes Agent 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 lemlist # connect Lemlist (browser OAuth) npx -y @useclawlink/cli actions lemlist # list available actions npx -y @useclawlink/cli run lemlist --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash 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 test ``` Then connect Lemlist in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Lemlist API key once. Verify the connection by asking Hermes: > Pull the relevant data from Lemlist, 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Lemlist is connected in the dashboard, that agent calls the same 54 Lemlist 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). ## Lemlist MCP for Hermes Looking for a Lemlist MCP server for Hermes Agent? ClawLink connects Lemlist to Hermes Agent and exposes 54 Lemlist 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 OpenClaw instead? The [OpenClaw Lemlist integration](https://claw-link.dev/openclaw/lemlist) works the same way. ## What the Hermes Agent Lemlist integration can do 54 Lemlist tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 54. ### 30 of 54 Lemlist tools for Hermes | Tool | What it does | |---|---| | **Get all webhooks** `lemlist_get_all_webhooks` | List Lemlist webhooks | | **Get campaign by ID** `lemlist_get_campaign_by_id` | Get a Lemlist campaign by ID | | **Get campaign sequences** `lemlist_get_campaign_sequences` | List Lemlist campaign sequences | | **Get campaign stats** `lemlist_get_campaign_stats` | Get Lemlist campaign statistics | | **Get contact messages** `lemlist_get_contact_messages` | List Lemlist contact messages | | **Get label** `lemlist_get_label` | Get a Lemlist label | | **Get list campaigns** `lemlist_get_list_campaigns` | List Lemlist campaigns | | **Get list tasks** `lemlist_get_list_tasks` | List Lemlist tasks | | **Get list team senders** `lemlist_get_list_team_senders` | List Lemlist team senders | | **Get retrieve activities** `lemlist_get_retrieve_activities` | List Lemlist activities | | **Get retrieve lead by email** `lemlist_get_retrieve_lead_by_email` | Get a Lemlist lead by email | | **Get campaign export status** `lemlist_get_campaign_export_status` | Check the status of an asynchronous campaign export | | **Get companies schema** `lemlist_get_companies_schema` | Retrieve the schema definition for companies in the people database | | **Get database filters** `lemlist_get_database_filters` | Retrieve available filters for searching the people and companies database | | **Get export campaign leads** `lemlist_get_export_campaign_leads` | Export campaign leads with state filtering and choose between JSON or CSV output | | **Get export unsubscribes** `lemlist_get_export_unsubscribes` | Download a CSV file containing all unsubscribed email addresses | | **Get get unsubscribe email** `lemlist_get_get_unsubscribe_email` | Retrieve a single unsubscribed email record | | **Get list watchlist signals** `lemlist_get_list_watchlist_signals` | Retrieve paginated watchlist signals with filtering and sorting | | **Get people schema** `lemlist_get_people_schema` | Retrieve the schema definition for people in the people database | | **Get retrieve unsubscribes** `lemlist_get_retrieve_unsubscribes` | Retrieve the list of all people who are unsubscribed | | **Get team credits** `lemlist_get_team_credits` | Retrieve credits left in the team | | **Get team info** `lemlist_get_team_info` | Retrieve information about your team | | **Get user** `lemlist_get_user` | Retrieve all information for a specific user by their ID | | **Get user info** `lemlist_get_user_info` | Retrieve all information of the authenticated user | | **List companies** `lemlist_list_companies` | Retrieve a paginated list of all companies in your CRM | | **List company notes** `lemlist_list_company_notes` | Retrieve all notes associated with a specific company | | **List labels** `lemlist_list_labels` | List all labels available to your team | | **Search companies database** `lemlist_search_companies_database` | Search the companies database using filters, keywords, and pagination | | **Search people database** `lemlist_search_people_database` | Search the Lemlist people database using filters, keywords, and pagination | | **Create company note** `lemlist_create_company_note` | Create a note attached to a specific company | ## Example prompts **Get All Webhooks** > Pull the relevant data from Lemlist, summarize it in plain English, and point out anything that needs attention. **Get Campaign By Id** > Pull the relevant data from Lemlist, summarize it in plain English, and point out anything that needs attention. **Get Campaign Sequences** > Pull the relevant data from Lemlist, summarize it in plain English, and point out anything that needs attention. **Get Campaign Stats** > Pull the relevant data from Lemlist, 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 Lemlist working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Lemlist API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Lemlist 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 Lemlist. | 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 Lemlist actions to the runtime in a format your agent can reliably use. | 54 tools for Lemlist are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Lemlist 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 Lemlist in the browser, and the 54 tools above work from chat. There is no SDK and no config file, and the Lemlist 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. ### Hermes paired but still can't use Lemlist 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 Lemlist 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 Lemlist tools Lemlist 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 Lemlist 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. ### Lemlist 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 Lemlist has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a Hermes Agent Lemlist integration? Yes. ClawLink is the fastest way to connect Hermes to Lemlist: link your Lemlist account once in the browser and Hermes Agent can call the Lemlist API through 54 ready-made tools — no custom code or token handling. ### How do I connect Lemlist 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 Lemlist in the dashboard and Hermes can use it from the next message — no config files, and the Lemlist key you paste is stored server-side instead of in your environment. ### How long does it take to connect Lemlist to Hermes Agent? About two minutes. Sign in, click Connect next to Lemlist in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Lemlist 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 Lemlist working from chat. ### Hermes paired but still can't use Lemlist 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`. ## Related - [ActiveCampaign tools](https://claw-link.dev/hermes/activecampaign) — Marketing automation, CRM, and email marketing - [Connect Benchmark Email](https://claw-link.dev/hermes/benchmark-email) — Benchmark Email is a comprehensive email marketing platform offering tools for creating, sending, and analyzing email campaigns. - [Mailchimp](https://claw-link.dev/hermes/mailchimp) — Create email campaigns and manage audiences