# Lemlist

## What It Does

Adds leads to a Lemlist email campaign for automated cold email outreach. Leads are deduplicated — if a lead is already in the campaign, it is silently skipped.

## Authentication

API Key. When adding Lemlist as a connection step in an automation, enter your Lemlist API key. During setup, you also select which campaign receives the leads.

## Data Sent to Lemlist

| Midbound Field                   | Lemlist Field    |
| -------------------------------- | ---------------- |
| Work email (fallback: personal)  | Email (required) |
| First name                       | First name       |
| Last name                        | Last name        |
| Company name                     | Company name     |
| Job title                        | Job title        |
| LinkedIn URL                     | LinkedIn URL     |
| Company domain (from work email) | Company domain   |
| Work phone (fallback: personal)  | Phone            |

## Key Behaviors

* **Email required** — Unlike HeyReach, Lemlist requires an email address. If no email is available, the action fails with an error.
* **Built-in deduplication** — Lemlist's API automatically checks for duplicates. If the lead already exists in the campaign, Midbound detects this and skips gracefully (no error).
* **Company domain extraction** — If a work email is present, the domain (e.g., "acme.com") is automatically extracted and sent as the company domain for Lemlist's personalization features.
* **Campaign selection** — During connection setup, you choose which Lemlist campaign receives the leads.

## Using with Workflows

1. Connect Lemlist and select your target campaign
2. Build a workflow triggered by audience entry or visitor identification
3. Leads with email addresses are added to the campaign automatically
4. Leads already in the campaign are skipped — no duplicates

## Related

* [Integrations Overview](/docs/integrations/overview.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://midbound.ai/docs/integrations/lemlist.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.