Connect a Lemlist team with an API key and sync campaigns, contacts, companies, and outreach activities into your warehouse.
Lemlist is an in progress connector undergoing end-to-end validation. It is listed separately from released ingestion sources.
Connect Lemlist as a warehouse source using a dedicated API key from Settings → Integrations → Generate a new API key. You need an Embrasure workspace administrator and Lemlist API access to all four supported resources.
For validation, use the Lemlist setup link and paste the key. Embrasure verifies the team and reads one record from each supported endpoint. Select the tables you need and start the sync. The key is stored encrypted and used only for read requests.
| Table | Contents | How it updates |
|---|---|---|
lemlist.campaigns | Campaign names, status, creation time, creator, and sequence IDs | Full paginated rescan each sync |
lemlist.contacts | Saved contacts, email, owner, custom fields, and campaign membership | Full paginated rescan each sync |
lemlist.companies | Saved companies, domains, industry, owner, and custom fields | Full paginated rescan each sync |
lemlist.activities | Outreach events such as sends, opens, replies, bounces, and unsubscribes | Initial history read, then date-window reads with a five-minute overlap |
Each table uses the Lemlist _id as its warehouse id. Common fields remain queryable columns, and data preserves the complete record returned by Lemlist. Contact campaign membership is available in data.campaigns. The generated sync_cursor records the scan time, not a provider modification time.
Activities use a fixed upper date while paging. The next checkpoint advances only after every page in that window has completed. Overlapping activity reads and retries merge by ID. Late activities older than the five-minute overlap and later edits to historical activities require a full resync.
Other tables rescan because their list endpoints do not document a modification-time filter. These offset-based reads are not a point-in-time snapshot; concurrent source changes can move rows between pages. Subsequent scans reconcile current records. Deleted records remain until Actions → Full resync successfully replaces the destination tables. A contact's unsubscribe flag remains in data.
Lemlist allows 20 requests per two seconds per API key. Embrasure shares rate-limit cooldowns across workers using that key and honors Retry-After. Each batch reads at most 100 records; scans stop with an explicit error after 10,000 pages or a response larger than 10 MB, preserving the last committed checkpoint.
The connector does not call enrichment, prospect search, sending, or source mutation endpoints. Campaign statistics, campaign-lead exports, inbox messages, tasks, webhooks, and other resources are outside this initial connector. The campaign-leads list has a documented maximum of 500 rows without pagination, so it is not exposed as a complete warehouse table.
See Lemlist's authentication guide, API specification, and activity API.
Apollo
Connect an Apollo workspace with one API key and sync its CRM records, outreach emails, calls, users, tasks, sequences, and stages without using enrichment credits.
PostHog
Connect one PostHog Cloud project with scoped OAuth, choose the history window and modules, and verify every warehouse table.