How To Automate Cold Email From Sales Navigator With Claude? (2026)

JB Jezequel JB Jezequel Linkedin Sales Navigator

In cold email, timing beats copy.

A VP of Sales who started a new role last week is looking for quick wins. The same person six months later has already picked their tools.

Most teams still export a list once, email it weeks later, and wonder why the replies dried up.

30-Second Summary

  • Recurring exports find new leads for you: Evaboot runs your Sales Navigator search on a schedule and keeps only people who are new to it, with verified emails.
  • Claude writes one email per lead: a scheduled task reads each new lead's profile and company data, then writes an email from your brief.
  • Your tools take it from there: leads go into your CRM and your cold email platform automatically. We use HubSpot and lemlist here, but any tool with an API or MCP works.
  • Intent triggers make it timely: build searches around job changes, profile views and recent activity, so you email people when they're most likely to reply.

Now you can run your entire prospecting workflow on autopilot, from Sales Navigator all the way to a sent cold email.

You describe your ideal prospect in a sentence. From then on, new leads arrive every day, land in your CRM, and get a personalized email waiting in your campaign.

No CSV downloads. No copy-pasting. No list that goes stale.

In this guide, I'm going to show you how to set it up with the Evaboot MCP and Claude.

In my example, I'm using HubSpot as my CRM and lemlist to send emails. If you use different tools, the process is the same, as long as they have an API or an MCP.

Then I'll show you how to use LinkedIn's intent triggers to reach people at the right moment.

Walkthrough: a Sales Navigator search, a daily Evaboot recurring export, and a scheduled Claude task that fills HubSpot and lemlist

Everything is in one public GitHub repo: the skill, the daily task, an email brief and the n8n workflow. Paste the prompt into your AI Agent, or pick the n8n tab to run it in n8n.

Agent kit Free · Public

Let your AI agent set it up

Paste this prompt into Claude Code, Codex or Cursor. Your agent clones the public repo, follows its instructions and asks before every change.

Prompt · GitHub
Clone https://github.com/evaboot-labs/daily-lead-pipeline, read AGENTS.md
and follow the skill. Set up a daily pipeline for VPs of Sales in France.

In the repo

  • The daily-lead-pipeline skill: search, recurring export, campaign, brief and first run
  • TASK.md: the daily task you schedule in Claude
  • BRIEF.md: the brief every email follows
  • The n8n workflow, with its setup guide

Set it up in n8n

Paste this prompt into your AI agent and it walks you through the import, one step at a time. Or open the workflow JSON on GitHub and import it yourself.

Prompt · n8n
Set up the daily lead pipeline in my n8n.
Clone https://github.com/evaboot-labs/daily-lead-pipeline and follow docs/n8n.md.
Walk me through importing n8n/daily-lead-pipeline.json,
the Evaboot, lemlist, Anthropic and HubSpot credentials and the settings,
one step at a time.

In the repo

  • The workflow JSON: every day, today's Evaboot run in, HubSpot contacts and lemlist leads out
  • docs/n8n.md: the credentials and the settings, step by step
  • The same filters and email rules as the Claude task

Here is what this guide covers:

In this guide

  • What You Need
  • How To Build the Automated Pipeline
  • How To Run Intent-Based Automated Outreach
  • Segmented vs Personalized Emails
  • Choosing a Cadence
  • How To Change or Stop the Pipeline
  • Limits and What To Watch
  • FAQ

What You Need

Before you start, make sure you have these 5 things in place:

  • An Evaboot account with credits. Each lead costs 1 credit, email included.
  • A LinkedIn Sales Navigator seat, connected to Evaboot through the Chrome extension.
  • A HubSpot account, where every new lead is saved as a contact.
  • A lemlist account with at least one warmed-up sending mailbox, or any outreach tool with an MCP.
  • A paid Claude plan. The daily task runs in the Claude desktop app, or as a Claude Code routine.

