Lemlist

This connector uses the Lemlist API v1 (developer.lemlist.com).

Setup:

1. Sign in to Lemlist → top-right avatar → Settings → Integrations → API → Get my API key.
2. Copy the key. Set LEMLIST_API_KEY.

Authentication: HTTP Basic Auth — Authorization: Basic base64('':${LEMLIST_API_KEY}) — username is empty, password is the API key. (Yes, swapped from the usual: empty username, key as password.) The adapter handles this via BASIC_AUTH with username='' and password=key.

Campaign model: Lemlist's central unit. A campaign has a sequence of steps (email + waits + LinkedIn touches). You add leads (prospects) to a campaign — the campaign then drips touchpoints to each lead.

Lead state: a lead in a campaign has status (active/paused/replied/bounced/unsubscribed/completed). New leads default to active and start receiving the campaign's first step.

Custom variables: leads support arbitrary key/value pairs (e.g. {firstName:'Jane', icebreaker:'...'}) — referenced as {{firstName}} in the campaign emails. Lemlist's selling point is dynamic-personalization with image overlays driven by these variables.

Email accounts: each campaign sends from a connected email account (Gmail, Outlook, custom SMTP). Configured in UI; the API doesn't expose connection management.

Pagination: limit (default 100, max 100) + offset. Some endpoints return arrays without paging metadata — assume more if you get exactly limit items back.

Out of scope here: campaign creation (the step-builder is UI-only), team analytics, hook editing (configured via Lemlist's UI), Lemlist Chrome extension actions.