How teams use HeyReach with Tapistro
Teams running LinkedIn outreach through HeyReach use Tapistro to feed their campaigns automatically. A Journey qualifies prospects using your signals, filters, and AI Agents, then adds them to a HeyReach campaign, so connection requests and messages go out without anyone building lists by hand.
HeyReach works in both directions in Tapistro: as a Destination that receives prospects from a Journey, and as a Source that brings LinkedIn engagement back in.
Before you connect
HeyReach sends all outreach through LinkedIn accounts, so connect your LinkedIn accounts (senders) in HeyReach first. Each sender has an ID in HeyReach that Tapistro uses when assigning leads.
Connect HeyReach
Go to Connections in Tapistro and select HeyReach.
Paste your HeyReach API key.
Save the connection. Tapistro validates the key with HeyReach automatically, so an invalid key is caught at setup.
Send prospects to a HeyReach campaign from a Journey
Open your Journey and add a Destination step.
Select HeyReach.
Pick the campaign from the dropdown. Tapistro fetches your campaign list live from HeyReach, so you don't need to copy campaign IDs.
Pick the sender from the dropdown in the same Destination step. This is the LinkedIn account the outreach for these leads will come from, fetched live from your HeyReach senders.
When the Journey runs, every person who reaches the Destination step is added to the selected HeyReach campaign under that sender.
How leads are tied to LinkedIn accounts
HeyReach ties every lead to one LinkedIn account. All activity for that lead, from the connection request through every follow-up message, comes from that same account. That's why each Destination step carries a sender: it decides which LinkedIn account owns the leads that flow through it.
Round robin your leads across multiple senders
To spread outreach volume across your LinkedIn accounts instead of sending everything from one, split your lead set with a decision node and give each branch its own Destination step.
Two things to decide first:
Whether the round robin is based on accounts or persons. Account-based keeps everyone from the same company with the same sender; person-based distributes individuals regardless of company.
The number of buckets, which is the number of senders you want to distribute across.
For an account-based round robin across three senders, add a decision node with three branches:
Branch 1:
java_string_abs_hashcode(domain) % 3 = 0Branch 2:
java_string_abs_hashcode(domain) % 3 = 1Branch 3:
java_string_abs_hashcode(domain) % 3 = 2
Connect each branch to its own Destination step, each configured with the same HeyReach campaign setup but a different sender. The hash assigns every lead to exactly one branch and always the same branch, so each lead stays with its assigned LinkedIn account for all activity while the volume is shared roughly evenly across the three.
For a pure person round robin, use email_id instead of domain in the branch conditions. To distribute across a different number of senders, change the number of branches and replace 3 with that number in each condition.
Bring HeyReach engagement back into Tapistro
When someone accepts a connection request or replies, HeyReach sends that engagement back to Tapistro. To capture it, create a new Source and select HeyReach LinkedIn Engagement as the source type. Tapistro then:
Creates contacts from the lead's email and LinkedIn URL
Discovers the account from the email domain and enriches it through the standard enrichment pipeline
Attributes each contact to the HeyReach source, so you can route engaged leads into follow-up Journeys