Lemlist Trigger

Triggers on Lemlist outreach events such as email opens, clicks, replies, and LinkedIn interactions

Overview

Receives webhook notifications from Lemlist when email outreach and sales engagement events occur. Supports over 40 event types including email sends, opens, clicks, replies, bounces, unsubscribes, LinkedIn interactions (visits, invites, replies, voice notes), Aircall events, API actions, and campaign lifecycle events (paused, resumed, connection issues). Can filter by specific campaign and first-occurrence only. Useful for automating follow-ups based on prospect engagement, syncing lead activity to CRMs, triggering alerts on delivery failures, and building multi-channel outreach workflows.

Category: Marketing
Tool Name: lemlist_trigger
Version: 1

Appearance: Icon: lucide-Mail | Color: #4c5dff

Node Type

Trigger — webhook (receives incoming HTTP callbacks)

Input / Output

Direction	Port(s)
Input	None (trigger node)
Output	Output

Credentials

This tool requires Lemlist credentials. See the Credentials Guide for setup instructions.

Parameters

Parameter	Type	Required	Default	Description
Event	options	Yes	—	Which Lemlist event to listen for. Select * to receive all event types.
				Options: * (All Events), contacted, hooked, attracted, warmed, interested, skipped, notInterested, emailsSent, emailsOpened, emailsClicked, emailsReplied, emailsBounced, emailsSendFailed, emailsFailed, emailsUnsubscribed, emailsInterested, emailsNotInterested, opportunitiesDone, aircallCreated, aircallEnded, aircallDone, aircallInterested, aircallNotInterested, apiDone, apiInterested, apiNotInterested, apiFailed, linkedinVisitDone, linkedinVisitFailed, linkedinInviteDone, linkedinInviteFailed, linkedinInviteAccepted, linkedinReplied, linkedinSent, linkedinVoiceNoteDone, linkedinVoiceNoteFailed, linkedinInterested, linkedinNotInterested, linkedinSendFailed, manualInterested, manualNotInterested, paused, resumed, customDomainErrors, connectionIssue, sendLimitReached, lemwarmPaused
Options	collection	No	{}	Additional configuration options for filtering webhook events.
— Campaign ID	string	No	—	Only trigger this webhook for the specified campaign. Leave empty to receive events from all campaigns.
— Is First	boolean	No	false	Whether to call this webhook only the first time this activity happens for a given lead.

Output Data

Each delivery produces one output item. The Lemlist payload is placed directly on the item alongside three metadata fields:

{
  "_trigger": "lemlist_webhook",
  "_timestamp": "2026-01-01T00:00:00.000Z",
  "_webhookEvent": "emailsOpened",
  "type": "emailsOpened",
  "campaignId": "cam_abc123def456",
  "campaignName": "Test Campaign",
  "leadId": "lea_abc123def456",
  "sequenceId": 1,
  "sequenceStep": 1,
  "email": "prospect@example.com",
  "firstName": "John",
  "lastName": "Doe",
  "companyName": "Example Corp",
  "sendDate": "2026-01-01T00:00:00.000Z",
  "openDate": "2026-01-01T00:00:00.000Z",
  "isFirst": true
}

• _trigger — always lemlist_webhook.
• _timestamp — ISO 8601 timestamp of when the delivery arrived.
• _webhookEvent — the event name, copied from the payload’s type field, or unknown when it is absent.
• The remaining fields come straight from Lemlist and vary by event: lead identity (leadId, email, firstName, lastName, companyName), campaign context (campaignId, campaignName, sequenceId, sequenceStep) and event-specific timestamps such as sendDate and openDate. isFirst marks the first occurrence of that activity for the lead.

Reference values downstream by expression, for example {{ $json.email }} or {{ $json.campaignName }}.

Usage Examples

• Start a workflow when a prospect opens an outreach email in Lemlist
• Trigger a CRM update when a lead replies to a Lemlist campaign email
• Send a Slack alert when an email bounces in a Lemlist sequence
• Automate follow-up tasks when a LinkedIn invite is accepted via Lemlist
• Log unsubscribe events from Lemlist campaigns to a spreadsheet

Example Configuration

Fire on every email open:

{
  "type": "lemlist_trigger",
  "parameters": {
    "event": "emailsOpened"
  }
}

Fire on replies within one campaign:

{
  "type": "lemlist_trigger",
  "parameters": {
    "event": "emailsReplied",
    "options": {
      "campaignId": "cam_abc123def456",
      "isFirst": false
    }
  }
}

Fire only the first time a lead accepts a LinkedIn invite:

{
  "type": "lemlist_trigger",
  "parameters": {
    "event": "linkedinInviteAccepted",
    "options": {
      "isFirst": true
    }
  }
}

Qualify interested leads from one campaign, once per lead:

{
  "type": "lemlist_trigger",
  "parameters": {
    "event": "emailsInterested",
    "options": {
      "campaignId": "cam_qualification001",
      "isFirst": true
    }
  }
}

Watch for connection issues and send failures:

{
  "type": "lemlist_trigger",
  "parameters": {
    "event": "connectionIssue"
  }
}

Receive every Lemlist event:

{
  "type": "lemlist_trigger",
  "parameters": {
    "event": "*"
  }
}

Trigger Behavior

• Activation: When the workflow is activated, a webhook endpoint is registered with the service.
• Deactivation: The webhook is automatically unregistered when the workflow is deactivated.
• Payload: The incoming webhook payload is parsed and output as workflow items.
• Verification: Supports signature verification where applicable.

Tips

Entry point that fires when Lemlist sends a webhook for subscribed outreach events. Select which event type to listen for (or use * for all events). Optionally scope to a specific campaign and filter to first-occurrence only. The webhook payload contains lead and activity details from Lemlist.