Skip to main content
Lemlist logo

Overview

Add Lemlist to any ModuleX agent or workflow. Manage sales-engagement outreach against the Lemlist REST API (api.lemlist.com): retrieve campaign activities and replies, look up lead details, and send emails through the Lemlist inbox.
Categories: Sales · Email Marketing · Sales Engagement · Auth: API Key · Actions: 3

Authentication

API Key Authentication

Authenticate using your Lemlist API key
1

Step 1

Sign in to Lemlist and open Settings -> Team Settings -> Integrations
2

Step 2

Generate an API key (it is shown only once — copy it immediately)
3

Step 3

Paste the API key below

Required Credentials

Available Actions

Parameters

string
Filter by activity type (e.g., emailOpened, emailClicked, emailReplied, paused)
string
Filter by campaign ID (e.g., “cam_abc123def456”)
string
Filter by lead ID (e.g., “lea_abc123def456”)
boolean
Filter for first activity only
integer
Number of results per request (max 100, default 100)
integer
Number of records to skip for pagination (e.g., 0, 100, 200)

Response

Parameters

string
required
Lead email address (e.g., “john@example.com”) or lead ID (e.g., “lea_abc123def456”)

Response

Parameters

string
required
Identifier for the user sending the message (e.g., “usr_abc123def456”)
string
required
Email address of the sender (e.g., “sales@company.com”)
string
required
Mailbox identifier for the sender (e.g., “mbx_abc123def456”)
string
required
Recipient contact identifier (e.g., “con_abc123def456”)
string
required
Associated lead identifier (e.g., “lea_abc123def456”)
string
required
Email subject line
string
required
Email message body in HTML format
array
Array of CC email addresses

Response

Limits & Quotas

  • Pagination: get_activities accepts limit (max 100, default 100) and offset for paging through campaign activity.
  • Send eligibility: send_email requires a configured Lemlist sender user, mailbox, and an existing contact/lead — the values come from your Lemlist workspace.
  • Error model: non-2xx responses and timeouts are caught and returned as success=False + error rather than raising. Plan for retries on the agent side based on the error string.

Enrow

Findymail

Icypeas