By the end of this tutorial, you’ll know how to stop (or pause) lemlist campaigns automatically when a prospect books a meeting, using lemcal, a manual link-based approach, or Zapier for true “meeting booked” automation.
Why this matters
When someone books time on your calendar, continuing to send follow-ups can hurt the experience and lower conversion quality. Stopping campaigns at the right moment keeps your outreach relevant, reduces noise, and helps you focus on prospects who are ready to talk.
Prerequisites
You already have an active lemlist campaign.
You have a scheduling link ready (lemcal, Calendly, or another calendar tool).
If using Zapier: you have access to Zapier and permission to connect your apps.
Core lesson — Step-by-step workflow
Phase 1: Choose the right method
Use lemcal if you want the simplest setup inside the lemlist ecosystem.
Use manual link-based pausing if you don’t use lemcal and can accept that clicks don’t always mean a meeting was booked.
Use Zapier if you want the campaign to stop only when a meeting is actually confirmed (best accuracy).
Phase 2: Configure campaign behavior
Option 1: Lemcal users (recommended if you’re on lemcal)
Open your campaign settings (click the Settings gear icon), then in General settings enable Book a lemcal meeting under “Stop the campaign for people that”.
This ensures the campaign stops for that lead as soon as they book via lemcal, preventing unnecessary follow-ups. Note that, by default, lemlist already stops campaigns for leads who reply to campaign messages.
Option 2: Without Zapier (manual link-based integration)
If you’re not using lemcal, you can rely on lemlist’s behavior to pause/stop a campaign when someone clicks a specific link (for example, your Calendly link).
Important limitation: a click doesn’t guarantee a booking. Some prospects click your scheduling link but don’t complete the booking, so this method can stop campaigns too early.
Also note: lemlist campaign stopping/pausing is based on actions tied to that campaign’s flow, and direct cross-campaign automation isn’t supported inside lemlist.
Option 3: Using Zapier
Zapier lets you stop campaigns only when a meeting is truly booked (e.g., “Invitee Created” / “Meeting Scheduled” in Calendly). This reduces false positives and keeps your pipeline focused.
How to set it up (Zapier)
Log in to Zapier and click Make a Zap.
Select Calendly (or your calendar tool) as the trigger app, and choose a trigger that indicates a confirmed booking.
Select lemlist as the action app. If you need help connecting lemlist, see How to connect lemlist to Zapier.
Configure the action to stop the campaign for the booked lead (using the email as the identifier when available).
Test the Zap to confirm the right lead is stopped in lemlist.
Turn on the Zap.
Practical application (example workflow)
Example: You run a 5-step email campaign with a scheduling CTA in steps 2 and 4.
If you use lemcal: stop the campaign immediately when the meeting is booked so step 3–5 never send.
If you use Calendly + Zapier: trigger on “meeting scheduled,” then stop the lead’s campaign in lemlist to avoid any post-booking outreach.
If you use manual link-based pausing: pause/stop on click, but monitor results since some clicks won’t become bookings.
Troubleshooting & pitfalls
Issue: The campaign stops too early (before a meeting is actually booked).
Root cause: You’re stopping based on link clicks, not confirmed bookings.
Fix: Use Zapier with a “meeting booked/confirmed” trigger instead of a click-based rule.
Issue: The Zap runs, but the campaign doesn’t stop for the right lead.
Root cause: The identifier sent from the calendar tool doesn’t match the lead data in lemlist (often email mismatch).
Fix: Ensure the Zap uses the lead’s email address (or the same unique field used in lemlist) and run a test booking with a known lead record.
Issue: Leads still receive messages from another campaign.
Root cause: lemlist doesn’t support native cross-campaign automation for stopping leads across multiple campaigns.
Fix: Use import-time Duplicate Handling to prevent enrolling leads in multiple campaigns, and/or manage exclusions with tags/segments plus external automation (Zapier) where appropriate.
Knowledge check
Are you stopping based on a confirmed booking (best) or a link click (less accurate)?
If using Zapier, did you test with a real booking and confirm the correct lead was stopped in lemlist?
Have you prevented leads from being active in multiple campaigns at once (via Duplicate Handling or your enrollment rules)?