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

# Lemlist

> This page outlines how to use the Lemlist integration for sales outreach and email campaigns in Cargo.

Lemlist is a sales engagement platform that helps teams send personalized cold emails at scale with automated follow-ups and advanced personalization. Cargo's native integration with Lemlist allows you to manage leads, campaigns, and email activities directly from your workflows.

## How to set up Lemlist

To connect Lemlist, you'll need an API key from your Lemlist account.

### Connection details

| Field       | Description          |
| ----------- | -------------------- |
| **API Key** | Your Lemlist API key |

<Tip>Find your API key in Lemlist under **Settings → Integrations → API**.</Tip>

Once the connector is created, you can:

* **Set up Lemlist data models** — Create data models from your Lemlist leads and activities to trigger Plays.
* **Use Lemlist in workflows** — Choose **Lemlist** from the node catalog within a **Play**, **Tool**, or **Agent**.

***

## Lemlist actions

### Create Lead

Create a new lead in a Lemlist campaign.

**Use cases**

* **Campaign enrollment** – Add qualified leads to outreach campaigns
* **List building** – Push leads from various sources to Lemlist
* **Multi-channel sequences** – Enroll leads in email sequences

**Configuration**

| Field        | Description                               |
| ------------ | ----------------------------------------- |
| **Campaign** | Select the campaign to add the lead to    |
| **Email**    | The lead's email address                  |
| **Mappings** | Map additional lead attributes            |
| **Options**  | Additional processing options (see below) |

**Available options**

| Option                  | Description                                    |
| ----------------------- | ---------------------------------------------- |
| **Deduplicate**         | Check if email exists in other campaigns first |
| **Find email**          | Use Lemlist to find verified email             |
| **LinkedIn enrichment** | Run LinkedIn enrichment on the lead            |
| **Verify email**        | Verify the existing email address              |

<Info>
  When creating leads with the **Deduplicate** option, Lemlist will check all
  campaigns to prevent adding the same email twice.
</Info>

### Update Lead

Update an existing lead in a campaign.

**Use cases**

* **Data enrichment** – Update leads with enriched data
* **Status updates** – Update lead information based on external events
* **Field updates** – Sync lead data from other systems

**Configuration**

| Field        | Description                             |
| ------------ | --------------------------------------- |
| **Campaign** | Select the campaign containing the lead |
| **Email**    | The lead's email address to match       |
| **Mappings** | Map lead attributes to update           |

### Upsert Lead

Create a new lead or update an existing one.

**Use cases**

* **Data sync** – Sync leads from your CRM without duplicates
* **Idempotent operations** – Safely retry lead creation
* **Continuous enrollment** – Keep leads updated as data changes

**Configuration**

| Field        | Description                |
| ------------ | -------------------------- |
| **Campaign** | Select the target campaign |
| **Email**    | The lead's email address   |
| **Mappings** | Map lead attributes        |

### Upsert Contact

Create or update a contact in the Lemlist CRM without enrolling them in a campaign.

**Use cases**

* **CRM sync** – Push enriched contacts into Lemlist before outreach
* **Data enrichment** – Update contact fields from external sources
* **Company linking** – Associate contacts with existing companies

**Configuration**

| Field                      | Description                                                         |
| -------------------------- | ------------------------------------------------------------------- |
| **Contact ID**             | Update an existing contact by ID (optional)                         |
| **Email**                  | Primary identifier for create/update (optional)                     |
| **LinkedIn URL**           | Alternative identifier (optional)                                   |
| **LinkedIn Sales Nav URL** | Alternative identifier (optional)                                   |
| **Contact owner**          | Team member to assign as owner (optional)                           |
| **Company ID**             | Link to an existing company by ID (optional)                        |
| **Company domain**         | Link to a company by domain (optional)                              |
| **Company LinkedIn URL**   | Link to a company by LinkedIn URL (optional)                        |
| **Mappings**               | Map additional contact attributes (e.g. firstName, lastName, phone) |

<Info>
  At least one of **Contact ID**, **Email**, **LinkedIn URL**, or **LinkedIn
  Sales Nav URL** is required. Contacts are separate from campaign leads — use
  **Create Lead** when you want to enroll someone in a sequence.
</Info>

### Upsert Company

Create or update a company in the Lemlist CRM.

**Use cases**

* **Account sync** – Keep company records up to date from your CRM or enrichment tools
* **Pre-outreach setup** – Create companies before syncing contacts

