Resources · Zapier integration

lemlist Zapier integrationAutomate lemlist with Zapier.

The lemlist Zapier integration gives you 2 triggers, 16 actions and 1 search. One trigger reports every campaign activity the moment it happens; the actions add, enrich, verify, pause or unsubscribe leads from any other tool you use.

See the 19 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the lemlist Zapier integration does for an outbound team

It connects your lemlist account to Zapier, the tool that passes information between apps without anyone copying it. When something happens in a lemlist campaign, Zapier can carry it elsewhere. More often, it works the other way round: a form, a CRM or a spreadsheet drives lemlist, adding, enriching and stopping leads on its own.

Start with the detail that changes your setup. Of the two triggers, New Activity is the only instant one: lemlist warns Zapier itself, so it reacts straight away even on the free plan, while Unsubscribed Recipient waits for your plan's check interval. Build anything time-sensitive on the first one.

Three results come up most. Leads that arrive ready: Add Lead to Campaign drops a new contact into a sequence, with options to find a verified email or enrich from LinkedIn on the way. Sequences that stop on their own: Pause Lead From All or Specific Campaigns or Remove Lead From Campaign halts outreach once a deal moves elsewhere. Consent that stays in sync: Add Recipient to Unsubscribe List mirrors an opt-out collected in another tool.

What Zapier does not do here: there is no action to create or launch a campaign, and no trigger for a single type of event; New Activity covers them all and you sort them out yourself. The same app is covered in our lemlist n8n integration and lemlist Make integration pages.

Vocabulary

Zapier vocabulary in one minute

Eight words come back on every line of this page. Here they are in plain English, once.

Zap
An automation you build in Zapier: one trigger, then one or more actions that run each time the trigger's event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for it.
Action
What the Zap does after it starts: the step that creates, updates or moves something on your behalf.
Task
What Zapier bills. One task is one action that completed successfully; your plan's allowance counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment it happens.
Filter
A step that lets the Zap continue only if the incoming data meets your condition, and stops it quietly otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can reuse what it found.
Connection
Your account of an app, linked to Zapier once, then reused by every step of every Zap that talks to that app.
Cost

What a lemlist Zap really costs

Zapier bills tasks, not triggers. The activity that starts your Zap is free; each action after it is not.

  • TriggerNever costs a task
  • Successful action1 task each
  • Free plan100 tasks a month, 2-step Zaps
  • Premium appNo

Every action that goes through counts as one task, and a failed one is not counted. A Zap with three actions costs three times a one-action Zap. lemlist is not a premium app, so it runs on the free plan: 100 tasks a month, unlimited Zaps, two steps per Zap. Add a filter, a search or a second action and you are building a multi-step Zap, which needs a paid plan. The polling grid only concerns Unsubscribed Recipient: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise.

Connect

Connect your lemlist account

  1. 01

    Open the Apps page

    In Zapier, go to Apps and click + Add connection. You need a lemlist account, plus access to any campaign you do not own yourself and want the Zap to change.

  2. 02

    Pick lemlist

    Type lemlist in the search box of the dialog that opens, select it, then confirm with Add connection. A new browser tab then opens on the lemlist side.

  3. 03

    Sign in and grant access

    Log in to lemlist in that tab and allow Zapier to use the account. The connection then shows up in your list, ready to be picked in any step of any Zap.

First Zap

Your first Zap: flag interested leads everywhere

GoalWhen a lead's activity passes the rule you set (a reply, for instance), mark that lead as interested across all your lemlist campaigns.

  1. 01

    Create the Zap

    In Zapier, create a new Zap. Choose lemlist as the trigger app and New Activity as the trigger event, then select the connection you made.

  2. 02

    Test the trigger

    Run the test: Zapier brings back the three most recent activities of the account. Pick one of the kind you care about, so the next steps are set on real data.

  3. 03

    Add the filter

    Click the plus icon, add a Filter, then fill its three boxes: the value to look at, the rule, and what to compare with. Use a text rule on a text value.

  4. 04

    Add the action

    Add lemlist again with Mark a Lead From All Campaigns as Interested, and map the lead from the trigger step so the right person is flagged.

  5. 05

    Test, then publish

    Run each step once and check the lead in lemlist. When it is flagged as expected, click Publish. With the filter, this Zap needs a paid plan.

