Skip to main content
Agent skill

Lemlist Automation

Automate Lemlist multichannel outreach -- manage campaigns, enroll leads, add personalization variables, export campaign data, and handle unsubscribes via the Composio MCP integration.

Get started

Get the complete skill folder, including its scripts and reference files.

This workflow depends on an external MCP integration. Check the source for the server, account access and setup it requires.

When to use this skill

Use Lemlist Automation when an AI agent needs a reusable SKILL.md workflow for this job: Automate Lemlist multichannel outreach -- manage campaigns, enroll leads, add personalization variables, export campaign data, and handle unsubscribes via the Composio MCP integration.

When not to use it

Skip Lemlist Automation when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/lemlist-automation
# Save SKILL.md to ~/.claude/skills/lemlist-automation/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/lemlist-automation/SKILL.md. For a shared project, commit the folder at .claude/skills/lemlist-automation/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Lemlist Automation skill for this task: Use Lemlist Automation when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

72/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
63/100
Source signals
80/100
Model compatibility evidence
  • claudeinferred

    The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Lemlist Automation

Automate your Lemlist multichannel outreach workflows -- manage campaigns, enroll leads at scale, enrich with custom variables, export campaign data, and clean up unsubscribes.

**Toolkit docs:** [composio.dev/toolkits/lemlist](https://composio.dev/toolkits/lemlist)

---

## Setup

1. Add the Composio MCP server to your client: `https://rube.app/mcp` 2. Connect your Lemlist account when prompted (API key authentication) 3. Start using the workflows below

---

## Core Workflows

### 1. List and Discover Campaigns

Use `LEMLIST_GET_LIST_CAMPAIGNS` to enumerate all campaigns by status, with pagination support.

``` Tool: LEMLIST_GET_LIST_CAMPAIGNS Inputs: - status: "running" | "draft" | "archived" | "ended" | "paused" | "errors" (optional) - limit: integer (max 100, default 100) - offset: integer (pagination offset) - sortBy: "createdAt" - sortOrder: "asc" | "desc" ```

**Important:** The response may be wrapped as `{campaigns: [...], pagination: {...}}` instead of a flat list. Always extract from the `campaigns` key.

### 2. Get Campaign Details

Use `LEMLIST_GET_CAMPAIGN_BY_ID` to validate campaign configuration before writes.

``` Tool: LEMLIST_GET_CAMPAIGN_BY_ID Inputs: - campaignId: string (required) -- e.g., "cam_A1B2C3D4E5F6G7H8I9" ```

### 3. Enroll Leads into a Campaign

Use `LEMLIST_POST_CREATE_LEAD_IN_CAMPAIGN` to add leads with optional email finding, phone lookup, and LinkedIn enrichment.

``` Tool: LEMLIST_POST_CREATE_LEAD_IN_CAMPAIGN Inputs: - campaignId: string (required) - email: string (required) - firstName, lastName, companyName, companyDomain: string (optional) - jobTitle, phone, linkedinUrl, icebreaker: string (optional) - deduplicate: boolean (prevents cross-campaign duplicates) - findEmail, findPhone, verifyEmail, linkedinEnrichment: boolean (optional) - timezone: string (IANA format, e.g., "America/New_York") ```

**Bulk pattern:** Chunk leads into batches of ~50 and checkpoint progress between batches.

### 4. Add Custom Variables to a Lead

Use `LEMLIST_POST_ADD_VARIABLES_TO_LEAD` to enrich leads with personalization fields after enrollment.

``` Tool: LEMLIST_POST_ADD_VARIABLES_TO_LEAD Inputs: - leadId: string (required) -- internal Lemlist lead ID (NOT email) - company: string (required) -- must match your company name in Lemlist - variables: object (required) -- key-value pairs, e.g., {"score": "42", "color": "yellow"} ```

**Important:** This is NOT an upsert -- attempting to add variables that already exist will fail. Resolve the internal `leadId` via `LEMLIST_GET_RETRIEVE_LEAD_BY_EMAIL` if you only have the email address.

### 5. Export Campaign Leads

Use `LEMLIST_GET_EXPORT_CAMPAIGN_LEADS` to download leads with state filtering for reporting or QA.

``` Tool: LEMLIST_GET_EXPORT_CAMPAIGN_LEADS Inputs: - campaignId: string (required) - (supports state filtering and JSON/CSV output) ```

### 6. Unsubscribe Lead from Campaign

Use `LEMLIST_DELETE_UNSUBSCRIBE_LEAD_FROM_CAMPAIGN` to stop outreach by removing a lead from a campaign.

``` Tool: LEMLIST_DELETE_UNSUBSCRIBE_LEAD_FROM_CAMPAIGN Inputs: - campaignId: string (required) - leadId or email: string (required) ```

---

## Known Pitfalls

| Pitfall | Detail | |---------|--------| | Wrapped campaign list | `LEMLIST_GET_LIST_CAMPAIGNS` may return `{campaigns: [...], pagination: {...}}` instead of a flat array. Always extract from the `campaigns` key. | | Cross-campaign deduplication | `LEMLIST_POST_CREATE_LEAD_IN_CAMPAIGN` with deduplication enabled fails with HTTP 500 "Lead already in other campaign" -- disable deduplication for intentional cross-campaign enrollment. | | Bulk import failures | Chunk bulk imports to ~50 per batch with checkpoints to avoid losing partial progress on intermittent failures. | | Invalid leadId | `LEMLIST_POST_ADD_VARIABLES_TO_LEAD` returns HTTP 400 "Invalid leadId" when using an email as the leadId -- resolve the internal ID via `LEMLIST_GET_RETRIEVE_LEAD_BY_EMAIL` first. | | Variable collisions | `LEMLIST_POST_ADD_VARIABLES_TO_LEAD` is not an upsert. Adding keys that already exist returns HTTP 400 "Variables X already exist". |

---

## Quick Reference

| Tool Slug | Description | |-----------|-------------| | `LEMLIST_GET_LIST_CAMPAIGNS` | List all campaigns with status filter and pagination | | `LEMLIST_GET_CAMPAIGN_BY_ID` | Get detailed campaign info by ID | | `LEMLIST_POST_CREATE_LEAD_IN_CAMPAIGN` | Create and enroll a lead into a campaign | | `LEMLIST_POST_ADD_VARIABLES_TO_LEAD` | Add custom personalization variables to a lead | | `LEMLIST_GET_RETRIEVE_LEAD_BY_EMAIL` | Look up a lead by email address | | `LEMLIST_GET_EXPORT_CAMPAIGN_LEADS` | Export leads from a campaign with state filtering | | `LEMLIST_DELETE_UNSUBSCRIBE_LEAD_FROM_CAMPAIGN` | Remove a lead from a campaign |

---

*Powered by [Composio](https://composio.dev)*

Intended uses

  • Use Lemlist Automation when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.