**Configuration**

| Field                      | Description                                                       |
| -------------------------- | ----------------------------------------------------------------- |
| **Company ID**             | Update an existing company by ID (optional)                       |
| **Name**                   | Company name (required when creating without Company ID)          |
| **Domain**                 | Company website domain (required when creating without ID)        |
| **LinkedIn URL**           | Alternative identifier (optional)                                 |
| **LinkedIn Sales Nav URL** | Alternative identifier (optional)                                 |
| **Company owner**          | Team member to assign as owner (optional)                         |
| **Mappings**               | Map additional company attributes (e.g. industry, location, size) |

### Get Contact

Retrieve contact information by ID or email.

**Use cases**

* **Contact lookup** – Fetch contact data for workflow conditions
* **Pre-upsert check** – Verify a contact exists before syncing

**Configuration**

| Field  | Description                 |
| ------ | --------------------------- |
| **ID** | Contact ID or email address |

### Get Company

Retrieve company information by ID or domain.

**Use cases**

* **Account lookup** – Fetch company data for workflow conditions
* **Pre-upsert check** – Verify a company exists before syncing

**Configuration**

| Field  | Description          |
| ------ | -------------------- |
| **ID** | Company ID or domain |

### Delete Lead

Remove a lead from a campaign.

**Use cases**

* **Campaign cleanup** – Remove invalid leads
* **Unsubscribe handling** – Remove leads who opted out
* **Lead management** – Remove leads that no longer qualify

**Configuration**

| Field        | Description                             |
| ------------ | --------------------------------------- |
| **Campaign** | Select the campaign containing the lead |
| **Email**    | The lead's email address to remove      |

### Get Lead

Retrieve lead information by ID or email.

**Use cases**

* **Lead lookup** – Fetch lead data for workflow conditions
* **Status check** – Check lead status before taking action

**Configuration**

| Field  | Description              |
| ------ | ------------------------ |
| **ID** | Lead ID or email address |

### Get Campaign

Retrieve campaign information by ID.

**Configuration**

| Field  | Description |
| ------ | ----------- |
| **ID** | Campaign ID |

### Unsubscribe Lead from Campaign

Remove a lead from a specific campaign's sequence.

**Use cases**

* **Opt-out handling** – Stop sequences for specific campaigns
* **Campaign management** – Remove leads from specific outreach

**Configuration**

| Field        | Description              |
| ------------ | ------------------------ |
| **Campaign** | Select the campaign      |
| **Email**    | The lead's email address |

### Add unsubscribe email

Add an email to the global unsubscribe list.

**Use cases**

* **Global opt-out** – Prevent all future emails to an address
* **GDPR compliance** – Honor unsubscribe requests

**Configuration**

| Field     | Description                      |
| --------- | -------------------------------- |
| **Email** | The email address to unsubscribe |

<Warning>
  Adding an email to the unsubscribe list will prevent it from receiving emails
  across all campaigns.
</Warning>

### Delete unsubscribe email

Remove an email from the global unsubscribe list.

**Use cases**

* **Re-subscription** – Allow a previously unsubscribed email to receive emails
* **Error correction** – Fix accidental unsubscribes

**Configuration**

| Field     | Description                                  |
| --------- | -------------------------------------------- |
| **Email** | The email address to remove from unsubscribe |

***

## Lemlist data models

Cargo allows you to create data models on top of your Lemlist data that can be used to trigger Plays and power workflows.

### Available extractors

<AccordionGroup>
  <Accordion title="Fetch leads" icon="users">
    Pull lead records from Lemlist with incremental sync support. **Use cases**

    * Build data models from your Lemlist leads - Trigger workflows when leads
      are added or updated - Sync lead data back to your CRM
  </Accordion>

  <Accordion title="Fetch campaigns" icon="paper-plane">
    Pull campaign records from Lemlist. **Use cases** - Track campaign status
    and settings - Monitor campaign performance
  </Accordion>

  <Accordion title="Fetch activities" icon="chart-line">
    Pull activity events from Lemlist including opens, clicks, and replies.
    **Use cases** - Track email engagement - Trigger workflows on email opens or
    replies - Monitor campaign performance
  </Accordion>

  <Accordion title="Fetch unsubscribes" icon="ban">
    Pull the global unsubscribe list. **Use cases** - Sync unsubscribes to other
    systems - Maintain compliance records
  </Accordion>
</AccordionGroup>