# Connect lemlist to OpenClaw Prepare a grounded outreach campaign briefing

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

- Page: https://www.agent200.com/connectors/lemlist/framework/openclaw/
- Connector: [lemlist](https://www.agent200.com/connectors/lemlist.md)
- Framework: OpenClaw
- Updated: 2026-11-17

## Instructions for AI agents

Goal: connect lemlist to OpenClaw with Agent200, through its MCP server.
Guide: https://www.agent200.com/connectors/lemlist/framework/openclaw/

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 OpenClaw'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 OpenClaw: 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 OpenClaw'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

Save the Agent200 server settings in OpenClaw, inspect tool discovery, then read one campaign the user can access. A saved setting alone does not verify the read.

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:** OpenClaw · 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/openclaw/#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.
- **OpenClaw, with custom MCP servers allowed.** OpenClaw is open source and self-hosted: anyone running it can add MCP servers, from the CLI, the config file or the Control UI.

## Connect lemlist to OpenClaw

### Step 1: Create your Agent200 API key

Create a key on the [API keys page](https://agent200.com/platform/apikeys/) and store it securely.

File `.env`:

```bash
# Keep the key out of your code, prompts and chats.
export AGENT200_API_KEY="paste-your-key-here"
```

(Conceptual example of the Agent200 SDK.)

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

OpenClaw fills `${AGENT200_API_KEY}` in its config from `~/.openclaw/.env`, so the key never sits in the config itself.

File `~/.openclaw/.env`:

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

### Step 3: Save the server

`openclaw mcp set` takes one JSON object. Always set the transport to `streamable-http`: without it OpenClaw uses SSE. Keep the single quotes so your shell leaves `${AGENT200_API_KEY}` for OpenClaw. In the Control UI, add it under **Settings > MCP**, then put the header in the config editor on the same page.

Stop the Gateway before CLI changes or live probes against its state. Use the Control UI for supported changes while it is running.

File `Terminal`:

```bash
openclaw mcp set agent200 '{"url":"https://api.agent200.com/mcp/","transport":"streamable-http","headers":{"Authorization":"Bearer ${AGENT200_API_KEY}"}}'
```

### Step 4: Probe the server

Open a live connection and list the tools Agent200 offers. If a Gateway runs elsewhere, reload or restart it.

File `Terminal`:

```bash
openclaw mcp doctor agent200 --probe
openclaw mcp status --verbose
```

### Step 5: Authorize lemlist

Connect the intended user and test one accessible campaign.

## 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 OpenClaw 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 OpenClaw.** In your own words, for something in lemlist.
2. **OpenClaw 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. **OpenClaw 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 + Hermes Agent](https://www.agent200.com/connectors/lemlist/framework/hermes-agent.md)

---

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