Triggers

The 2 lemlist triggers

2 events start a Zap when something happens in lemlist, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

New Activity

Instant trigger

In Zapier“Triggers when an activity has ocurred. It can be an email has been sent, replied to, bounced, or unsubscribed from or v3 new activity like a LinkedIn profile have been visited or a phone call just ended.”

Starts your Zap whenever something happens to a lead in lemlist: an email sent, replied to, bounced or unsubscribed from, and newer activity such as a LinkedIn profile visit or a phone call that just ended. One trigger, every signal of your campaigns.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a reply should reach the account owner's inbox or CRM while the prospect is still at their desk.
Watch out
the same event can fire several times (a lead opening one email twice); tick the Only First option to keep one run per event type.
2

Unsubscribed Recipient

Polling trigger

In Zapier“Triggers when a recipient be unsubscribes from an email subscription list.”

Watches the lemlist unsubscribe list and starts a Zap when a recipient is added to it. It gives other tools a clean feed of people who no longer want to hear from you.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
your newsletter tool should stop mailing anyone who opted out of your cold sequences, so consent matches across both.
Watch out
Zapier remembers what it has already seen on this list, so a recipient starts the Zap once, not at every check.
Actions

The 16 lemlist actions

lemlist gives you 16 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Enrich Lead

Action

In Zapier“Enrich lead with email, phone number and linkedin data.”

Fills in a lead with an email address, a phone number and LinkedIn data. The richer record comes back to Zapier, ready for the next step.

When to use it
a trade-show list holds only names and companies, and you want contact details before anything goes into a CRM.
Watch out
the next step can only use what the test actually returned.
2

Find Email

Action

In Zapier“Find someone verfied email address.”

Looks for a verified email address for a person and hands it back to the Zap. It answers one narrow question, which keeps the Zap easy to read.

When to use it
a new contact from a LinkedIn form lacks an email, and you want one before adding them to a sequence.
Watch out
plan what the Zap should do when nothing is found.
3

Find Phone

Action

In Zapier“Find someone phone number.”

Searches for a person's phone number and returns it to the Zap. Useful when a call step is part of your process and a number is missing.

When to use it
a hot lead flagged by the team should land in the dialer list with a number already attached.
Watch out
it runs as an action, so each successful run counts as a task.
4

Mark a Lead From All Campaigns as Interested

Action

In Zapier“Mark a Lead From All Campaigns as Interested.”

Sets the interested flag on a lead across every campaign it belongs to. No campaign to pick, the whole account follows.

When to use it
it is the action of the first Zap on this page, which flags a lead everywhere once their activity passes your filter.
Watch out
it touches every campaign the lead belongs to, with no way to leave one out.
5

Mark a Lead From One Campaign as Interested

Action

In Zapier“Mark a Lead From One Campaign as Interested.”

Flags a lead as interested inside one specific campaign. The status in lemlist then tells the team who to follow up with first.

When to use it
a prospect books a meeting through your calendar tool, and the campaign that brought them in should show it.
Watch out
the campaign is required; for every campaign at once, use the all-campaigns version.
6

Add Lead to Campaign

Action

In Zapier“Add a Lead to a campaign.”

Drops a new lead into the lemlist campaign you choose, so the sequence picks it up. Options let it find a verified email, enrich from LinkedIn, check an existing address and skip duplicates found in other campaigns.

When to use it
a demo request from your website should start a follow-up sequence without anyone retyping the contact.
Watch out
the campaign is required, so create it in lemlist first.
7

Mark a Lead From All Campaigns as Not Interested

Action

In Zapier“Mark a Lead From All Campaigns as Not Interested.”

Applies the not-interested flag to a lead in all campaigns at once. It is the account-wide version of the action above.

