Claude + Lemlist
Claude writes every email and sorts every reply. Lemlist sends, follows up and tracks. Connect the two, hand over a contact list and one ask, and your outreach runs whenever you want: on demand, or on a schedule you pick. Here is the exact setup and both prompts.
Sound familiar? Sending 500 personal emails by hand takes a week. Sorting the replies takes another.
The workflow
Contacts loaded into Lemlist
Lemlist linked to Claude
Batches in a sequence, when you choose
Replies bucketed and drafted
The tools
Each does the part it's best at. Together they turn a contact list into a running outreach pipeline.
What this is
The Lemlist connection lets Claude manage your campaigns and sequences straight from the chat.
One prompt drafts a personal email for every contact, adds it to a sequence, and schedules the follow-up.
Run the prompt any time you like, or save it as a scheduled task so the next batch goes out on its own.
A second prompt buckets yes, no, questions and auto-replies, and drafts answers for the ones that matter.
The honest bit
It will if you blast. A million happens in small batches over time, spread across several warmed-up sending inboxes, with a follow-up and an easy way to opt out. Start with a few hundred per batch, watch your reply and complaint rates, and add volume only while the numbers stay healthy.
It depends where you and your recipients are: CAN-SPAM in the US, GDPR in the EU, the PDPA and Spam Control Act in Singapore. At minimum, email people with a real reason to hear from you, say who you are, include an unsubscribe option and honor it right away. Check your market's rules before you scale.
Step by step
0 of 4 done
Sign up, create a campaign, and import your contacts as a CSV with name, email and company. Connect a sending address so emails go out from you.
Clean the list first: remove rows without an email, drop anyone who opted out before, and dedupe by domain if you want one contact per company.
In Claude, open Settings → Connectors, find Lemlist in the directory and click Connect. Sign in to Lemlist, pick your team and approve access, then ask “list my Lemlist campaigns” to confirm it works. Full steps in the FAQ ↓
Paste the send prompt, swap the bracketed details, and review the first table of emails before you send more or put it on a schedule.
Start small: about 50–100 a day per inbox.
Once replies start coming in, paste the reply prompt. Log your numbers, then decide whether to add volume.
Prompts
Copy a prompt, swap the [highlighted words] for your own details, and paste it into Claude.
Using the Lemlist connector, pull every person in the list called [LIST NAME] who has not been emailed yet and has not unsubscribed. For each one, write a short, friendly email from me that [THE ASK, e.g. asks them to reply with one word about X]. Keep it under 80 words, personal, and a little playful. Say who I am and end with a one-line way to opt out. Add each email to the Lemlist campaign called [CAMPAIGN NAME] with one follow-up 3 days later, mark the lead as Contacted, and give me a table of who was emailed. Send to [BATCH SIZE, e.g. 200] people now. If I ask, set this up as a scheduled task that sends the next batch [WHEN, e.g. weekdays at 9am]. Pause and tell me if the bounce or unsubscribe rate goes above [X]%.
Using the Lemlist connector, read every reply that came into the [CAMPAIGN NAME] campaign since [WHEN, e.g. yesterday]. Sort them into: said yes, said no, asked a question, asked to unsubscribe, automated reply. Unsubscribe anyone who asked and remove them from all campaigns. For everyone who said yes or asked a question, draft a reply from me and queue it. Remove automated replies from the campaign. Give me the counts for each group, the sent, open and reply numbers for that period, and the three most interesting replies.
FAQ
How to set it up, and what Claude can and can't do once it's connected.
Takes about two minutes.
Add it as a custom connector instead. In Settings → Connectors, choose Add custom connector, name it lemlist, and use this URL:
https://app.lemlist.com/mcp
Then sign in to Lemlist and approve access the same way.
No. The connection uses your Lemlist sign-in, and it stays connected on its own. If you'd rather use a key, you can create one in Lemlist under Settings → Team → Integrations.
Claude doesn't act on its own when something happens in Lemlist. A new reply or a new lead won't set anything off. It works when you run a prompt, or on a schedule you set up.
It also works with what you give it. The better your list, offer and ask, the better the emails.
Some actions do, such as finding or verifying email addresses. Claude tells you before it runs one of those.
It does what your prompt says. Ask it to show you the first batch before anything goes out, check a few emails, then let it send.
Make it yours
Book a call, try a free tool, answer a one-question survey. The prompt doesn't care what you ask for.
Run two batches with different first lines and let Lemlist show you which gets more replies.
Add a line asking Claude to create a task for you on every yes, so nothing slips.
Before & after
Lemlist connected to Claude. One prompt sends personal emails in batches whenever you want, and a second sorts every reply before you open your inbox.
Ready?
You have the exact prompts. All you need is a Claude account and a Lemlist account. Both take a minute.