Skip to content
OutboundManager
Sign inStart free trial

Email + LinkedIn stack

Lemlist + HeyReach: two LinkedIn tools, one count

Running LinkedIn outreach from both Lemlist and HeyReach? OutboundManager adds up invites, messages and replies per rep across both, next to Lemlist email.

Start 7-day free trialTalk to us

7-day free trial • No credit card required • 5-min setup

The question this page answers

We run LinkedIn from both Lemlist and HeyReach. How many LinkedIn touches and replies does each rep really have?

Why Lemlist and HeyReach do not line up on their own

Lemlist knows each lead's email address and LinkedIn profile, the campaign, and every email and LinkedIn step it ran for that lead.

HeyReach knows the lead's LinkedIn profile, the campaign, which LinkedIn account reached out, whether the invite was accepted and what was said in the conversation.

Each tool reports on its own channel, in its own dashboard, with its own idea of a sender: mailboxes and LinkedIn accounts in Lemlist, LinkedIn sender accounts in HeyReach. Neither has a row for the rep who works both.

This pair overlaps. Lemlist sends email and LinkedIn steps, HeyReach sends LinkedIn only, and one rep's LinkedIn profile may be connected to both. Each tool reports its own invites and messages, and a total for the rep exists in neither.

How OutboundManager joins Lemlist and HeyReach

  1. Lemlist leads sync as contacts identified by the lead's email address and LinkedIn profile URL. HeyReach leads sync as contacts identified by the lead's LinkedIn profile URL, plus the email address when the HeyReach lead has one.
  2. Two records become one contact when they share an email address or, failing that, the same LinkedIn URL (normalised to linkedin.com/in/ form).
  3. Lemlist leads carry both an email address and a LinkedIn profile URL, so they merge with HeyReach leads on the LinkedIn URL directly. This is the cleanest match of any email and LinkedIn pair.
  4. A Lemlist activity is tied to the team member's mailbox or LinkedIn account that sent it. When an activity carries no sender, the campaign owner gets the credit. Every HeyReach invite and message carries the LinkedIn account that sent it, and each account is mapped to a rep. Map both to the same rep and their email and LinkedIn work adds up on one row.
  5. Email replies and LinkedIn replies are classified from their text with the same rules: interested, not now, not interested, wrong person, opt-out or auto-reply.
  6. Every human reply from both tools lands in one queue. An answer written there goes out through the tool that received the reply, in the original thread or conversation.
  7. With HubSpot connected, each deal is credited to the most recent email sent, LinkedIn invite, LinkedIn message or call to any of the deal's contacts, before the deal was created and no more than 120 days before it, whichever of the two tools made it.

A worked example

A rep's LinkedIn profile is connected to Lemlist for a multichannel campaign and to HeyReach for a LinkedIn-only campaign. In one week Lemlist sends emails and invites, and HeyReach sends invites and messages. Lemlist reports its number and HeyReach reports its own. On the scorecard the rep has one LinkedIn figure that is the sum of the two, one email figure from Lemlist and one reply count across everything.

What you can see once both are connected

  • LinkedIn invites, accepts, messages and replies from Lemlist and HeyReach added up per rep, with Lemlist emails alongside
  • Lemlist LinkedIn campaigns and HeyReach campaigns in the same table, so the two tools can be compared on replies per touch
  • One reply queue for both tools, with assignment per rep and filters for interested, not now and the other classes
  • Combined touches per rep: emails sent plus LinkedIn invites and messages, with replies and positive replies across both
  • With HubSpot connected: which channel sourced each deal, and pipeline per campaign for email and LinkedIn alike
Reply queue with interested replies on the left and an open thread with a reply composer on the right

The unified reply queue: human replies from every tool, answered in their original thread. Demo data.

Set it up

Connect Lemlist

  1. In lemlist, open Settings → Integrations and generate an API key in the API section. The key acts as the user who created it.
  2. In OutboundManager, an admin opens Settings → Connections and clicks Add connection.
  3. Pick Lemlist. Paste the API key. It is checked against the tool automatically; click Save once it shows Key works. The key is stored encrypted.
  4. Open Settings → Reps & senders and give each sender a rep. Suggested matches by email are offered; re-mapping later moves the history with the sender.

Lemlist integration: what syncs and its limitsLemlist documentation (opens in a new tab)

Connect HeyReach

  1. In HeyReach, open the workspace you want to report on and go to Settings → Integrations → API. Create a workspace API key.
  2. Use a workspace key, not an organization key. Organization keys cannot read campaign data, and the connection test says so.
  3. In OutboundManager, an admin opens Settings → Connections and clicks Add connection.
  4. Pick HeyReach. Paste the workspace API key. It is checked against the tool automatically; click Save once it shows Key works. The key is stored encrypted.
  5. Open Settings → Reps & senders and give each sender a rep. Suggested matches by email are offered; re-mapping later moves the history with the sender.

HeyReach integration: what syncs and its limitsHeyReach documentation (opens in a new tab)

After both are connected

  1. Map senders to reps. In Settings → Reps & senders, give every mailbox, LinkedIn account, dialer seat and HubSpot owner a rep. Re-mapping later moves the history with the sender.
  2. Set weekly targets per rep on the same page, so the scorecard shows each number against a target and the overview flags reps under 60% of it.
  3. Add recipients or a Slack webhook for the weekly report in Settings → Report, so the combined numbers arrive every Monday. Connect HubSpot whenever you want meetings, pipeline and won revenue next to them.

Good to know

  • LemlistOpens, clicks, visits, likes, follows, WhatsApp, SMS, calls and manual tasks are not imported. Aggregate campaign stats are never turned into activity.
  • LemlistWhen an activity carries no sender, the campaign owner gets the credit.
  • LemlistLinkedIn replies can only be answered for campaign leads, because lemlist only messages leads.
  • Lemlistlemlist allows 20 requests every 2 seconds per key, so a large first backfill can take several sync runs.
  • HeyReachHeyReach only exposes each lead's current connection state, not the time of each invite or acceptance. OutboundManager fixes an approximate time the first time it sees the event and never moves it.
  • HeyReachProfile views, likes, follows and the InMail versus message split are only available as totals in HeyReach and are not synced.
  • HeyReachLeads removed from a campaign and deleted conversations are not seen.
  • HeyReachThe API key is shared across the workspace at 300 requests a minute.

Lemlist + HeyReach questions

A rep's LinkedIn account is connected to both tools. Is their activity counted twice?

The account appears as two senders, one per tool, because each tool reports the activity of its own campaigns. Map both to the same rep and their invites and messages add up on one row.

Which tool answers a LinkedIn reply?

The one that received it. An answer written in the reply queue goes back through the source tool. Lemlist can only message campaign leads, so Lemlist LinkedIn replies from people outside a campaign cannot be answered from the queue.

Do I need HubSpot for Lemlist and HeyReach to work together?

No. The rep scorecard, the campaign table and the weekly report work with just Lemlist and HeyReach. HubSpot is what adds meetings, deals, pipeline and won revenue; it is the only CRM supported today.

Does OutboundManager send any email or LinkedIn outreach itself?

No. It reads from Lemlist and HeyReach. The only thing it sends is an answer a person on your team writes in the reply queue, and that goes out through the tool that received the reply.

The two tools on this page

See all stacks · See all integrations

See Lemlist and HeyReach in one set of numbers.

Start 7-day free trialTalk to us

7-day free trial • No credit card required • 5-min setup

Lemlist and HeyReach are trademarks of their respective owners. OutboundManager is not affiliated with, endorsed by or partnered with Lemlist or HeyReach.