lemlist + OpenClaw
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.
On this page
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.
- Connector
- lemlist
- Works with
- OpenClaw · Agent app, through MCP
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 5 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page 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
-
1
Step 1: Create your Agent200 API key
Create a key on the API keys page and store it securely.
.envConceptual exampleStore the Agent200 API key as an environment variable # Keep the key out of your code, prompts and chats. export AGENT200_API_KEY="paste-your-key-here" -
2
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.~/.openclaw/.envMCP: OpenClaw key in ~/.openclaw/.env AGENT200_API_KEY=your-agent200-api-key -
3
Step 3: Save the server
openclaw mcp settakes one JSON object. Always set the transport tostreamable-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.
TerminalMCP: OpenClaw save the server from the CLI openclaw mcp set agent200 '{"url":"https://api.agent200.com/mcp/","transport":"streamable-http","headers":{"Authorization":"Bearer ${AGENT200_API_KEY}"}}' -
4
Step 4: Probe the server
Open a live connection and list the tools Agent200 offers. If a Gateway runs elsewhere, reload or restart it.
TerminalMCP: OpenClaw probe the server openclaw mcp doctor agent200 --probe openclaw mcp status --verbose -
5
Step 5: Authorize lemlist
Connect the intended user and test one accessible campaign.
Test your connection
Run one request to check everything is wired up.
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.
Get your API key
Create a key in the Agent200 dashboard. It reaches lemlist and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect lemlist to OpenClaw.
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.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/lemlist/framework/openclaw.md
lemlist tools OpenClaw can call
-
List campaigns
Readlemlist_list_campaignsFind campaigns available to the connected team.
-
Read a campaign
Readlemlist_get_campaignRetrieve one identified campaign.
-
List campaign leads
Readlemlist_list_campaign_leadsFind leads in the selected campaign.
-
Read a lead
Readlemlist_get_leadRetrieve one identified campaign lead.
-
List activities
Readlemlist_list_activitiesReview recorded outreach activity in scope.
No tool matches that search.
How it works
-
01
You ask OpenClaw
In your own words, for something in lemlist.
-
02
OpenClaw picks a tool
It sees the lemlist tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
With your own lemlist connection, within the tools and scopes your project allows.
-
04
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.
