lemlist

Manage Lemlist campaigns, leads, and sequences via Robomotion CLI.

2|1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/robomotionio/robomotion-skills --skill lemlist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lemlist
Source: https://github.com/robomotionio/robomotion-skills/tree/main/skills/lemlist
Command: npx skills add https://github.com/robomotionio/robomotion-skills --skill lemlist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lemlist outreach management is automated to streamline campaigns, leads, and email sequences using Robomotion.

Core Features & Use Cases

  • List campaigns and view campaign details
  • Add or remove leads from email campaigns
  • Manage lead data and outreach sequences

Quick Start

Install the Lemlist integration, connect a session, list campaigns, and disconnect, always using --output json.

Prerequisites

  • Robomotion CLI installed
  • Robomotion install lemlist
  • Lemlist API key configured via Robomotion vault

IMPORTANT: Session Mode

Each CLI operation runs as a separate process; connection IDs do not persist across calls. You must use --session on connect and pass --session-id to all subsequent commands.

Workflow

  1. Install (once): Robomotion install lemlist
  2. Connect with session: Robomotion lemlist lemlist_connect --session --output json
  3. Use the returned client-id and session-id in all subsequent commands: Robomotion lemlist lemlist_list_campaigns --client-id "<client-id>" --session-id "<session-id>" --output json
  4. Disconnect when done: Robomotion lemlist lemlist_disconnect --client-id "<client-id>" --session-id "<session-id>" --output json

Always append --output json to get structured JSON results.

Commands Reference

  • lemlist connect --session --output json
  • lemlist disconnect --client-id --session-id "<session-id>" --output json
  • lemlist get_team --client-id [--user-url] --session-id "<session-id>" --output json
  • lemlist list_campaigns --client-id [--0] [--100] --session-id "<session-id>" --output json
  • lemlist unsubscribe_lead_from_campaign --client-id [--campaign-id] [--email-address] --session-id "<session-id>" --output json
  • lemlist remove_lead_from_campaign --client-id [--campaign-id] [--email-address] --session-id "<session-id>" --output json

Environment

  • ROBOMOTION_API_TOKEN (if vault credentials are needed)

Frequently Asked Questions about lemlist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Lemlist email outreach campaign management?

To automate Lemlist email outreach, use the Robomotion CLI to connect a session, list campaigns, and manage leads. You must install the integration, configure your Lemlist API key in the vault, and append --output json to commands for structured results.

What do I need to set up before managing Lemlist leads via CLI?

Before managing Lemlist leads via CLI, you need the Robomotion CLI installed, the Lemlist package added via 'Robomotion install lemlist', and your Lemlist API key configured in the Robomotion vault. An API token may also be required for vault access.

How does session management work for Lemlist CLI operations?

Each CLI operation runs as a separate process, so connection IDs do not persist. You must use '--session' on connect, then pass the returned '--client-id' and '--session-id' to all subsequent commands, and finally disconnect when operations are complete.

Can I remove or unsubscribe leads from Lemlist campaigns in bulk?

You can remove or unsubscribe leads from Lemlist campaigns using specific CLI commands. The operations require the campaign ID and the lead's email address, along with your active session ID, and return JSON formatted results confirming the action.

Why does my Robomotion Lemlist integration lose connection between commands?

Your Lemlist integration loses connection because each CLI operation runs as a separate process without persisting connection IDs. You must pass the '--client-id' and '--session-id' parameters returned from your initial connect command to every subsequent command.