LinkedIn Outbound Loop: Clay + Lemlist + HubSpot

Job changes are the single highest-intent signal in B2B outbound. Most teams waste them by reacting two weeks late with a generic cold email. The workflow I’m walking you through fires within 48 hours of a prospect changing roles, drops a personalized LinkedIn touch first, escalates to a Lemlist email sequence, and logs every open, click, and reply back to HubSpot as structured activity data. I’ve deployed this at three SaaS clients this year. It consistently outperforms static list campaigns by 2 to 3x on booked meetings.

Why This Three-Tool Stack Works

The logic is simple. Clay does the signal detection and enrichment work that used to eat three hours of an SDR’s morning per account. Lemlist handles the multichannel sequencing with personalized images and LinkedIn steps built in. HubSpot closes the loop so AEs have context before they ever pick up the phone. None of these tools gets you there alone, but together they form a tight signal-to-sequence-to-CRM loop that runs largely without human intervention.

Before you build, you need a few things in place. A Clay workspace with LinkedIn enrichment enabled (via the native integration or a Phantombuster connection). A Lemlist account on the Email Pro or Multichannel plan, because LinkedIn steps require Multichannel. And HubSpot with the Lemlist native integration installed from the App Marketplace. HubSpot’s State of Sales 2024 report found that reps who receive automated activity logging spend 21% more time on actual selling. That is exactly the time this stack gives back.

The Gotcha That Breaks This Workflow

The most common failure point I see is merge field mismatches between Clay’s column headers and Lemlist’s expected variable names. Clay exports column headers as-is. Lemlist expects camelCase variable names. If your Clay column is called “First Name” with a space, Lemlist will not parse it. Full stop.

// Clay HTTP action body -- use camelCase keys
{
  "email": "{{email}}",
  "firstName": "{{first_name}}",
  "linkedinUrl": "{{linkedin_url}}",
  "currentCompany": "{{company}}",
  "recentPostSummary": "{{recent_post_summary}}",
  "jobChangeDate": "{{started_date}}"
}

HubSpot Tracking: What to Actually Measure

Once Lemlist is writing activity back to HubSpot, resist the urge to track everything. I tell clients to focus on three properties: lemlist_last_reply_date, lemlist_sequence_status (active, replied, bounced, unsubscribed), and lemlist_campaign_name. Create a HubSpot list for contacts where lemlist_sequence_status = replied and lifecycle_stage != customer to give your AEs a clean SQL queue. Then build a simple HubSpot report showing reply-to-meeting conversion by campaign name so you can A/B test your Lemlist sequence copy over time.

G2’s outbound sales benchmarks show that teams closing the feedback loop between sequence engagement and CRM stage see 28% higher conversion from SQL to opportunity. That number tracks with what I see in practice. The teams skipping this step are optimizing sequence copy in the dark.

This is also where the Trigify + HubSpot lead scoring workflow becomes additive. If you’re already scoring leads in HubSpot, pipe Lemlist engagement events into your scoring model as positive signals.

Which plan do you actually need?

Choose Clay if

• You are running more than 500 enriched contacts per month
• You want waterfall enrichment across multiple data providers in one table
• You need custom formula columns and signal logic without code

From $149/mo (Explorer) Try Clay →

Choose Lemlist if

• You want LinkedIn connection and message steps built into your sequences natively
• You need dynamic image personalization without a design tool
• You are running multichannel outbound from one campaign interface

Multichannel from $99/mo Try Lemlist →

Choose HubSpot if

• Your AEs live in a CRM and need activity context before calls
• You want workflow automation to route replied contacts to reps automatically
• You need reporting across the full signal-to-close funnel

Sales Hub Starter from $20/seat Try HubSpot →

Ship This Week, Iterate Next Month

This workflow is intentionally scoped to one signal (job changes) and one sequence structure (LinkedIn first, email escalation). Do not bolt on intent data, website visitor signals, or account scoring in the first build. Get 50 contacts through the full loop, check your HubSpot activity log, verify that replies are routing to reps, and measure reply rate before you add any complexity.

If you want to extend the signal layer, the Warmly + Make signal-based outbound workflow pairs well here as a warm account layer running in parallel. The Clay enrichment table approach also scales cleanly to cold email deliverability workflows if you want to add volume through a tool like Smartlead or Instantly later. But the three-tool core, Clay pulling signal, Lemlist sequencing it, and HubSpot tracking it, is already a production-grade outbound loop that most sales teams simply don’t have.