Lemlist

Last updated on Jul 03, 2025

Lemlist is a sales engagement platform that accelerates and optimizes every interaction throughout the sales process. It is used to personalize emails on a large scale to increase your cold email outreach, automate follow-ups with your prospects, and keep campaign related emails out of the spam folder of the prospects. So, you can engage your prospects at the right time across the right channels.

You can replicate the data from your Lemlist account to a Destination database or data warehouse using Hevo Pipelines. Hevo ingests the data objects in Full Load mode. Refer to section, Data Model for the list of supported objects.

Lemlist uses an API key to identify Hevo and authorize the request for accessing account data.

Setup

Data Sync

Prerequisites

An active Lemlist account from which data is to be ingested exists.
The API key is available to authenticate Hevo on your Lemlist account.
You are logged in as a user with Admin access to obtain the API key. Else, you can obtain it from your account administrator.
You are assigned the Team Administrator, Team Collaborator, or Pipeline Administrator role in Hevo to create the Pipeline.

Obtaining the API Key

The API keys you generate in Lemlist do not expire. Therefore, you can use an existing key or create a new one to authenticate Hevo on your Lemlist account.

Note: You must log in as a user with Admin access to perform these steps.

To retrieve the API key:

Log in to your Lemlist account.
In the bottom left corner of the page, click your profile name and then click Settings.
In the left navigation pane, click Integrations, and then click Generate to generate a new API key.
(Optional) In the dialog box, specify a unique Name for the API key.
Click Create Key.
Click Copy to copy the API key and save it securely like any other password. Use this key while configuring your Hevo Pipeline.

Configuring Lemlist as a Source

Perform the following steps to configure Lemlist as the Source in your Pipeline:

Click PIPELINES in the Navigation Bar.
Click + CREATE PIPELINE in the Pipelines List View.
In the Select Source Type page, select Lemlist.
In the Configure your Lemlist Source page, specify the following:
- Pipeline Name: A unique name for the Pipeline, not exceeding 255 characters.
- API Key: The API key that you generated in your Lemlist account.
Click TEST & CONTINUE.
Proceed to configuring the data ingestion and setting up the Destination.

Data Replication

For Teams Created	Default Ingestion Frequency	Minimum Ingestion Frequency	Maximum Ingestion Frequency	Custom Frequency Range (in Hrs)
Before Release 2.21	1 Hr	1 Hr	24 Hrs	1-24
After Release 2.21	6 Hrs	30 Mins	24 Hrs	1-24

Note: The custom frequency must be set in hours as an integer value. For example, 1, 2, or 3, but not 1.5 or 1.75.

Hevo ingests all the objects in Full Load mode in each run of the Pipeline.

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination database:

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

Object	Description
Activities	Contains the details of last 100 activities associated with a campaign. For example, emails sent, emails opened, emails clicked, and emails replied to.
Campaigns	Contains the details of all marketing campaigns created and running in your Lemlist account. Campaigns are the marketing messages used for attracting customers.
Team	Contains the details of the different group of users in your Lemlist account.
Unsubscribes	Contains the details of the users who have unsubscribed from your campaign.

Additional Information

Read the detailed Hevo documentation for the following related topics:

Source Considerations

Rate Limit: Lemlist imposes a limit of 20 API calls per two seconds per API key. If the limit is exceeded, Hevo defers the ingestion till the limits reset. Read Rate Limit.

Limitations

Hevo currently does not support deletes. Therefore, any data deleted in the Source may continue to exist in the Destination.
The data is loaded in Full Load mode in each Pipeline run. As a result, you cannot load the historical data alone at any time.
Hevo does not load data from a column into the Destination table if its size exceeds 16 MB, and skips the Event if it exceeds 40 MB. If the Event contains a column larger than 16 MB, Hevo attempts to load the Event after dropping that column’s data. However, if the Event size still exceeds 40 MB, then the Event is also dropped. As a result, you may see discrepancies between your Source and Destination data. To avoid such a scenario, ensure that each Event contains less than 40 MB of data.

Revision History

Refer to the following table for the list of key updates made to this page:

Date	Release	Description of Change
Jul-07-2025	NA	Updated the Limitations section to inform about the max record and column size in an Event.	lumn size in an Event.
Jan-07-2025	NA	Updated the Limitations section to add information on Event size.
Dec-02-2024	NA	Updated section, Obtaining the API Key as per the latest Lemlist UI.
Mar-05-2024	2.21	Updated the ingestion frequency table in the Data Replication section.
Sep-14-2023	NA	Updated the section, Obtaining the API Key as per the latest Lemlist UI.
Nov-08-2022	2.01	New document.