Skip to main content

​
Prerequisites

Before continuing, you should have already completed the following for this connector:
1

Configure the Connector

Enable the connector and set up its connector profile in your project. See Managing Connectors.

Connector Profile

Lemlist - API Key
2

Link an Account

Connect an account using StackOne Hub or Auth Link.

Link Account

Lemlist - API Key

​
How webhooks are set up

Lemlist delivers events through a webhook subscription, and StackOne provisions it for you on connection — there is nothing to configure in Lemlist and no URL to paste. StackOne registers a single Lemlist webhook subscribed to all event types; only the events you enable in StackOne are dispatched onward. When you disconnect the account, StackOne removes the subscription automatically.

1

Connect with your API key

Authorize the connection with your Lemlist API key (Settings → Integrations → API & Webhooks → Generate key). StackOne uses it to create and delete the webhook subscription on your behalf — no further setup is needed in Lemlist.

2

Enable the events you need

Enable the Lemlist events you want in StackOne. The provisioned webhook already covers every event type; StackOne dispatches only the events you have enabled.

​
Delivery format & verification

Each delivery is a JSON body whose event type is in the type field. The record identifier is in _id for most events, data[0].id for enrichment events, and campaignId for campaign events. Lemlist sends no signature header; StackOne verifies deliveries via a shared secret echoed back in the payload and the per-account callback URL token, so no manual verification is required.

​
Available webhook events

The events below can be enabled for this connection.

1

Lead state events

Fired when a lead’s lifecycle or interest status changes in a sequence.

  • Contacted (contacted) — the lead was contacted.
  • Hooked (hooked) / Attracted (attracted) / Warmed (warmed) — engagement milestones.
  • Interested (interested) / Not Interested (notInterested) — interest status changed.
  • Paused (paused) / Resumed (resumed) — the lead was paused or resumed.
  • Stopped (stopped) / Skipped (skipped) — the lead was stopped or skipped.
2

Email events

Fired for email-channel activity (requires a connected sending mailbox).

  • Sent (emailsSent) / Opened (emailsOpened) / Clicked (emailsClicked) / Replied (emailsReplied).
  • Bounced (emailsBounced) / Failed (emailsFailed) / Send Failed (emailsSendFailed).
  • Unsubscribed (emailsUnsubscribed) / Interested (emailsInterested) / Not Interested (emailsNotInterested).
3

LinkedIn events

Fired for LinkedIn-channel activity (requires a connected LinkedIn account).

  • Sent (linkedinSent) / Opened (linkedinOpened) / Replied (linkedinReplied) / Send Failed (linkedinSendFailed).
  • Interested (linkedinInterested) / Not Interested (linkedinNotInterested).
  • Invite done/failed/accepted (linkedinInviteDone, linkedinInviteFailed, linkedinInviteAccepted).
  • Visit done/failed (linkedinVisitDone, linkedinVisitFailed).
  • Voice note, follow, endorse, like last post, withdraw invitation — done/failed/skipped variants.
4

WhatsApp & SMS events

Fired for WhatsApp and SMS channel activity (requires the respective channel connected).

  • WhatsApp (whatsappMessageSent, whatsappMessageDelivered, whatsappMessageOpened, whatsappReplied, whatsappMessageFailed).
  • SMS (smsSent, smsDelivered, smsReplied, smsFailed).
5

Call events

Fired for Aircall calls and call processing (requires Aircall connected).

  • Aircall created/ended/done/interested/not-interested (aircallCreated, aircallEnded, aircallDone, aircallInterested, aircallNotInterested).
  • Call recording / transcript done (callRecordingDone, callTranscriptDone).
6

API & manual events

Fired for API-step and manual actions on a lead.

  • API done/interested/not-interested/failed (apiDone, apiInterested, apiNotInterested, apiFailed).
  • Manual Interested (manualInterested) / Manual Not Interested (manualNotInterested).
  • Annotated (annotated) / Opportunities Done (opportunitiesDone).
7

Campaign, enrichment & system events

Fired for campaign completion, lead enrichment, and workspace-level system alerts.

  • Campaign Complete (campaignComplete) — a campaign finished processing all leads.
  • Enrichment done/error (enrichmentDone, enrichmentError).
  • System — custom-domain errors, connection issues, send-limit reached, lemwarm paused, inbox-label updated, signal registered, deliverability alert (customDomainErrors, connectionIssue, sendLimitReached, lemwarmPaused, inboxLabelUpdated, signalRegistered, deliverabilityAlertTriggered).

​
Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.