Setup takes around 20 minutes. After that, the pipeline runs on its own.

Here is what each tool does in the pipeline:

StepToolWhat it does
1EvabootRuns your search every day, keeps only new people, finds and verifies emails.
2ClaudeReads the new leads and writes one email per person.
3HubSpotSaves each lead as a contact, so your CRM stays up to date.
4lemlistReceives each lead with its own email and sends it.

How To Build the Automated Pipeline

There are 9 steps. You only do them once.

  1. Connect Evaboot and lemlist to Claude
  2. Connect HubSpot to Claude
  3. Check Sales Navigator is connected
  4. Build your search from a sentence
  5. Turn it into a daily recurring export
  6. Create the lemlist campaign
  7. Write your email brief
  8. Schedule the daily Claude task
  9. Review the first batch, then go live

1. Connect Evaboot and lemlist to Claude

Evaboot gives you the exact setup for each AI tool. In your Evaboot dashboard, open MCP in the left menu and pick the Claude tab.

Claude tab on the Evaboot MCP page with the connector URL https://mcp.evaboot.com/mcp and the setup steps

In Claude, open Settings > Customize > Connectors, click Add, and add a custom connector named Evaboot with the URL https://mcp.evaboot.com/mcp. Sign in to Evaboot and approve.

claude add custom connector dialog with the name evaboot and the url https://mcp.evaboot.com/mcp

lemlist is in Claude's connector directory. On the same page, click Browse, search lemlist, click Connect and authorize your lemlist team.

If you work in Claude Code, open the Claude Code tab on the same Evaboot page instead.

Using Claude Code?

The Claude Code tab gives you a one-line claude mcp add command. It already includes your Evaboot API key, so you run it in your terminal and you're connected.

Treat that command like a password. Don't paste it in a shared doc or a screenshot.

This is the Claude Code tab, with the API key hidden:

Claude Code tab on the Evaboot MCP page with the claude mcp add command, API key hidden

2. Connect HubSpot to Claude

HubSpot has its own connector in Claude, so you don't need a URL.

In Settings > Connectors, find HubSpot, click connect, and sign in to your HubSpot account.

Grant the permissions it asks for, so Claude can read and create contacts.

hubspot connector page in claude with the connect to claude button

Then create one contact property in HubSpot: Lead source, a single-line text field, in Settings > Properties. The task writes where each contact came from in it.

3. Check Sales Navigator Is Connected

Before you build anything, ask Claude to check your account.

Prompt

Check my Evaboot quota and whether my Sales Navigator is connected.

Claude shows your credits and your Sales Navigator status.

claude reply: sales navigator connected and valid, 2,490 exports left today and the credit balance

If the status says invalid, the fix takes one minute:

If the status is invalid

Open Chrome, sign in to Evaboot, open any Sales Navigator search and click Export with Evaboot.

Opening the export page is enough. Then ask Claude again.

4. Build Your Search From a Sentence

Describe your ideal prospect in plain English. Ask for people first, then for the company filters. Claude turns it into real Sales Navigator filters.

Prompt

Build a Sales Navigator search for VPs of Sales in France, about 500 people. Search people only, then add the Software Development industry and the 51-500 employees company size to the search URL.

Claude builds the people search, adds the industry and company size to the URL, and gives you a Sales Navigator link.

Open it and check the people before you move on. This search runs every day from now on, so it's worth getting right.

claude reply with the people search, the software development industry and the 51-500 company size added, and an open in sales navigator link

Here is the same search in Sales Navigator, with more than 1,000 people:

sales navigator lead search with the 51-200 and 201-500 company headcount, sales title and france filters, and 1k+ results, names hidden

Notice the order of the prompt. It matters:

Why people first?

If your first sentence names an industry or a company size, Evaboot builds the search from a temporary list of companies.

A recurring export can't repeat that kind of search. A people search with the company filters added can.

One more piece of advice before you move on:

