Every outbound motion generates the same quiet waste: leads who replied once, went cold, or got auto-tagged "not interested" — and then just sat there. That's pipeline you already paid to create, going stale because nobody has time to re-engage it well.
Re-engaging it well is the catch. A good re-engagement picks up the actual conversation — what you pitched, what they said, why it stalled. Doing that by hand means re-reading every old thread, one lead at a time. So reps either fire a generic "just circling back" that gets ignored, or the cold list never gets touched.
This Twain + n8n + HeyReach workflow removes the tradeoff. It reads each cold lead's real prior conversation and drafts a re-engagement that continues the thread — not a cold open — in seconds. The draft lands in Slack and the lead flows into a HeyReach list ready to send. You stay the sender.
The cold-lead graveyard
Cold leads aren't bad leads. They're people who once engaged — a reply, a connection, a "not right now" — and then dropped off the radar. Re-engaging them is some of the cheapest pipeline you can get, because the relationship already exists.
But it doesn't scale by hand, for one reason: the context lives in the thread. To write a re-engagement that lands, you have to re-read what was said and pick it back up. Across a whole list of cold leads that's hours of scrolling old conversations. So two things happen:
- Reps send a generic "just following up" that reads like it forgot the entire conversation — and gets ignored.
- Or the cold list just sits there, and the pipeline you paid for quietly dies.
Neither is fixed by "sending more." The fix is to make the context-aware re-engagement the easy one — the message that actually goes out.
The outcome: a re-engagement that remembers
Point the workflow at your cold leads, and for each one Twain reads the actual prior conversation and drafts a message that continues it — referencing what was discussed instead of opening cold.
What used to be "scroll the old thread, remember where it stalled, write something that doesn't sound like a form letter" becomes a draft — ready in seconds — that already reads like the next message in a real conversation.
How it works
Two n8n workflows, kept deliberately simple.
A dispatcher runs on a schedule (or on demand). It pulls your HeyReach conversations, keeps the leads worth re-engaging, skips the ones you've already handled, and hands each remaining lead off to be processed on its own.
For each lead, a second workflow does the real work: it sends that lead's prior conversation to Twain, Twain drafts a re-engagement that continues the thread using your campaign's agent, and the result is added to a HeyReach list, posted to Slack for review, and tagged so it won't be picked up again.
Running one lead per execution keeps each one isolated — a single bad profile can't stop the batch, every lead gets its own clean log, and the whole thing scales by just adding leads.
Not "just following up"
The difference between this and a mail-merge "circling back" is that Twain actually reads the conversation. It formats the prior thread into a clean chat log — kept on the lead in Twain — and feeds it in as context, so the model writes the next message in that relationship: acknowledging what was said, addressing the reason it went quiet, and moving it forward.
That's the whole point of re-engagement: the message has to prove you remember. A generic nudge proves the opposite.
You choose who gets re-engaged
You decide which leads qualify with two simple lists of tags — no code. Include the statuses worth re-engaging (say, Cold or an auto-tag like Not interested), and exclude anyone you've already touched.
That exclude list is also the dedup: once a lead is re-engaged it gets tagged, and the next run skips it automatically. No one is messaged twice, and reruns are safe.
Straight into HeyReach
Each drafted message rides into a dedicated HeyReach re-engagement list as a personalization field, so a HeyReach campaign can send it as-is. The lead lands in the list with its message attached — you just point a campaign at the list.
You stay the sender
Nothing goes out on its own. Every drafted re-engagement is posted to Slack for a human to read, and the lead is staged in a HeyReach list — not blasted. You review, then send from your own account. The speed of automation, with a human on every message.
Where it fits
This earns its place wherever cold pipeline piles up faster than anyone can re-engage it:
- Founder-led and SDR motions — turn a backlog of cold threads into warm, personal re-engagements without the scroll-and-rewrite.
- HeyReach users — it reads your inbox, drafts per lead, and hands the leads back into a list you campaign from.
- Teams wary of automation — you get the speed and stay the human who approves every message.
What each re-engagement says, and how it reads, is decided entirely in Twain — describe the job once in plain language and every cold lead gets a message built to that brief. See Campaign Brief and Deep Research to go deeper.