Learning Objective
By the end of this tutorial, you’ll know how to find your lemlist Zapier credentials (team ID + API key) and use them to connect lemlist to Zapier so you can start building Zaps.
Why This Matters
Connecting lemlist to Zapier lets you automate repetitive actions (like updating spreadsheets, notifying Slack channels, or syncing lead activity), so your tools stay aligned without manual work.
Prerequisites
You have access to a lemlist workspace (team).
You have a Zapier account where you can create or edit Zaps.
Core Lesson — Step-by-Step Workflow
Phase 1: Get your Zapier credentials in lemlist
In lemlist, click your profile/name in the bottom-left, then select Settings
In the left sidebar, click Integrations, then find Zapier and click Connect
In the Connect lemlist to Zapier pop-up, copy your Login (your lemlist team ID) and your Password (your lemlist API key). You’ll paste these into Zapier when prompted
Phase 2: Connect lemlist inside Zapier
Go to the official lemlist + Zapier integration page in Zapier.
Create a new Zap (or edit an existing one) and select lemlist as the Trigger or Action app.
When Zapier asks you to connect an account, paste your lemlist Login (team ID) and Password (API key) from Phase 1, then complete the connection test in Zapier.
Practical Application / Real-Life Example
Lead status alerts: When a lead replies in lemlist, send a Slack message to your sales channel.
Spreadsheet sync: When a lead’s status changes in lemlist, update a row in Google Sheets.
Troubleshooting & Pitfalls
Issue: Zapier won’t connect to lemlist (authentication error)
Root cause: Team ID and/or API key is incorrect, or the API key used in Zapier is no longer valid.
Fix:
Go back to lemlist Settings → Integrations → Zapier to copy the current Login (team ID) and Password (API key).
In Zapier, reconnect the lemlist account (or update the connection) using the latest credentials, then re-test.
Issue: A Zap suddenly stops working after it used to work
Root cause: The Zapier connection was disconnected, or the API key used for the connection changed.
Fix: Reconnect the lemlist account in Zapier using the current API key, then turn the Zap back on.