lemlist + Claude Code

Build a lemlist reader with Claude Code Prepare a grounded outreach campaign briefing

Use Claude Code to build a separate read-only lemlist assistant with Agent200. Ground the outreach campaign briefing in returned source data.

On this page
  1. Overview
  2. Before you start
  3. Setup steps
  4. Test your connection
  5. Instructions for AI agents
  6. lemlist tools
  7. How it works
  8. Troubleshooting
  9. FAQ

Overview

Use Claude Code to implement a read-only lemlist reader in your application. Validate identifiers, schemas and access failures before presenting a outreach campaign briefing.

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
Claude Code · Coding agent, with the SDK
Authentication
Managed OAuth, per end user
Tools
5 tools
Model in examples
openai/gpt-5.6-sol

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.
  • Claude Code in your project. It writes the code with the Agent200 SDK; you review it.

Connect lemlist to Claude Code

  1. 1

    Step 1: Create your Agent200 API key

    Create a key on the API keys page and store it securely.

    .env
    Conceptual example
    Store 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. 2

    Step 2: Inspect the real tool definitions

    Confirm the actual lemlist read operations and input schemas in your runtime.

  3. 3

    Step 3: Connect the user’s lemlist account

    Preserve the same stable user identity during authorization and later requests.

    connect.js
    Conceptual example
    Let 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);
    }
  4. 4

    Step 4: Build and test the read-only answer

    Prepare the outreach campaign briefing only from returned source data. The code example illustrates a sequence, not an SDK installation contract.

    run.js
    Conceptual example
    Run 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);

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.

Read the SDK docs

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 Claude Code.

Agent brief
Goal: connect lemlist to Claude Code with Agent200.
Guide: https://www.agent200.com/connectors/lemlist/framework/claude-code/

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. Make sure lemlist is enabled for the project in the Agent200 dashboard (Connectors), with the endpoints and scopes the task needs.
3. Add the Agent200 SDK to the project and create a client with that key.
4. Give every request a stable id for the end user. Agent200 uses only that user's own connections.
5. Connect the user's lemlist account through Agent200. If Agent200 returns an authorization link, show it to the user and continue once they have approved access on lemlist.
6. Run requests through Agent200 with a model (for example openai/gpt-5.6-sol) and "lemlist" in the tools. The model decides when a lemlist tool is needed; Agent200 executes the call.
7. 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.
8. 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 code on the guide page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

The whole guide is also available as Markdown, for agents and LLMs: /connectors/lemlist/framework/claude-code.md

lemlist tools Claude Code can call

  • List campaigns

    Read
    lemlist_list_campaigns

    Find campaigns available to the connected team.

  • Read a campaign

    Read
    lemlist_get_campaign

    Retrieve one identified campaign.

  • List campaign leads

    Read
    lemlist_list_campaign_leads

    Find leads in the selected campaign.

  • Read a lead

    Read
    lemlist_get_lead

    Retrieve one identified campaign lead.

  • List activities

    Read
    lemlist_list_activities

    Review recorded outreach activity in scope.

How it works

  1. 01

    Your app sends the request

    It calls Agent200 with the model, instructions, the input, the end user's id and the lemlist tools.

  2. 02

    The model picks a tool

    The model decides whether a lemlist tool is needed, and with which arguments.

  3. 03

    Agent200 runs the call

    It uses that user's own lemlist connection, within the endpoints and scopes your project allows, and returns the result to the model.

  4. 04

    Your app gets the result

    Agent200 returns the completed result. Your app decides when the agent runs and what happens next.

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.

Is this a native product integration?

This describes a separate application built with Agent200 and Claude Code; it does not install a connector into the Claude Code app.

Use lemlist with another framework

200 OK

lemlist, connected to Claude Code.
One SDK. One API key.

Agent200 handles the OAuth, the tokens and every tool call. You keep your agent, your model and your code.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)