When to use it
a deal marked lost for good in your CRM should be reflected everywhere in lemlist.
Watch out
use it only when the answer is final, since every campaign is affected.
8

Mark a Lead From One Campaign as Not Interested

Action

In Zapier“Mark a Lead From One Campaign as Not Interested.”

Records that a lead is not interested in one given campaign. It keeps the reporting of that campaign honest without touching the others.

When to use it
a prospect answers "not for this product" and may still be a fit for another offer.
Watch out
the campaign is required here.
9

Pause Lead From All or Specific Campaigns

Action

In Zapier“Pause Lead From All or Specific Campaigns.”

Puts a lead on hold in every campaign or in the ones you name. The sequence stops sending to that person until you resume it.

When to use it
a prospect opens a support ticket, and sales emails should wait while the issue is being handled.
Watch out
pair it with the resume action, or the lead stays paused.
10

Remove Lead From Campaign

Action

In Zapier“Remove a Lead from a campaign.”

Takes a lead out of a campaign entirely. Unlike a pause, the lead leaves the sequence rather than waiting in it.

When to use it
a contact becomes a customer and should no longer receive prospecting emails from that campaign.
Watch out
the campaign is required, one Zap step per campaign.
11

Remove Lead From Unsubscribe

Action

In Zapier“Remove a Lead from unsubscribe.”

Lifts a lead off the unsubscribe list. That person can then be reached by your campaigns again.

When to use it
a former contact opts back in through a form, and lemlist should stop blocking them.
Watch out
run it only on explicit consent, never as a bulk cleanup.
12

Resume Lead From All or Specific Campaigns

Action

In Zapier“Resume Lead From All or Specific Campaigns.”

Restarts a paused lead in all campaigns or in selected ones. Outreach picks up where it stopped.

When to use it
the support ticket that paused the lead is closed, and the sequence can carry on.
Watch out
make sure the reason for the pause is truly over before a Zap restarts anything.
13

Unsubscribe a Lead

Action

In Zapier“Unsubscribes a Lead”

Unsubscribes a lead from the campaign you pick. lemlist then treats that person as having opted out of it.

When to use it
someone asks your support team to stop all emails, and the request should reach the campaign without a manual step.
Watch out
the campaign is required; for account-wide consent, also use the unsubscribe list.
14

Add Recipient to Unsubscribe List

Action

In Zapier“Add a recipient to the unsubscribe list.”

Puts an email address on the lemlist unsubscribe list. It records consent at the account level, not campaign by campaign.

When to use it
an opt-out collected by your newsletter tool should block that address from future cold campaigns too.
Watch out
the email address is required, and the list feeds the Unsubscribed Recipient trigger.
15

Update Lead From Campaign

Action

In Zapier“Update Lead From Campaign.”

Changes the details of a lead already sitting in a campaign. The same options as the add action are there: dedupe, find a verified email, LinkedIn enrichment, check the current address.

When to use it
a sales rep corrects a job title in the CRM and the personalized lines of the sequence should follow.
Watch out
the campaign is required, and the lead must already be in it.
16

Verify Email

Action

In Zapier“Verify existing email (debounce).”

Checks an existing email address before you use it. It is the guard against sending a sequence to an address that will bounce.

When to use it
leads from an old spreadsheet should be checked one by one before they enter a campaign and start receiving emails.
Watch out
chained after a find, it makes the Zap multi-step.
Searches

The lemlist search

1 search step looks for data that already exists in lemlist, so a later step can use it.

A search step finds a lead that already exists, so a later step can act on it. In the editor it sits at the bottom of the action list, under SEARCH, and some fields offer + Add search step to insert it for you. Three settings decide what happens when the result is not the one you expected.

1

Search Lead

SearchFind or create

In Zapier“Search a lead.”

Finds a lead in your lemlist account and passes it to the next step. The Find or Create Lead entry in the editor is this same search with the create box ticked, not a separate operation.

