Email + LinkedIn stack

Woodpecker + HeyReach: both channels, one view per rep

See Woodpecker email and HeyReach LinkedIn activity per rep in one dashboard. Prospects with a LinkedIn URL in Woodpecker merge with the matching HeyReach lead.

Start 7-day free trial Talk to us

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

The question this page answers

What does each rep's week look like when the emails go out of Woodpecker and the LinkedIn touches go out of HeyReach?

Why Woodpecker and HeyReach do not line up on their own

Woodpecker knows each prospect's email address (and LinkedIn URL when you stored one), the campaign, and when the prospect was last contacted.

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: SMTP mailboxes in Woodpecker, LinkedIn sender accounts in HeyReach. Neither has a row for the rep who works both.

Both tools are thin on timestamps in their APIs: Woodpecker reports a prospect's last contact time, HeyReach a lead's current connection state. Lining the two up by hand means comparing two snapshots, not two activity logs.

How OutboundManager joins Woodpecker and HeyReach

Woodpecker leads sync as contacts identified by the prospect's email address, plus the LinkedIn URL when the prospect has one. HeyReach leads sync as contacts identified by the lead's LinkedIn profile URL, plus the email address when the HeyReach lead has one.
Two records become one contact when they share an email address or, failing that, the same LinkedIn URL (normalised to linkedin.com/in/ form).
Woodpecker is the one email sender here that can carry a LinkedIn URL on the prospect. When it does, the prospect and the HeyReach lead merge on that URL even if HeyReach has no email for them.
Woodpecker sends are tied to the SMTP mailbox, and each mailbox is mapped to a rep. 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.
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.
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.
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 prospect is stored in Woodpecker with an email address and a LinkedIn URL, and is also a lead in a HeyReach campaign. On sync the two records resolve to one contact through the LinkedIn URL, so the Woodpecker emails and the HeyReach invite and messages belong to one person. Without the LinkedIn URL on the Woodpecker prospect, and with no email on the HeyReach lead, the same person would be two contacts.

What you can see once both are connected

Woodpecker sends beside HeyReach invites, accepts and messages for each rep, built from regular syncs of both tools
Woodpecker inbox replies and HeyReach conversation replies in one queue, each answered through the tool that received it
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 Woodpecker

Make sure the API key add-on is active on your Woodpecker account. Without it, Woodpecker refuses API access.
In Woodpecker, go to Marketplace → Integrations → API keys and create a key.
In OutboundManager, an admin opens Settings → Connections and clicks Add connection.
Pick Woodpecker. Paste the API key. It is checked against the tool automatically; click Save once it shows Key works. The key is stored encrypted.
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.

Woodpecker integration: what syncs and its limits Woodpecker documentation (opens in a new tab)

Connect HeyReach

In HeyReach, open the workspace you want to report on and go to Settings → Integrations → API. Create a workspace API key.
Use a workspace key, not an organization key. Organization keys cannot read campaign data, and the connection test says so.
In OutboundManager, an admin opens Settings → Connections and clicks Add connection.
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.
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 limits HeyReach documentation (opens in a new tab)

After both are connected

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.
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.
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

WoodpeckerWoodpecker's API has no per-email send events, only each prospect's last contact time. Each sync records every prospect's latest step, which catches each step as it goes out unless two reach the same prospect between syncs; a backfill only sees each prospect's latest step.
WoodpeckerA prospect contacted in two or more synced campaigns cannot be attributed to one of them and is skipped.
WoodpeckerThe inbox only covers mailboxes connected by the key's owner. LinkedIn steps of multichannel campaigns are not synced.
WoodpeckerWoodpecker processes one API request at a time per account, so syncs are slower on large accounts.
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.

Woodpecker + HeyReach questions

We also run LinkedIn steps inside Woodpecker. Are those counted?

No. LinkedIn steps of multichannel Woodpecker campaigns are not synced. LinkedIn activity on this pair comes from HeyReach.

How exact are the dates when neither API logs every event?

HeyReach messages and replies have exact timestamps. Woodpecker steps are picked up by the next sync after they go out. HeyReach invites and accepts get an approximate time the first time they are seen, and that time is never moved afterwards.

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

No. The rep scorecard, the campaign table and the weekly report work with just Woodpecker 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 Woodpecker 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 Woodpecker and HeyReach in one set of numbers.