What this does
For each cold lead in HeyReach, Twain reads the actual prior conversation and drafts a re-engagement that continues the thread, referencing what was discussed instead of opening cold. The draft lands in Slack for review, and the lead flows into a HeyReach list ready to send. Nothing goes out on its own, you stay the sender.
Why it helps
Cold leads are cheap pipeline, because the relationship already exists. But a re-engagement that lands has to prove you remember the conversation, and re-reading every old thread by hand does not scale. So reps send a generic "just circling back" that gets ignored, or the cold list never gets touched. Twain reads the thread and drafts the next message in seconds.
How it works
It runs as two simple n8n workflows:
A dispatcher runs on a schedule (or on demand). It pulls your HeyReach conversations, keeps the leads worth re-engaging, skips the ones you have already handled, and hands each remaining lead off one at a time.
A per-lead 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 will not be picked up again.
Running one lead per execution keeps each one isolated, so a single bad profile can't stop the batch and every lead gets its own clean log.
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 have 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.
Where the draft lands
A card in Slack for a human to read.
A dedicated HeyReach re-engagement list, with the drafted message attached to the lead as a personalization field, so a HeyReach campaign can send it as-is. You just point a campaign at the list.
You review, then send from your own account.
What you need to set this up
An n8n instance
Your Twain API key, added in n8n as a Header Auth credential (see API access)
An existing Twain campaign and Agent set up for re-engagement
A HeyReach connection (with API key) and a Slack connection in n8n
For how the native HeyReach integration works, see Connect Twain to HeyReach.
Read the full walkthrough
For the step-by-step setup, see the blog post: Re-engage Cold Leads With Messages That Remember the Conversation.
How this differs from Twain Workflows
This is not the same as the built-in Workflows feature inside Twain. This setup calls the Twain API directly from n8n workflows you build and host yourself, so it runs outside the app.