5. Turn It Into a Daily Recurring Export

Now tell Claude to run the search on a schedule.

Prompt

Run this search every day and export only the new leads. Name it "VP Sales France SaaS". Don't send it to any integration.

The first run happens one day later, not straight away. Each run brings only people who are new to the search.

claude reply: vp sales france saas set up as a daily recurring export with no integration attached, first run tomorrow

Ask Claude for the next run time. You'll schedule the email step a few hours after it.

Every run spends credits

Each new lead costs 1 credit. If you run out, that day's run is skipped.

Notice the last sentence of the prompt. It matters.

Why "Don't send it to any integration"?

Claude adds the leads to HubSpot and lemlist, not Evaboot.

If you also switch on Evaboot's own lemlist or HubSpot integration, leads arrive twice, and some arrive with no email written.

6. Create the lemlist Campaign

Ask Claude to create the campaign. Its first email is two custom variables that Claude fills for each lead.

Prompt

In lemlist, create a campaign named "VP Sales France SaaS". Its first email has the subject {{aiSubject}} and the body {{aiEmail}}.

Here is the first step in lemlist:

lemlist campaign editor with the aiSubject variable as the subject and the aiEmail variable as the message in step 1

lemlist shows both as contact variables. Claude writes aiSubject and aiEmail for each lead when it adds the lead to the campaign.

Add your follow-up steps as normal templates. Connect your sending mailbox, but don't start the campaign yet.

7. Write Your Email Brief

This is what makes the emails good. Claude follows it for every lead.

Keep it short and concrete.

Example brief

We are Acme. We help sales teams book more demos with [one-line offer].
Proof: [one customer result with a number].
Goal of the email: get a reply, not a meeting.

Rules:
- 60 to 90 words. Plain text. No links.
- First sentence is about them, from ONE real fact in their data: a new role, company growth, sales team size, or something in their headline or summary.
- Never invent a fact. If nothing stands out, use their role and industry.
- One question at the end.
- Subject: 2 to 4 words, lowercase, no clickbait.
- Write in the language of their country.

The brief is the only part you need to write yourself.

8. Schedule the Daily Claude Task

In the Claude desktop app, open Scheduled > New task.

Set it to run daily, a few hours after your Evaboot run, with permissions on Auto. Paste this as the task, with your names and your brief filled in. It is also TASK.md in the repo:

Scheduled task

Run my daily lead pipeline.

Settings:
- Evaboot recurring export: VP Sales France SaaS
- lemlist campaign: VP Sales France SaaS
- HubSpot lead source: Evaboot recurring export

1. In Evaboot, call get_export_list and take the newest export whose name starts with the recurring export name. If its status is not EXECUTED, stop and tell me. If it was created more than 24 hours ago, stop and tell me there is no new run today.
2. Call get_export on it to get all its leads. Keep only leads where Matches Filters is YES and Email Status is safe. Count the others and why they were skipped.
3. In HubSpot, create or update a contact for each kept lead, matched on email: email, first name, last name, company name, job title, LinkedIn URL, and the property "Lead source" set to the HubSpot lead source above.
4. For each kept lead, write a cold email that follows my brief below. Use only facts from that lead's Evaboot data: never invent a customer, a number or a result. If nothing in the data fits the brief, skip the lead and say why.
5. In lemlist, call get_campaigns to find the campaign by name, then add_leads_to_campaign with deduplicate true. For each lead: email, firstName, lastName, companyName, companyDomain, jobTitle, linkedinUrl, and customVariables aiSubject (the subject) and aiEmail (the body). Never start the campaign.
6. Give me a summary: leads in the run, leads kept, contacts created or updated in HubSpot, leads added to lemlist, leads skipped and why, and 3 sample emails.

My brief:
[paste your brief here]

Here is the task in the Claude form:

claude new scheduled task form named daily lead pipeline, with the settings, auto permissions and a daily trigger at 18:00

