LinkedIn to Cold Email Sequencing
7-step multichannel sequence: LinkedIn touchpoints first, email phase gated behind a verified no-reply condition, shared exit on both channels.
Before You Start
7 steps, 2-4 hours: prerequisites and scope
Output: A 7-step multichannel sequence with LinkedIn connection and DM steps in Phase 1, a reply-gated email phase, and shared exit conditions across both channels.
Time: 2-4 hours for a single-stack tool. Add 1-2 hours for a split-stack setup requiring a Zapier or Make bridge.
LinkedIn account with no restrictions and 2-3 weeks of sending history at safe limits. Verified lead list with both a LinkedIn URL and an email address per contact. Sending domain warmed 4-6 weeks before the email phase goes live.
Workflow Overview
7-step sequence: LinkedIn to cold email at a glance
| Step | Action | Channel | Tool | Output |
|---|---|---|---|---|
| 1 | Set channel order and reply-gate logic | Planning | Sequence builder | Defined trigger conditions per channel |
| 2 | Source and verify email + LinkedIn URL per lead | Data | Enrichment tool / native finder | Lead list with both LinkedIn URL and verified email |
| 3 | Send connection request with personalized note | Automation tool | Connection request in market (Day 1) | |
| 4 | Send DM 1 and DM 2 with reply detection active | Automation tool | Two DMs; sequence pauses on any reply (Days 3-5) | |
| 5 | Trigger email phase after LinkedIn window closes with no reply | Transition | Condition / webhook | Email phase activates only for non-replies (Day 7-8) |
| 6 | Run 3-email cold sequence with global reply exit | Cold email tool | 3 emails over Days 8-20; reply on either channel stops all | |
| 7 | Log replies to CRM from both channels | CRM | CRM / unified inbox | Full conversation history per contact in one place |
Step by Step
Full build: 7-step LinkedIn to cold email sequence
- Set channel order and define the reply-gate condition
LinkedIn-first is the default: the connection request puts your name in front of the prospect before the email phase fires. Set the reply-gate condition before building any steps, it locks to whichever channel runs first.
- Source and verify both a LinkedIn URL and an email for every lead
Single-stack tools (lemlist at $109/mo, La Growth Machine at approx. €100/mo) include built-in email finding and verification. In split-stack setups, enrich via Apollo, Clay, or Hunter and tag contacts with no verified email to stay LinkedIn-only.
- Configure the LinkedIn phase: connection request Day 1, two DMs Days 3-5
Day 1: connection note under 300 characters with a role-specific hook. Days 3-5: DM 1 (short problem framing) then DM 2 (low-friction invite if no reply). Reply detection must be active on every DM step.
- Build the reply-gate transition between LinkedIn and email
In single-stack tools (La Growth Machine, Reply.io at $89/mo, lemlist), use the native "if no reply, proceed to email" condition at Day 7-8; in split-stack setups, a Zapier trigger on "completed, no reply" enrolls the contact in email. Test on 3 contacts manually before running any volume.
A timed delay is not a reply-gate. "Wait 7 days then email" skips the reply check and sends email to contacts who already replied on LinkedIn. Use the explicit "if no reply" condition, or read reply status from the LinkedIn tool via webhook.
- Build the email phase: 3 emails across Days 8-20
Email 1 (Day 8): standalone cold email, light LinkedIn context only, no "you didn't reply" framing. Email 2 (Day 14): different angle and hook. Email 3 (Day 20): a single yes/no question consistently outperforms longer closes.
- Configure global exit conditions covering both channels
Single-stack tools handle cross-channel exit natively. Split stacks need two webhooks: LinkedIn reply unenrolls from email, email reply marks LinkedIn sequence complete. Test both directions before enrolling live contacts.
- Log replies from both channels to a shared CRM record
La Growth Machine and Reply.io sync natively to HubSpot, Pipedrive, and Salesforce. In split stacks, push reply events from both tools to the same CRM contact record via Zapier before scaling past 50 active contacts.
Common Failures
What breaks: 4 failure modes and fixes
Tool Fit
Single-stack vs split-stack: tool options and prices
Single-stack tools manage both channels in one builder with native reply gating. Split-stack pairs give deeper per-channel controls, connected via Zapier or Make at the cost of manual webhook configuration.
| Tool | Price | Key feature for this workflow | Type |
|---|---|---|---|
| La Growth Machine | approx. €100/identity/mo | LinkedIn, email, calls in one sequence; dedicated 5G proxy; native CRM sync | Single-stack |
| lemlist | $109/mo/user | LinkedIn + email + WhatsApp, lemwarm included, unified inbox | Single-stack |
| Reply.io | $89/mo + $69 LinkedIn add-on | High email volume alongside LinkedIn touchpoints | Single-stack |
| Skylead | $100/mo | If/else Smart Sequences, image/GIF personalization across both channels | Single-stack |
| Expandi + Instantly or Smartlead | $99/mo + email tool cost | Dedicated country-based IP for LinkedIn; strong deliverability on email side; Zapier bridge required | Split-stack |
Split-stack pairs require cross-channel exit webhooks configured manually on both sides. Set up and test both directions before enrolling any live contacts.
Need to pick the right tool for this sequence?
The LinkedIn automation shortlist compares single-stack and split-stack options by channel support, safety controls, reply-gate logic, and pricing.