HeyReach → Attio: LinkedIn activity where the CRM can see it

Running LinkedIn outreach outside the CRM means two parallel realities. HeyReach thinks one thing, Attio thinks another, and your reps are the expensive bridge between them. We wire HeyReach into Attio the same way we wire Lemlist: list-driven enrollment, replies as activities on the Person, connection-accepted events flipping the status, opt-outs applied globally across all channels.

Direction

Attio ↔ HeyReach (enrollment, replies, connections)

Stack

HeyReach API, Attio API, n8n, Slack

The what

What this integration actually does

Build a list in Attio → enroll in the mapped HeyReach campaign. Connection requests, accepts, replies, and opt-outs flow back into Attio as Person activities and field updates. Cross-channel suppression means someone who opted out via email won't get LinkedIn'd the next week.

The how

How we build it

1
Map Attio lists to HeyReach campaigns by ICP segment.
2
Enrollment workflow: Attio list membership → n8n → HeyReach campaign API.
3
Webhook back from HeyReach on connection accepted, reply, mention, opt-out.
4
Merge cross-channel state: a Person opted out of Lemlist is automatically suppressed from HeyReach.
5
Hot-reply routing: positive LinkedIn replies ping the right AE in Slack, same as Lemlist.

Under the hood

What lives inside the pipeline

LinkedIn profile URL captured as a Person field on first touch.
Connection-accepted event flips Person status (cold → warm).
Cross-channel dedup: no Person is in both a Lemlist and HeyReach active campaign simultaneously.
Reply sentiment on LinkedIn is harder than email - we default to human review on reply notifications.
Opt-outs (LinkedIn or email) suppress globally.

Hard-earned lessons

What we learned the hard way

LinkedIn rate limits are brutal. HeyReach handles them, but your enrollment pipeline must respect daily send limits or campaigns pause.
Matching LinkedIn profiles to Attio People by email isn't reliable - LinkedIn rarely exposes email. Match by name + company domain with human fallback.
Connection accepts are not replies. Don't treat a connection as engagement signal - only a real reply counts.
LinkedIn's TOS changes every six months. HeyReach stays on top of it; your integration should not try to clever its way around LinkedIn rules.

Case study

B2B SaaS client running multichannel outbound

Problem

Email outbound was in Lemlist, LinkedIn outbound was in HeyReach, and the two tools didn't know about each other. Same prospects were getting hit on both channels in the same week.

Solution

Unified Attio as the source of truth. Enrollment logic lives in Attio, HeyReach and Lemlist both pull from it, cross-channel suppression prevents overlap.

Outcome

Reply rate improved meaningfully once prospects stopped feeling spammed. Reporting finally showed true channel performance.

FAQ

Questions we get

Yes - "send LinkedIn connect on day 1, email on day 3, LinkedIn message on day 7" is exactly the kind of sequence Attio + n8n can drive across both tools.

Same architecture. HeyReach is our reference because it's what we run and it has the cleanest API of the three.

HeyReach uses their cloud infrastructure and human-like sending patterns. We've never had an account flagged - but LinkedIn's rules can change, so respect daily limits.