Clay for LinkedIn outreach: how to connect Clay and HeyReach
Using Clay for LinkedIn outreach comes down to one handoff. Clay doesn't send LinkedIn messages, and HeyReach doesn't build lists.
Clay is where you find, enrich and qualify people. HeyReach is where you send, from one or many LinkedIn profiles. Connecting the two takes a few minutes.
What decides your results is everything you build in between. This guide covers the workflow we use, the fields worth mapping, a worked example of one lead moving through the whole setup, and the mistakes that quietly kill reply rates.
How do Clay and HeyReach work together?
Clay builds and qualifies the prospect list, then pushes each approved lead, with its custom fields, into a HeyReach campaign through a native integration, where HeyReach sends the connection requests and messages from your LinkedIn profiles. Clay owns the data. HeyReach owns the sending.
A little more on each:
- Clay is a data and workflow platform. You bring in companies or people, then add columns that enrich, research, score and filter each row. It pulls from many data providers and can run AI research on each lead.
- HeyReach is a LinkedIn outreach tool built for multiple senders. You connect several LinkedIn profiles, build a sequence, and it spreads activity across them, with one shared inbox for replies.
The workflow, in six stages
1. Seed the table
Every Clay workflow starts with a seed list. Common sources:
- A Sales Navigator search
- An export from your CRM
- A list of target accounts
- A signal source, such as companies hiring for a role or recently funded
If you're running signal-based outbound, the seed is the signal. You start with accounts where something changed, not with everyone who fits.
2. Enrich the company, then the person
Enrich in two layers. Company first: size, industry, location, tech used, recent news. Then the person: current title, seniority, time in role, LinkedIn URL.
Clay can try several data providers in order until one returns a result. That waterfall approach improves coverage, but every lookup costs credits. Only enrich the columns you'll actually filter on or write with.
3. Turn qualification into columns
This is where most of the value sits. In Clay, every qualification rule becomes a column that answers one question. Then a final column adds them up.
| Clay column | What it checks | Output |
|---|---|---|
icp_fit |
Industry, size and region match | Yes / No |
buyer_role |
Title and seniority can buy or influence | Yes / No |
signal_live |
A relevant signal inside your freshness window | Yes / No |
in_crm |
Already a customer or open deal | Yes / No |
competitor |
Works at a competitor | Yes / No |
recently_contacted |
Contacted in the last 90 days | Yes / No |
send_ok |
All fit checks pass, all exclusions clear | Yes / No |
Only rows where send_ok is Yes move on. A smaller list of the right people beats a long list of maybes every time.
4. Write the personalization fields
Generate one or two short fields per lead, not a full message:
reason_line: one sentence on why now, based on the signalpain_line: the problem that signal usually points to
A short prompt turns the signal into one plain sentence. Keep both fields short and plain. Nobody reading them should be able to tell a tool wrote them. Then check a sample of 20 to 30 rows by hand before anything goes out. AI fields fail quietly, and you only notice when replies don't come.
5. Push to HeyReach
Create the campaign in HeyReach first. Clay's integration adds leads straight into an existing campaign, so the sequence and senders need to be set up before you push. Then map your Clay columns to custom variables in HeyReach. The names have to match what your sequence uses.
| Clay column | HeyReach variable | Used in |
|---|---|---|
first_name |
{first_name} |
Connection note |
company_name |
{company} |
Message 1 |
reason_line |
{reason_line} |
Message 1 |
pain_line |
{pain_line} |
Follow-up |
linkedin_url |
Profile URL | Required to send |
Don't let the push run on every new row automatically. Add an approved column, check rows by hand, and only push rows marked Yes. Once a lead reaches a running campaign, it can start sending, so this check is your last chance to catch bad rows.
6. Run, pace and route replies
In HeyReach, assign sender profiles, set working hours and keep daily volume steady. New profiles need warming before they send at full pace. Our rules for that are in LinkedIn outreach without getting restricted.
When replies arrive, tag them in HeyReach as interested, not now or not a fit. Interested leads go to whoever takes the call within 24 hours. "Not now" leads get logged back in Clay with a date to revisit, so a fresh signal on that account can bring them back.
A worked example: one lead, end to end
Here's how a single row moves through the setup. Say you sell a payroll and compliance tool to companies expanding in the Gulf. The person and company are illustrative.
The seed. Your signal source flags a logistics software company that just announced an office in Riyadh. That's an expansion signal, one of the categories we cover in LinkedIn buying intent signals.
Enrichment. Clay adds the company details (180 staff, Series B, based in Dubai) and finds the person most likely to own the problem: Omar, Head of Finance and Operations, eight months in role.
Qualification. Every column checks out. The company fits the ICP, Omar's role can buy, the signal is two weeks old, he isn't in the CRM, and nobody has contacted him in 90 days. send_ok is Yes.
Personalization. Clay writes the two fields:
reason_line: "Saw the team is opening in Riyadh, which usually means a lot of new process to set up fast."pain_line: "Payroll and compliance tend to get messy fast once a second country goes live."
HeyReach. Omar's row gets a quick manual check in Clay, then the push sends him into the campaign. His connection note uses only {first_name} and the Riyadh news. Message 1, after he accepts, uses {reason_line} and ends with one light question about whether Saudi payroll setup is on his plate this quarter.
The reply. Omar answers "Good timing, we're mid-rollout." HeyReach tags it interested, and it reaches your sales lead the same day.
Notice what Clay did and didn't do. It never wrote the whole message. It decided whether Omar should hear from you at all, and gave the message one specific reason. The sequence and the sending stayed in HeyReach.
Six mistakes we see in Clay to HeyReach setups
- Personalizing on the headline. Everyone does it, so it reads as automation. Personalize on the reason to talk, not the job title.
- Long AI-written openers. Short openers read as human. A paragraph that summarizes someone's profile reads as generated.
- No suppression columns. Messaging an existing customer or a competitor's employee costs more than a missed lead.
- Pushing the whole table. Filter on
send_okfirst. If a row doesn't pass, it doesn't go to HeyReach. - Overlap across senders. When several profiles share a campaign, make sure one person isn't contacted by two of them. Also decide who sends to whom: if you leave the sender field empty in Clay, HeyReach spreads leads randomly across the campaign's senders.
- Spending credits on columns you never use. Every enrichment should feed a filter or a message. If it doesn't, delete it.
What this setup can produce
Across programs our team has run with this kind of stack, we reached 10,251 decision makers, made 3,390 new connections (33% acceptance) and got 977 replies, with 440 interested buyers. In one AI SaaS program, that turned into more than 60 qualified demos in 12 weeks.
The tools didn't do that on their own. Targeting, suppression and message discipline did. The tools made it repeatable. Full numbers are in our LinkedIn outreach benchmarks.
Should you build it or hire it?
Build it yourself if you have someone who enjoys working in Clay tables, time to test messaging every week, and a founder or rep ready to take calls.
Hire it out if outbound keeps sliding down the priority list, or you'd rather approve messaging than manage the system. Either way, tool costs (Clay credits, HeyReach seats) sit on top of any service fee, so check current pricing for both before you budget.
FAQ
Does Clay have a native HeyReach integration? Yes. You can send leads from a Clay table straight into a HeyReach campaign, with custom fields mapped to HeyReach variables. The campaign has to exist in HeyReach first.
Can Clay send LinkedIn messages on its own? No. Clay prepares the data. A LinkedIn tool such as HeyReach does the sending.
Do I need Sales Navigator? It helps as a seed source, but it isn't required. You can start from a CRM export, an account list or a signal source.
How many leads should I push at once? Only as many as your senders can contact in a week or two. Signals go stale while leads sit in a queue.
Is HeyReach safe for my LinkedIn account? Any LinkedIn tool carries some risk. Safe pacing, warmed profiles and good targeting reduce it far more than the choice of tool.