CRM and sales
lemlist for AI agents.
Make the right campaign easier to review.
Read accessible campaigns and related records in lemlist. Prepare a source-grounded outreach campaign briefing within the selected account.
About lemlist
With the lemlist connector, your agent reads outreach campaigns in each user’s own lemlist account. It can list campaigns, read a campaign, list its leads, read a lead, and list activities, using only the tools your project allows.
lemlist is a sales outreach platform for cold email and multichannel campaigns.
Tools
What your agent can do in lemlist.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own lemlist connection.
-
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.
Control
Limits you can set.
You decide what your agent may do in lemlist, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent read campaigns and leads, and switch off
lemlist_list_campaign_leadsif it should not see who is in a campaign. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example campaigns but not leads. A call outside them is refused.
Get started
Connect lemlist
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect lemlist
Each end user authorizes their own lemlist account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own lemlist account, once. const connection = await agent200 .user("user_123") .connect("lemlist"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the lemlist tools
Name the user, the model and the tools. The model decides which lemlist tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "List my active lemlist campaigns", tools: ["lemlist"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Connect the intended account
Use the documented lemlist authorization route. Confirm the organization, team or workspace before reading records.
-
Match access to the request
The lemlist MCP connection uses OAuth. Select the correct team and inspect the live tools before requesting a campaign or lead.
-
Preserve the application user
Keep the same stable application user identity for connection and later requests. Store the Agent200 key outside prompts and code.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the lemlist connector and how to use it.
Connector: lemlist, through Agent200. In code: "lemlist". What it does: Read accessible campaigns and related records in lemlist. Prepare a source-grounded outreach campaign briefing within the selected account. Page: https://www.agent200.com/connectors/lemlist/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on lemlist's own page, through the authorization link Agent200 returns. Never ask a user for a lemlist password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: lemlist_list_campaigns, lemlist_get_campaign, lemlist_list_campaign_leads, lemlist_get_lead, lemlist_list_activities. Name "lemlist" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/lemlist/framework/claude/ https://www.agent200.com/connectors/lemlist/framework/chatgpt/ https://www.agent200.com/connectors/lemlist/framework/claude-code/ https://www.agent200.com/connectors/lemlist/framework/muse/ https://www.agent200.com/connectors/lemlist/framework/grok-bot/ https://www.agent200.com/connectors/lemlist/framework/openai-dots/ https://www.agent200.com/connectors/lemlist/framework/claude-duet/ https://www.agent200.com/connectors/lemlist/framework/hermes-agent/ https://www.agent200.com/connectors/lemlist/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/lemlist.md
Guides
Use lemlist with the AI you build on.
Step-by-step setup for lemlist with a specific model, assistant or agent framework.
-
lemlist + Claude
How to connect lemlist to Claude
-
lemlist + ChatGPT
How to connect lemlist to ChatGPT
-
lemlist + Claude Code
How to connect lemlist to Claude Code
-
lemlist + Muse
How to connect lemlist to Muse
-
lemlist + Grok Bot
How to connect lemlist to Grok Bot
-
lemlist + OpenAI Dots
How to connect lemlist to OpenAI Dots
-
lemlist + Claude Duet
How to connect lemlist to Claude Duet
-
lemlist + Hermes Agent
How to connect lemlist to Hermes Agent
-
lemlist + OpenClaw
How to connect lemlist to OpenClaw
FAQ
lemlist and Agent200, answered.
What access does lemlist need?
The lemlist MCP connection uses OAuth. Select the correct team and inspect the live tools before requesting a campaign or lead. Provider documentation.
Does a list include every record?
Campaign and team scope matter. Do not interpret a paged activity list as every send, open or reply.
Can this workflow make changes?
The listed lemlist operations are read-only. A proposed change in the agent answer does not edit the source.
How should I verify the answer?
Identify the selected campaign and compare the answer with campaign, lead and activity fields. Disclose missing or inaccessible fields.
Are these exact runtime tool schemas?
The listed identifiers describe catalogue capabilities. Discover the actual runtime tool names and input schemas before executing a request.