Lemlist Automation
by ComposioHQLemlist Automation helps AI assistants run Lemlist outreach workflows via Composio MCP: list campaigns, inspect setup, enroll leads, manage variables, export data, and handle unsubscribes.
This skill scores 72/100, which means it is acceptable for directory listing but should be presented as a lightweight MCP workflow guide rather than a fully packaged automation module. Directory users get enough concrete tool names, setup context, and workflow framing to decide whether it fits Lemlist outreach operations, though adoption still requires some comfort with Composio/Rube MCP and Lemlist API behavior.
- Clear, triggerable scope for Lemlist outreach automation, including campaign discovery, campaign validation, lead enrollment, personalization variables, exports, and unsubscribe cleanup.
- Provides concrete Composio tool names and input schemas, such as LEMLIST_GET_LIST_CAMPAIGNS with status, limit, offset, sortBy, and sortOrder parameters.
- Includes operational cautions such as extracting campaigns from a wrapped response and validating campaign configuration before write operations.
- Setup is minimal: it only points users to the Rube MCP endpoint and Lemlist API-key connection, with no repository-specific install command or verification steps.
- The skill appears to be a single SKILL.md with no supporting scripts, examples, references, or tests, so users must rely on the documented tool calls and linked Composio toolkit docs for deeper behavior.
Overview of Lemlist Automation skill
What Lemlist Automation does
Lemlist Automation is a Composio MCP-based skill for operating Lemlist outreach workflows from an AI assistant. It helps an agent list campaigns, inspect campaign setup, enroll leads, add personalization variables, export campaign data, and process unsubscribes without manually navigating the Lemlist UI for every step.
Best fit for sales outreach operators
This Lemlist Automation skill is most useful for sales, growth, RevOps, and founder-led outbound teams that already use Lemlist and want a controlled assistant workflow for routine campaign operations. It is especially relevant for Lemlist Automation for Sales Outreach when the work involves campaign hygiene, lead enrollment, personalization fields, and campaign data review.
Key differentiators and adoption notes
The skill is not just a generic “write my outbound email” prompt. It maps assistant actions to specific Lemlist tools through the Composio rube MCP server, including LEMLIST_GET_LIST_CAMPAIGNS and LEMLIST_GET_CAMPAIGN_BY_ID. The main adoption requirement is tool access: your client must connect to https://rube.app/mcp, and your Lemlist account must authenticate through Composio.
What to check before installing
Before using Lemlist Automation, confirm that you are comfortable giving an assistant operational access to outreach data. The upstream skill is contained in a single SKILL.md, so installation is lightweight, but there are no extra scripts, policy files, or validation helpers. Teams with strict approval flows should add their own review steps before lead enrollment or unsubscribe handling.
How to Use Lemlist Automation skill
Lemlist Automation install and MCP setup
For directory-based installation, use the repository skill path:
npx skills add ComposioHQ/awesome-claude-skills --skill "Lemlist Automation"
Then configure the Composio MCP server in your AI client:
https://rube.app/mcp
When prompted, connect your Lemlist account using API key authentication. The skill declares a dependency on the rube MCP server, so it will not be useful in a plain chat environment without MCP tool calling enabled.
Read these files first
Start with:
composio-skills/lemlist-automation/SKILL.md
That file contains the full workflow guidance and tool names. There are no companion README.md, rules/, resources/, references/, or scripts/ folders in the current skill directory, so users should treat SKILL.md as the source of truth and supplement it with the Composio Lemlist toolkit docs when needed.
Inputs that make the skill work well
A strong Lemlist Automation usage prompt should include the business goal, target campaign status or campaign ID, whether the assistant is allowed to write data, and any safety limits. For example:
“Use Lemlist Automation to find all running campaigns, identify the campaign named Q1 SaaS CFO outreach, inspect its configuration, and prepare a lead enrollment plan. Do not enroll leads yet. Return the campaign ID, required custom variables, and any missing fields I need to provide.”
This is better than “add leads to Lemlist” because it gives the assistant a discovery path, a target object, and a no-write boundary.
Practical workflow for safer execution
Use a staged workflow:
- List campaigns with
LEMLIST_GET_LIST_CAMPAIGNS, filtering by status such asrunning,draft,paused, orended. - Extract campaigns from the
campaignskey if the response is wrapped as{campaigns: [...], pagination: {...}}. - Validate the chosen campaign with
LEMLIST_GET_CAMPAIGN_BY_ID. - Ask the assistant to summarize required personalization variables before enrollment.
- Approve write actions only after reviewing campaign ID, lead count, variables, and unsubscribe handling.
This pattern reduces mistakes caused by wrong campaign selection, incomplete personalization fields, or accidental updates to archived or paused campaigns.
Lemlist Automation skill FAQ
Is Lemlist Automation only for technical users?
No, but it assumes you can connect an MCP server and authenticate Lemlist through Composio. Non-technical users can operate the workflow after setup, but an admin or technical teammate may be needed for the initial Lemlist Automation install and account connection.
How is this better than an ordinary prompt?
An ordinary prompt can draft outreach copy or suggest campaign strategy, but it cannot reliably call Lemlist operations. This skill gives the assistant tool-level actions for campaign discovery, campaign inspection, lead enrollment, variable handling, exports, and unsubscribes through the Composio integration.
When should I not use this skill?
Do not use it as an uncontrolled bulk-action agent. If your lead data is unverified, consent rules are unclear, unsubscribe logic is sensitive, or campaign ownership is ambiguous, first run the skill in read-only discovery mode. It is also a poor fit if you do not use Lemlist or cannot enable the Composio rube MCP server.
Does it write email copy too?
The skill is mainly operational automation for Lemlist workflows. You can ask your assistant to draft personalization or review variables, but the repository evidence centers on campaign management and data operations rather than a complete copywriting framework.
How to Improve Lemlist Automation skill
Improve Lemlist Automation prompts with guardrails
The best results come from prompts that define permissions. Say whether the assistant may only inspect, may prepare a CSV-style plan, or may execute changes. Include limits such as “max 25 leads,” “running campaigns only,” “do not modify archived campaigns,” or “ask before handling unsubscribes.” These constraints matter more than extra prose.
Provide cleaner campaign and lead context
Give exact campaign names, campaign IDs when known, lead fields, and personalization variables. If you are enrolling leads, include the required custom variable names expected by your Lemlist sequence. Poor inputs usually lead to failed writes, generic personalization, or extra back-and-forth.
Watch for common failure modes
The most important repository-specific pitfall is response shape: campaign list results may be wrapped under campaigns with pagination metadata. Ask the assistant to handle pagination and confirm extracted campaign IDs before taking action. Also require a campaign detail check before any write operation, because campaign names alone can be ambiguous.
Iterate after the first output
After the first run, ask for a concise operations report: campaign used, filters applied, records found, records changed, skipped leads, missing variables, and recommended next step. This turns Lemlist Automation from a one-off command into a repeatable outreach operations workflow that your team can audit and improve.