When to use it
a deal closes in your CRM and you need the matching lemlist lead before running Remove Lead From Campaign.
Watch out
it makes the Zap multi-step, so a paid plan.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps relying on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking it turns the search into a find-or-create. It then drops the setting above and asks for the fields needed to create the missing lead.
  3. If multiple search results are found?
    Three ways out when several leads match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When a lemlist Zap breaks

Zapier links no help article to lemlist, and no limit specific to the app is documented. What breaks is the general mechanics, and a busy outbound account meets them quickly.

Four cases explain most of the surprises. For a Zap that keeps failing without a clear reason, the Zapier troubleshooting guide goes through the checks in order.

  • Last month's opt-outs are not picked up

    A Zap only reacts to what happens after you publish it. Unsubscribes and replies from before stay where they are; moving that backlog is a separate job.

  • An unsubscribe Zap that feeds itself

    A Zap started by Unsubscribed Recipient that adds addresses back to the same list writes where its trigger watches. It runs again and again and burns tasks.

  • A bulk import gets held back

    When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold the runs back instead of firing them all.

  • The same opt-out never runs twice

    On the polling trigger, Zapier keeps track of what it has already seen. That avoids doubles, but test with a fresh address, not one the Zap has already seen.
Need help

Need help automating lemlist with Zapier?

A person reads every message.

FAQ

lemlist Zapier integration: questions people ask

01Is the lemlist Zapier integration free?
Yes, it runs on Zapier's free plan, because lemlist is not a premium app. The free plan gives you 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger and one action. Adding a filter, a search or a second action turns the Zap into a multi-step one, which needs a paid plan. The trigger itself never costs a task, so the activity that starts the Zap is free.
02How many tasks does a lemlist Zap use?
One task per action that completes successfully, and none for the trigger. A Zap that adds a lead to a campaign costs one task per lead; a Zap that finds an email, verifies it, then adds the lead costs three. Failed actions are not counted. Because New Activity fires on every event of every campaign, it is the trigger that drains an allowance fastest, so a filter or the Only First option pays for itself.
03Do lemlist triggers run in real time?
One does. New Activity is instant: lemlist tells Zapier the moment something happens and the Zap starts right away, whatever your plan. Unsubscribed Recipient is a polling trigger: Zapier checks it at regular intervals, every 15 minutes on the free plan, 2 on Professional and 1 on Team and Enterprise. Anything urgent, such as routing a reply, belongs on New Activity, and the editor marks it with a lightning bolt.
04What does it take to connect lemlist to Zapier?
A lemlist account, plus access to any campaign you do not own and want the Zap to change. You connect it once from the Apps page with + Add connection, sign in to lemlist in the tab that opens, and grant access. Every step then reuses that connection. Create your campaigns in lemlist first: most actions require one, and Add Recipient to Unsubscribe List requires an email address. The same connection then serves both triggers and all 16 actions.
05Why does New Activity start a Zap several times for one lead?
Because the same event can happen more than once: a lead can open the same email several times, and each open is an activity. The trigger has an Only First option for this. Tick it and the Zap runs only once per event type for that lead. Without it, every repeat reaches your actions and spends a task, which adds up quickly on a large campaign. A filter on the kind of activity is the other way to narrow it.
06What if the lemlist action you want is not in Zapier?
Then the integration does not offer it, and no setting will reveal it. The 16 actions cover leads, their status, enrichment and unsubscribes; none creates or launches a campaign. Keep that part in lemlist and let Zapier handle what happens before and after. Reading the list of action names once is the fastest way to know whether the change you have in mind is covered at all. If it is not there, no Zap will make it.
07Zapier, Make or n8n for lemlist?
It depends on your criteria rather than a ranking. On Zapier, lemlist runs on the free plan with one instant trigger and 16 actions, which makes a first automation quick to ship. Make and n8n can also work with lemlist, and each has its own page on this site. Compare which operations each one offers for your use case, and which tool your team already runs. On Zapier, a filter or a second action already means a paid plan.
Same platform

Other docs you might need on this stack.

Browse all integrations