Skip to main content
In the screenshot below, we only configured Zapier webhooks. Once configured, Lemlist will send specified events data to the webhook of the corresponding Zapier ID (hidden in below screenshot).
Webhook screenshot from the lemlist app interface

Webhook screenshot from the lemlist app interface

Webhooks send real-time HTTP notifications upon campaign events (opens, clicks, replies, etc.).

​
_id
string

Unique webhook identifier

​
targetUrl
string<uri>

Destination URL for event notifications

​
type
enum<string>

Event type to listen for

Available options:
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,
campaignComplete,
annotated,
enrichmentDone,
enrichmentError,
callRecordingDone,
callTranscriptDone
​
campaignId
string

The ID of the campaign the webhook is associated with (if any)

​
createdAt
string<date-time>

Creation timestamp

​
zapId
integer

Zapier integration ID (if the destination is a Zapier webhook)