Lemlist

Run a workflow on Lemlist activity — a lead replies, a LinkedIn invite is accepted, an enrichment finishes, a campaign completes. Lemlist has a large, channel-organized event catalog; each activity becomes the workflow's input.

For behavior shared by every provider (the delivery URL, testing), see the webhook triggers reference.

Prerequisites

Lemlist webhooks are auto-registered: Cotera creates the hook for you over Lemlist's API. You supply a Lemlist API Key on the trigger's setup page (see Lemlist's webhook API docs). Without it, install fails with lemlist_credentials_missing.

Setup

1. Add a From an app trigger and pick Lemlist, and enter your Lemlist API key.
2. Choose a channel, then the event within it (see the catalog below).
3. Optionally set a campaign ID to scope the trigger to a single campaign. Leave it empty to receive the event across all campaigns.
4. Save. Cotera registers the hook with Lemlist for that activity type, pointed at the trigger's unique URL.

Deleting the trigger removes the hook from Lemlist. When a campaign is set, Lemlist filters server-side so the trigger only ever receives that campaign's deliveries.

Authentication

Lemlist doesn't sign deliveries or send a signature header. Instead, Cotera sets a shared secret when it creates the hook, and Lemlist echoes that secret inside the JSON body of every delivery. Cotera constant-time compares it against the trigger's secret and rejects anything that doesn't match. Cotera strips the secret field out before the payload reaches your workflow, so it never lands in a run input.

Payload

Each delivery is a Lemlist activity object, passed through as the workflow input (minus the stripped secret). The type field is the event key. An emailsOpened delivery looks like:

{
  "_id": "act_ExAmPlE0123456789",
  "type": "emailsOpened",
  "teamId": "tea_ExAmPlE0123456789",
  "createdAt": "2026-01-15T10:30:00.000Z",
  "campaignId": "cam_ExAmPlE0123456789",
  "campaignName": "Q1 Outbound",
  "sequenceId": "seq_ExAmPlE0123456789",
  "sequenceStep": 1,
  "leadId": "lea_ExAmPlE0123456789",
  "leadEmail": "jane@example.com",
  "leadFirstName": "Jane",
  "leadLastName": "Doe",
  "contactId": "ctc_ExAmPlE0123456789",
  "sendUserId": "usr_ExAmPlE0123456789",
  "sendUserName": "Alex Rep",
  "sendUserEmail": "alex@mycompany.com",
  "subject": "Quick question, Jane",
  "to": [{ "address": "jane@example.com", "name": "Jane Doe" }],
  "cc": [],
  "bcc": []
}

Event catalog

Pick a channel, then an event. The event key is Lemlist's activity type — the same string that appears in the delivery's type field.

Lead journey

Aggregate lead-state events that span channels — Lemlist's engagement funnel.

Email

Unsubscribe

LinkedIn

Other channels

The remaining channels follow the same sent → delivered → opened → replied → failed shape as email, plus per-channel and workspace events. Every key below is a valid activity type.