> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enrow.io/llms.txt
> Use this file to discover all available pages before exploring further.

# lemlist Integration

> Push verified contacts from Enrow straight into your lemlist campaigns

## Overview

The lemlist integration lets you push contacts from your Enrow lists directly into a lemlist campaign — with verified emails, phone numbers, and personalization data mapped to your campaign's custom variables. No CSV exports, no re-verification.

<Info>
  Emails found by Enrow are **already verified** — you don't need lemlist's email verification add-on for leads pushed from Enrow.
</Info>

## Setup

<Steps>
  <Step title="Get your lemlist API key">
    In [lemlist](https://app.lemlist.com/settings/integrations), go to **Settings → Integrations** and generate an API key. Keys are team-scoped — any key from your team works.
  </Step>

  <Step title="Connect lemlist in Enrow">
    In the [Enrow Dashboard](https://app.enrow.io), go to **Integrations** in the left menu, click **lemlist**, and paste your API key. Enrow validates the key against lemlist before saving it.

    <Info>
      On a team account, only **team admins** connect the integration — every team member can then push contacts through the shared connection.
    </Info>
  </Step>

  <Step title="Configure (optional)">
    Pushing works out of the box with a sensible default mapping. From the integration page you can also set:

    * **Default campaign** — where pushes land when you don't pick a campaign explicitly
    * **Field mapping** — which Enrow fields feed which lemlist fields and custom variables
    * **Push options** — how duplicates across campaigns are handled
  </Step>
</Steps>

## Pushing contacts

From any Enrow list, push a single contact (contact row → lemlist icon) or select multiple rows and use the bulk **Push** action. Pick the destination campaign (your default is preselected) and confirm.

* The destination picker shows each campaign's **status** (paused, draft…) so you never push into a campaign that isn't sending, plus a green **“Already pushed”** badge on campaigns the contact was already sent to.
* Contacts **must have an email** — rows without a found email are skipped and reported.
* After each push you get the counts of added, duplicate, and skipped contacts, and every push shows up in the integration's **History** tab.

<Note>
  lemlist ingests leads one at a time and rate-limits its API, so large bulk pushes are automatically paced by Enrow — a big selection simply takes a little longer.
</Note>

## Field mapping

Default mapping (editable from the integration page):

| Enrow field  | lemlist field                |
| ------------ | ---------------------------- |
| Email        | `email`                      |
| First name   | `firstName`                  |
| Last name    | `lastName`                   |
| Company name | `companyName`                |
| Phone        | `phone`                      |
| LinkedIn URL | `linkedinUrl`                |
| Headline     | `jobTitle`                   |
| Location     | `location` (custom variable) |

Custom variables are created automatically on each lead when you push — nothing to set up in lemlist. Use them in your sequences as `{{location}}` etc.

## Push options

| Option                                 | Default | Effect                                                                                                                            |
| -------------------------------------- | ------- | --------------------------------------------------------------------------------------------------------------------------------- |
| Skip leads already in another campaign | On      | A contact whose email already exists in another lemlist campaign is skipped, so the same person is never in two sequences at once |

Turn it off from the integration page if you deliberately want the same contact in several campaigns.

## Need Help?

* **Enrow Support**: [api@enrow.io](mailto:api@enrow.io)