# 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.

- Page: https://www.agent200.com/connectors/lemlist/
- Category: CRM and sales
- Authentication: Managed OAuth
- Identifier in code: `lemlist`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-18

## Instructions for AI agents

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/

## About

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.

## lemlist tools

- **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.

## Limits you can set

**Turn single tools on or off.** Let the agent read campaigns and leads, and switch off `lemlist_list_campaign_leads` if 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

### Step 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.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 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.

File `connect.js`:

```js
// 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);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 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.

File `run.js`:

```js
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);
```

(Conceptual example of the Agent200 SDK.)

## 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.

## Example requests

- "List my active lemlist campaigns"
- "Show the leads in the Q1 outreach campaign"
- "What activity did we get on the fintech campaign"

## Guides: lemlist with your AI framework

- [lemlist + Claude](https://www.agent200.com/connectors/lemlist/framework/claude.md): Read campaigns with Claude and Agent200. Prepare a outreach campaign briefing using the connected user’s own lemlist account.
- [lemlist + ChatGPT](https://www.agent200.com/connectors/lemlist/framework/chatgpt.md): Use ChatGPT to build a separate read-only lemlist assistant with Agent200. Ground the outreach campaign briefing in returned source data.
- [lemlist + Claude Code](https://www.agent200.com/connectors/lemlist/framework/claude-code.md): Use Claude Code to build a separate read-only lemlist assistant with Agent200. Ground the outreach campaign briefing in returned source data.
- [lemlist + Muse](https://www.agent200.com/connectors/lemlist/framework/muse.md): Read campaigns with Muse and Agent200. Prepare a outreach campaign briefing using the connected user’s own lemlist account.
- [lemlist + Grok Bot](https://www.agent200.com/connectors/lemlist/framework/grok-bot.md): Read campaigns with Grok Bot and Agent200. Prepare a outreach campaign briefing using the connected user’s own lemlist account.
- [lemlist + OpenAI Dots](https://www.agent200.com/connectors/lemlist/framework/openai-dots.md): Use OpenAI Dots to build a separate read-only lemlist assistant with Agent200. Ground the outreach campaign briefing in returned source data.
- [lemlist + Claude Duet](https://www.agent200.com/connectors/lemlist/framework/claude-duet.md): Read campaigns with Claude Duet and Agent200. Prepare a outreach campaign briefing using the connected user’s own lemlist account.
- [lemlist + Hermes Agent](https://www.agent200.com/connectors/lemlist/framework/hermes-agent.md): Read campaigns with Hermes Agent and Agent200. Prepare a outreach campaign briefing using the connected user’s own lemlist account.
- [lemlist + OpenClaw](https://www.agent200.com/connectors/lemlist/framework/openclaw.md): Read campaigns with OpenClaw and Agent200. Prepare a outreach campaign briefing using the connected user’s own lemlist account.

## FAQ

### 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](https://developer.lemlist.com/api-reference/getting-started/overview).

### 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.

## Related connectors

- [HubSpot](https://www.agent200.com/connectors/hubspot.md): Look up and update contacts, companies and deals in your users' HubSpot CRM.
- [Salesforce](https://www.agent200.com/connectors/salesforce.md): Query and update accounts, contacts and opportunities in Salesforce.
- [LinkedIn](https://www.agent200.com/connectors/linkedin.md): Share posts and read profile details on LinkedIn on behalf of each of your users, where the relevant API permissions are available.
- [Zendesk](https://www.agent200.com/connectors/zendesk.md): Search, read, create and update Zendesk tickets, and reply to customers, on behalf of each of your users.

---

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