$ man how-to/heyreach-linkedin-automation
MCP Serversintermediate
HeyReach LinkedIn Automation
Set up HeyReach for multi-sender LinkedIn outreach with proper warming and campaign structure
What HeyReach Is
HeyReach is a LinkedIn automation tool built for multi-sender outreach. The core idea: connect multiple LinkedIn accounts to one workspace and run campaigns across all of them simultaneously. One person can manage 5, 10, 20 sender accounts from a single dashboard.
Why multi-sender matters: LinkedIn limits each account to roughly 100 connection requests per week and 150 profile views per day. One account caps out fast. Five accounts running the same campaign hit 500 connections per week. The math is straightforward. More senders means more pipeline.
HeyReach handles the rotation automatically. You build a campaign, assign senders, upload a lead list, and it distributes the outreach across accounts. It also manages warming, connection request limits, and response tracking per account.
CODE
Account Setup and Sender Configuration
Step 1: Create your HeyReach workspace at app.heyreach.io. One workspace per team or agency.
Step 2: Connect LinkedIn accounts. HeyReach uses a browser extension or cookie-based auth to link accounts. Each account becomes a "sender" in the workspace.
Warming rules for new senders:
Week 1: 10 connection requests per day, 30 profile views
Week 2: 15 connection requests per day, 50 profile views
Week 3: 20 connection requests per day, 80 profile views
Week 4+: 25 connection requests per day, 100 profile views
Do not skip warming. LinkedIn flags accounts that go from zero activity to 100 requests overnight. The warming period builds a natural activity pattern that keeps accounts safe.
Step 3: Set daily limits per sender in Settings > Sender Limits. Be conservative. 20-25 connection requests per day per account is the safe ceiling. Some accounts can handle more, but the risk of restriction goes up past 30.
PATTERN
Campaign Architecture
A HeyReach campaign has three components: the lead list, the sequence, and the sender pool.
Lead list: CSV upload or CRM sync. Each row needs a LinkedIn profile URL at minimum. Name, company, and title help with personalization variables. HeyReach deduplicates across campaigns automatically, so the same person does not get hit twice.
Sequence: The message flow. A typical outbound sequence:
Step 1: View profile (day 0)
Step 2: Send connection request with note (day 1)
Step 3: If accepted, send first message (day 2-3 after acceptance)
Step 4: Follow-up message if no reply (day 5-7 after first message)
Step 5: Final touch (day 10-14 after second message)
Connection request notes: keep them under 300 characters. Lead with why you are reaching out, not who you are. "Saw your team is scaling the SDR org - we built something for exactly that" beats "Hi, I am Shawn from GTMe OS and I would love to connect."
Sender pool: Assign 3-5 senders per campaign. HeyReach rotates which sender contacts which lead. This distributes the volume and makes the outreach pattern look more natural to LinkedIn.
PATTERN
Integrating with Clay
The real power is Clay feeding HeyReach. Clay enriches your lead list with company data, technographics, hiring signals, and custom scores. Then you push qualified leads directly to HeyReach campaigns.
The flow:
1. Clay table with enriched leads (company, title, LinkedIn URL, score)
2. Filter to qualified leads (score above threshold, title match, company fit)
3. Push to HeyReach via webhook or CSV export
4. HeyReach runs the LinkedIn sequence
5. Responses sync back to your CRM
For the webhook approach, Clay has an HTTP action that can POST to HeyReach API endpoints. Map the Clay columns to HeyReach lead fields: linkedin_url, first_name, last_name, company_name, title.
For the CSV approach: export from Clay, upload to HeyReach campaign. Less automated but works for batch campaigns where you want to review the list before launching.
PATTERN
Multi-Channel with Instantly
HeyReach handles LinkedIn. Instantly handles email. Running both on the same lead list creates a multi-channel sequence.
The routing logic depends on the lead. If you have a verified email, they go to Instantly for email outreach AND HeyReach for LinkedIn. If you only have a LinkedIn URL and no email, they go to HeyReach only. If the email domain uses aggressive spam filtering (Proofpoint, Mimecast), lead with LinkedIn through HeyReach and use email as the follow-up channel.
Timing matters. Do not blast both channels on the same day. Stagger them. LinkedIn connection request on day 1. Email on day 3. LinkedIn follow-up on day 7. Email follow-up on day 10. The prospect sees your name across two channels without feeling spammed.
Track which channel gets the response. Over time you will see patterns. Some industries respond better on LinkedIn. Some respond better to email. Let the data drive your channel allocation.
PRO TIP
Safety and Account Health
LinkedIn restricts accounts that behave like bots. HeyReach mitigates this with built-in limits and warming, but you still need to be smart about it.
Never exceed 25 connection requests per day per account. The hard limit from LinkedIn is around 100 per week, but spreading them across 5 days at 20 each is safer than doing 50 on Monday and 50 on Friday.
Use the accounts manually too. Post content, comment on posts, engage in groups. LinkedIn tracks overall activity patterns. An account that only sends connection requests and messages looks automated. An account that also posts and comments looks human.
Rotate senders periodically. If an account gets a temporary restriction, pull it from campaigns for 1-2 weeks. Let it cool down. Use the remaining senders to maintain campaign volume.
Monitor acceptance rates. A healthy acceptance rate is 30-50% for targeted outreach. Below 20% means your messaging or targeting is off. Below 10% and LinkedIn may start flagging the account.
Keep connection request notes genuine. Templates that sound like templates get ignored. Personalize the first line with something specific to the person or their company. HeyReach supports variables like {first_name}, {company_name}, and custom fields from your CSV.
related guides