Lemlist Automation

Lemlist Automation — Lemlist Multi-Channel Outreach Automation Tool

Skill Overview

Lemlist Automation integrates with Composio MCP to help you automatically manage Lemlist marketing campaigns and leads, including bulk lead imports, adding personalized variables, exporting campaign data, and handling unsubscribes. It’s suitable for B2B sales teams and marketers to improve outreach efficiency.

Use Cases

1. Bulk Import of Large Numbers of Leads

When you need to quickly import hundreds or thousands of leads into Lemlist marketing campaigns, you can use LEMLIST_POST_CREATE_LEAD_IN_CAMPAIGN to register leads in bulk. You may optionally enable email lookup, phone number completion, and LinkedIn enrichment. It’s recommended to process in batches (about 50 leads per batch) and set checkpoints between batches to avoid partial failures causing data loss.

2. Bulk Enrichment with Personalized Variables

After importing leads, you may need to add custom fields (e.g., customer rating, industry tags, product preferences) to achieve highly personalized email content. Use LEMLIST_POST_ADD_VARIABLES_TO_LEAD to add personalized variables to leads. Note that this operation does not support upsert; existing variables cannot be overwritten using this tool.

3. Export and Analysis of Campaign Lead Data

When you need to regularly export the lead status from marketing campaigns for reporting or quality checks, use LEMLIST_GET_EXPORT_CAMPAIGNS_LEADS to export lead data. It supports filtering by status and outputting in JSON/CSV formats, making it easy to integrate into data analysis workflows.

Core Features

1. Campaign Management and Query

Use LEMLIST_GET_LIST_CAMPAIGNS to enumerate all marketing campaigns. It supports filtering by status (running, draft, archived, etc.) and pagination queries. Use LEMLIST_GET_CAMPAIGN_BY_ID to retrieve detailed configuration information for a single marketing campaign, which helps verify campaign settings before performing write operations.

2. Bulk Lead Import and Deduplication Control

Use LEMLIST_POST_CREATE_LEAD_IN_CAMPAIGN to create and register leads into a marketing campaign. It supports providing rich fields such as name, company, title, and LinkedIn, and allows you to configure whether cross-campaign deduplication should be enabled (deduplicate parameter). Note that when deduplication is enabled, if a lead already exists in another campaign, the system returns an HTTP 500 error. If you need to register leads across campaigns, disable this option.

3. Lead Data Enrichment and Export

Use LEMLIST_POST_ADD_VARIABLES_TO_LEAD to add custom personalized variables to leads. You must use the internal leadId (not an email address). Use LEMLIST_GET_EXPORT_CAMPAIGNS_LEADS to export campaign lead data for reporting or analysis. Use LEMLIST_DELETE_UNSUBSCRIBE_LEAD_FROM_CAMPAIGN to handle unsubscribe requests.

Common Questions

How do I bulk import leads into a Lemlist marketing campaign?

Use the LEMLIST_POST_CREATE_LEAD_IN_CAMPAIGN tool, providing the required campaignId and email parameters, plus optional fields such as firstName, lastName, and companyName. It’s recommended to process leads in batches (about 50 per batch), and set checkpoints between batches to save progress and avoid losing partial data due to intermittent failures.

How can I avoid the “Lead already in other campaign” error when registering leads across multiple marketing campaigns?

This error occurs when deduplicate is enabled and the system detects that the lead already exists in another marketing campaign. If you need to register the same lead across multiple campaigns (e.g., different marketing sequences), call LEMLIST_POST_CREATE_LEAD_IN_CAMPAIGN with deduplicate set to false to disable the cross-campaign deduplication check.

Why do I get the “Variables already exist” error when adding personalized variables?

LEMLIST_POST_ADD_VARIABLES_TO_LEAD is not an upsert operation. If you try to add a variable key name that already exists, the system returns an HTTP 400 error. If you need to update an existing variable, first check whether the lead already has that variable and avoid adding the same key name again. Also, make sure you use the correct internal leadId (Lemlist lead ID), not an email address. You can resolve the internal leadId from an email address first using LEMLIST_GET_RETRIEVE_LEAD_BY_EMAIL.