The task also runs outside the desktop app:

Using Claude Code instead?

You can create the same task as a routine at claude.ai/code/routines, or with the /schedule command.

Routines use the same connectors you set up in Claude.

9. Review the First Batch, Then Go Live

After the first run, Claude gives you a summary: leads in the run, leads kept, contacts saved and emails written.

claude scheduled task run summary: 10 leads in the run, 3 kept, hubspot contacts created and updated, 3 leads added to lemlist, names hidden

Check HubSpot too. The new contacts should be there, with the lead source filled in.

hubspot contact properties with lead source set to evaboot recurring export

Then open the campaign in lemlist and preview the emails lead by lead.

lemlist email preview of one lead, with the subject and the body claude wrote from the lead's data

If something is off, fix the brief and run the task again by hand. When the emails are right, start the campaign.

You're live

From now on, every new lead is saved in HubSpot, gets its own email, and enters your sequence with no action from you.

How To Run Intent-Based Automated Outreach

The pipeline above emails anyone who matches your ideal customer profile.

Intent-based outreach goes one step further. It emails people at the moment something changes.

  • What intent-based outreach is
  • The LinkedIn triggers you can use
  • One saved search per trigger
  • Using Evaboot alerts as a trigger

What Is Intent-Based Outreach?

Definition

Intent-based automated outreach means using LinkedIn triggers, like a job change or a profile view, to decide who gets an email and when.

Instead of one big list, each trigger feeds its own flow of leads, with an email that fits the moment.

A trigger gives you two things: a reason to reach out now, and a natural first line.

The LinkedIn Triggers You Can Use

Sales Navigator has filters that act as triggers. Add any of them to your search, and your recurring export only picks up people who match.

TriggerWhy it worksEmail angle
Changed jobs in the past 90 daysNew leaders review tools and want early winsCongratulate, then offer a quick win for the new role
Viewed your profile recentlyThey already know your nameLight and direct, no pitch in the first line
Posted on LinkedIn in the past 30 daysThey're active and have shared a viewReply to the idea in their post
Following your companyThey've shown interest in what you doAsk what caught their attention
Work anniversaryA natural moment to review what's workingMark the milestone, ask about the next year

One Saved Search Per Trigger

Build a separate search for each trigger, then turn each one into its own recurring export.

Prompt

Build a Sales Navigator search for VPs of Sales at SaaS companies with 50 to 500 employees in France who changed jobs in the past 90 days. Then run it every day, export only the new leads, and name it "VP Sales France SaaS - Job change". Don't send it to any integration.

Keeping one export per trigger means you always know why a lead is in your pipeline.

Using Evaboot Alerts as a Trigger

Sales Navigator also sends alerts when your saved leads change jobs, post, or when their company raises money.

The Evaboot MCP can read those alerts, so Claude can pick up the leads behind them and add them to the right campaign.

Add one line to your scheduled task: "Read my Sales Navigator alerts for my saved leads, and add each lead with a job change to the job change campaign."

Claude reads the job changes, posts and funding rounds in your feed, for all saved leads or for one lead list.

Segmented vs Personalized Emails

Once you have leads coming in by trigger, there are 2 ways to email them.

  • Segmented: one campaign per trigger
  • Personalized: one campaign, Claude adapts
  • Which one to choose

Segmented: One Campaign Per Trigger

Each trigger gets its own lemlist campaign, its own brief and its own scheduled task.

A job change lead gets a "new role" email. A profile view lead gets a "saw you stopped by" email.

Example: job change email (fictional names)

Subject: new role at northwind

Hi Claire, congrats on the move to Northwind. Three months in is usually when a new sales leader starts fixing the pipeline.

We helped Brightline add 40 demos a quarter by fixing exactly that, without adding headcount.

Is pipeline on your list for this quarter?

Personalized: One Campaign, Claude Adapts

All triggers feed one campaign. Claude reads which export each lead came from, and writes the first line around that trigger.

