# Connect lemlist to Hermes Agent Prepare a grounded outreach campaign briefing

> Read campaigns with Hermes Agent and Agent200. Prepare a outreach campaign briefing using the connected user’s own lemlist account.

- Page: https://www.agent200.com/connectors/lemlist/framework/hermes-agent/
- Connector: [lemlist](https://www.agent200.com/connectors/lemlist.md)
- Framework: Hermes Agent
- Updated: 2026-11-17

## Instructions for AI agents

Goal: connect lemlist to Hermes Agent with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/lemlist/framework/hermes-agent/

1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Hermes Agent's settings themselves: never ask for it in chat and never write it into files you share.
2. Make sure lemlist is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs.
3. Add Agent200's MCP server to Hermes Agent: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Hermes Agent's exact menus or commands.
4. The first lemlist request returns an authorization link if the user has not connected lemlist yet: show it to them and continue once they have approved access on lemlist's own page.
5. Check it works with this request: "Read the lemlist campaign I identify and prepare a outreach campaign briefing. Name the source and use only campaign, lead and activity fields. State access gaps; do not change records."
   What should come back:
   - The selected campaign is identified.
   - Only the returned campaign, lead and activity fields are reported.
   - Access gaps and missing context are explicit; no source data is changed.
6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in lemlist, then retry.

## Overview

Inspect the Agent200 tools Hermes advertises after connection. Use discovered names and input schemas for the campaign read, not guesses from catalogue labels.

Start with one identified campaign. Preserve returned campaign, lead and activity fields; report missing data and keep the workflow read-only.

Provider reference: [lemlist API](https://developer.lemlist.com/api-reference/getting-started/overview).

- **Connector:** [lemlist](https://www.agent200.com/connectors/lemlist/)
- **Works with:** Hermes Agent · Agent app, through MCP
- **Authentication:** Managed OAuth, per end user
- **You need:** [An Agent200 API key](https://agent200.com/platform/apikeys/)
- **Tools:** [5 tools](https://www.agent200.com/connectors/lemlist/framework/hermes-agent/#tools)
- **MCP server:** `https://api.agent200.com/mcp/`

## Before you start

- **An Agent200 API key.** Create one on the [API keys page](https://agent200.com/platform/apikeys/) of the dashboard.
- **lemlist enabled for your project.** In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- **An end user with a lemlist account.** They approve access once, on lemlist's own page.
- **Hermes Agent, with custom MCP servers allowed.** Hermes Agent is open source and self-hosted: anyone running it can add MCP servers in its config file.

## Connect lemlist to Hermes Agent

### Step 1: Create your Agent200 API key

Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Hermes Agent in the next step, as "Authorization: Bearer <your key>". One key covers lemlist and every other connector enabled for your project. Keep it out of chats and source control.

Create an API key: https://agent200.com/platform/apikeys/

### Step 2: Store your key in ~/.hermes/.env

Keep the key out of `config.yaml`: Hermes reads it from `~/.hermes/.env`.

File `~/.hermes/.env`:

```bash
AGENT200_API_KEY=your-agent200-api-key
```

### Step 3: Add the server to ~/.hermes/config.yaml

Add an entry under `mcp_servers` with the URL and the Authorization header. Do not set `transport: sse`: Agent200 serves streamable HTTP.

File `~/.hermes/config.yaml`:

```text
mcp_servers:
  agent200:
    url: "https://api.agent200.com/mcp/"
    headers:
      Authorization: "Bearer ${AGENT200_API_KEY}"
```

### Step 4: Reload and test

In a running session, run `/reload-mcp`, or restart Hermes. Then check what the server returned from a terminal.

File `Terminal`:

```bash
# In a running Hermes session: /reload-mcp
hermes mcp test agent200
hermes mcp list
```

### Step 5: Connect your lemlist account

The first time you ask Hermes Agent for something in lemlist, Agent200 returns an authorization link. Open it and approve access on lemlist's own page. Agent200 stores the connection and keeps it working; your password never reaches Hermes Agent or Agent200.

## Test your connection

Ask: "Read the lemlist campaign I identify and prepare a outreach campaign briefing. Name the source and use only campaign, lead and activity fields. State access gaps; do not change records."

What should come back:

- The selected campaign is identified.
- Only the returned campaign, lead and activity fields are reported.
- Access gaps and missing context are explicit; no source data is changed.

Check the selected campaign ID, account scope, read permission and pagination. Campaign and team scope matter. Do not interpret a paged activity list as every send, open or reply.

## lemlist tools Hermes Agent can call

- **List campaigns** (`lemlist_list_campaigns`, read): Find campaigns available to the connected team.
- **Read a campaign** (`lemlist_get_campaign`, read): Retrieve one identified campaign.
- **List campaign leads** (`lemlist_list_campaign_leads`, read): Find leads in the selected campaign.
- **Read a lead** (`lemlist_get_lead`, read): Retrieve one identified campaign lead.
- **List activities** (`lemlist_list_activities`, read): Review recorded outreach activity in scope.

## How it works

1. **You ask Hermes Agent.** In your own words, for something in lemlist.
2. **Hermes Agent picks a tool.** It sees the lemlist tools on the Agent200 MCP server and calls the one the request needs.
3. **Agent200 runs the call.** With your own lemlist connection, within the tools and scopes your project allows.
4. **Hermes Agent answers.** It gets the result back from the MCP server and uses it in its reply or its next step.

**Each user's own connection.** Connections belong to individual end users. A request for one user never reaches another user's lemlist account.

**Permissions at every level.** Your project settings decide what the agent may request, the end user decides what they authorize, and lemlist enforces what its API grants.

## Troubleshooting

### The source cannot be read

Check the selected campaign ID, account scope, read permission and pagination. Campaign and team scope matter. Do not interpret a paged activity list as every send, open or reply.

## FAQ

### How do I verify this result?

Compare the named campaign and returned campaign, lead and activity fields with the source. Treat missing information as missing, not as a fact.

## Use lemlist with another framework

- [lemlist + Claude](https://www.agent200.com/connectors/lemlist/framework/claude.md)
- [lemlist + ChatGPT](https://www.agent200.com/connectors/lemlist/framework/chatgpt.md)
- [lemlist + Claude Code](https://www.agent200.com/connectors/lemlist/framework/claude-code.md)
- [lemlist + Muse](https://www.agent200.com/connectors/lemlist/framework/muse.md)
- [lemlist + Grok Bot](https://www.agent200.com/connectors/lemlist/framework/grok-bot.md)
- [lemlist + OpenAI Dots](https://www.agent200.com/connectors/lemlist/framework/openai-dots.md)
- [lemlist + Claude Duet](https://www.agent200.com/connectors/lemlist/framework/claude-duet.md)
- [lemlist + OpenClaw](https://www.agent200.com/connectors/lemlist/framework/openclaw.md)

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
