Lemlist is a cold-outreach and sales-engagement platform for running multichannel campaigns (email, LinkedIn, calls) and tracking how leads respond. This connector extracts your campaigns, the leads enrolled in them, the full activity funnel (sends, opens, clicks, replies, and more), team senders, unsubscribes, webhooks, and sending schedules.

Configuring Lemlist as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Lemlist option from the list of connectors. Click Next and you’ll be prompted to add your access.

1. Add account access

To connect Lemlist, you need:

API Key: Your Lemlist API key.

You can generate one in the Lemlist app under Settings > Integrations > API & Webhooks, then click Generate key. The key is shown only once, so copy it immediately. Once you’re done, click Next.

2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis:

Campaigns
Campaign Leads
Activities
Team
Team Senders
Unsubscribes
Hooks
Schedules

Select the streams and click Next.

3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.

Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
- Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
- Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.

The Activities stream supports incremental sync (based on each activity’s createdAt). All other streams are full table. Once you are done configuring, click Next.

4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated. Optionally, you can define some additional settings:

Start Date (optional): The earliest date to fetch activities from. Only activities on or after this date will be extracted on the first run.
Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.

Once you are ready, click Next to finalize the setup.

5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.

For you to be able to see it on your Catalog, you need at least one successful source run.

Streams and Fields

Below you’ll find all available data streams from Lemlist and their corresponding fields:

Campaigns

Outreach campaigns in your account, including status, the sending sequence, schedules, and senders. Full table sync.

Field	Type	Description
`_id`	string	Unique campaign identifier (primary key)
`name`	string	Campaign name
`status`	string	Campaign status (e.g. `running`, `paused`, `draft`, `ended`, `archived`, `errors`)
`labels`	array	Categorization labels
`sequenceId`	string	Identifier of the campaign’s message sequence
`scheduleIds`	array	Sending schedule identifiers used by the campaign
`teamId`	string	Owning team identifier
`createdBy`	string	User identifier of the creator
`createdAt`	datetime	Campaign creation timestamp
`hasError`	boolean	Whether the campaign currently has errors
`errors`	string	Campaign errors (JSON)
`creator`	object	Creator details (`userId`, `userEmail`)
`senders`	array	Sending mailboxes (`id`, `email`, `sendUserMailboxId`)

Campaign Leads

Full per-lead snapshot for each campaign, including contact details and the lead’s current state in the funnel. Child of Campaigns. Full table sync.

Field	Type	Description
`_id`	string	Unique lead identifier (primary key)
`email`	string	Lead email address
`emailStatus`	string	Email deliverability status (`deliverable`, `risky`, `undeliverable`)
`firstName`	string	Lead first name
`lastName`	string	Lead last name
`companyName`	string	Lead company name
`companyDomain`	string	Lead company domain
`jobTitle`	string	Lead job title
`phone`	string	Lead phone number
`linkedinUrl`	string	Lead LinkedIn profile URL
`picture`	string	Lead picture URL
`timezone`	string	Lead timezone
`icebreaker`	string	Personalized icebreaker text
`state`	string	Current lead state in the campaign
`stateSystem`	string	Internal system state
`lastState`	string	Previous lead state
`status`	string	Lead status
`campaign_id`	string	Identifier of the parent campaign

Activities

The activity funnel: every event performed for a lead in a campaign (emails sent/opened/clicked/replied/bounced/unsubscribed, LinkedIn actions, calls, and more). Supports incremental sync based on createdAt.

Field	Type	Description
`_id`	string	Unique activity identifier (primary key)
`type`	string	Activity type (e.g. `emailsSent`, `emailsOpened`, `emailsClicked`, `emailsReplied`, `emailsBounced`, `emailsUnsubscribed`, `linkedinSent`, …)
`leadId`	string	Lead the activity refers to
`campaignId`	string	Campaign the activity belongs to
`sequenceId`	string	Sequence identifier
`stepId`	string	Sequence step identifier
`sequenceStep`	integer	Zero-indexed position of the step in the sequence
`totalSequenceStep`	integer	Total number of steps in the sequence
`createdAt`	datetime	When the activity occurred (replication key)

Team

Your Lemlist team account (a single record). Full table sync.

Field	Type	Description
`_id`	string	Unique team identifier (primary key)
`name`	string	Team name
`userIds`	array	Identifiers of users in the team
`createdBy`	string	User identifier of the team creator
`createdAt`	datetime	Team creation timestamp
`creatorDomain`	string	Email domain of the team creator

Team Senders

Team members (senders) and the campaigns they participate in. Full table sync.

Field	Type	Description
`userId`	string	Sender user identifier (primary key)
`campaigns`	array	Campaigns the sender is involved in (`_id`, `name`, `status`, `sendingChannels`)

Unsubscribes

Unsubscribed email addresses and domains. Full table sync.

Field	Type	Description
`_id`	string	Unique unsubscribe identifier (primary key)
`email`	string	Unsubscribed email address
`campaignId`	string	Campaign the unsubscribe originated from
`campaignName`	string	Campaign name
`unsubscribedAt`	datetime	When the unsubscribe occurred
`scope`	string	Scope of the unsubscribe (`campaign`, `team`, or `global`)

Hooks

Webhooks configured for your team (configuration, not delivered events). Full table sync.

Field	Type	Description
`_id`	string	Unique webhook identifier (primary key)
`targetUrl`	string	Destination URL the webhook posts to
`type`	string	Event type the webhook listens for
`campaignId`	string	Campaign the webhook is scoped to, if any
`createdAt`	datetime	Webhook creation timestamp
`zapId`	integer	Associated Zapier identifier, if any

Schedules

Sending schedules that control when campaigns send. Full table sync.

Field	Type	Description
`_id`	string	Unique schedule identifier (primary key)
`name`	string	Schedule name
`secondsToWait`	integer	Delay between sends, in seconds
`timezone`	string	Schedule timezone
`start`	string	Daily start time (e.g. `09:00`)
`end`	string	Daily end time (e.g. `18:00`)
`weekdays`	array	Active weekdays (1=Monday … 7=Sunday)
`public`	boolean	Whether the schedule is shared across the team
`teamId`	string	Owning team identifier
`createdBy`	string	User identifier of the creator
`createdAt`	datetime	Schedule creation timestamp
`deletedAt`	datetime	Deletion timestamp, if deleted
`deletedBy`	string	User identifier who deleted the schedule

​Configuring Lemlist as a Source

​1. Add account access

​2. Select streams

​3. Configure data streams

​4. Configure data source

​5. Check your new source

​Streams and Fields

Configuring Lemlist as a Source

1. Add account access

2. Select streams

3. Configure data streams

4. Configure data source

5. Check your new source

Streams and Fields