You manage one brief and one sequence, but every email still reflects the moment.

Add to your brief

Each lead comes from an export named after a trigger (Job change, Profile view, Posted recently). Open the email with that trigger. If the trigger doesn't fit their data, fall back to their role and company.

Which Should You Choose?

SegmentedPersonalized
SetupMore campaigns and tasksOne campaign, one task
ControlFull control per triggerClaude decides the angle
ReportingReply rate per trigger, out of the boxNeeds a tag per trigger
Best forTesting which triggers workRunning many triggers at once

Choosing a Cadence

Match the schedule to how fast the trigger moves, not how often you want new leads.

  • Daily suits fast triggers like job changes and profile views, where being first matters.
  • Weekly suits active outbound, where you work through leads faster than the search refills.
  • Monthly suits broad ICP searches that change slowly.

Daily runs on a search that adds four people a month just burn tasks and attention.

Keep the email task in step

If you change an export from daily to weekly, change the scheduled Claude task too.

How To Change or Stop the Pipeline

Everything can be changed with a sentence to Claude.

You want toDo this
Get fewer leads per dayAsk Claude: "Make my VP Sales recurring export weekly."
Pause the lead flowAsk Claude: "Pause my VP Sales recurring export."
Change the email styleEdit the brief inside the scheduled task.
Stop sendingPause the campaign in lemlist.
Stop everythingAsk Claude: "Delete my VP Sales recurring export." Then delete the scheduled task.

Limits and What To Watch

Three things can stop the pipeline or hurt your results:

  • Credits and skipped runs
  • The 2,500 lead cap
  • Deliverability and compliance

Credits and Skipped Runs

Each new lead costs 1 credit. If your balance runs out, the run is skipped for that day.

Check your quota before you add more triggers.

Prompt

How many Evaboot credits do I have left, and how many leads did my recurring exports bring in last week?

The 2,500 Lead Cap

A Sales Navigator search shows at most 2,500 leads. If your search is bigger, split it by region, seniority or industry.

With recurring exports this matters less, because each run only picks up new people.

Deliverability and Compliance

Automation sends faster, so mistakes spread faster too.

  • Only email leads with a safe email status.
  • Warm up your mailboxes and set up SPF, DKIM and DMARC before you go live.
  • Keep daily volume in line with how many mailboxes you have.
  • Add an easy way to opt out, and check the rules where you and your leads are based (GDPR, CAN-SPAM).

For more, read our guide to cold email best practices.

Keep a human in the loop

Read Claude's daily summary. It takes 2 minutes, and it's how you spot a bad brief before it reaches 100 inboxes.

That's the whole pipeline. Here is the short version:

Frequently asked questions

Does Evaboot send the emails?

No. Evaboot finds, cleans and verifies the leads. Claude writes the emails, and lemlist (or your own email tool) sends them.

Do I need Claude Code?

No. You can do everything in the Claude desktop app. Claude Code is an option if you prefer routines, or already work there.

Can I use a tool other than HubSpot or lemlist?

Yes. Any CRM or email tool with an API or an MCP that Claude can connect to will work. Only the tool names in your scheduled task change.

How much does it cost per lead?

Each new lead costs 1 Evaboot credit, with email finding and verification included. You also need your Sales Navigator, Claude, HubSpot and lemlist plans.

What happens if a run fails?

If the Evaboot export hasn't finished, the Claude task stops and tells you. If you're out of credits, that day's export is skipped. Nothing is sent by mistake.

Can I use Evaboot's native integrations instead?

Yes, but not together with this workflow. Native integrations push leads without an email written by Claude. If you use both, leads arrive twice.

Will the same person get emailed twice?

No. Recurring exports only bring new people, and the task skips anyone already in the lemlist campaign. HubSpot contacts are matched by email.

Rate this article

Free playbook · 04 steps

The Unlimited Leads System™

Enter your email and we'll send you the playbook.