HeyReach HubSpot Integration: Setup, Fields & Gaps

LinkedIn outreach produces some of the best conversations in outbound, and some of the worst data hygiene. Replies sit inside the LinkedIn automation tool, reps work in HubSpot, and unless the two are connected, the pipeline report cannot tell you which deals started on LinkedIn.

HeyReach is one of the tools most agencies use for multi-account LinkedIn sending, and it has a native HubSpot integration. This guide explains what that integration does, the limits that catch teams out, and what to build when it is not enough. For the email side of the same problem, see our Smartlead and Instantly HubSpot integration guide.

Sourcing note: HeyReach behaviour below comes from HeyReach's help article and its HubSpot Marketplace listing, both read on 5 October 2026. The two sources disagree in places, and we say where. Plan and price details can be stale, so confirm in your account. Anything we could not confirm is marked (directional), and build patterns are our own recommendation.

The Short Answer

Use the native integration when your LinkedIn leads already exist in HubSpot with an email address, for example leads you enriched in Clay before the campaign. Use a webhook flow or Clay in the middle when leads come from LinkedIn searches with no email, because the native sync will skip them and will never create the contact. Many agencies run both: native for rich timeline activity, webhooks for everything the native route cannot reach.

Native vs Webhook vs Clay at a Glance

How the Native Integration Works

Setup

In HeyReach, open Integrations, click the HubSpot card (labelled Beta in the help article), click Connect and complete HubSpot's OAuth screen. There is no API key. HeyReach then creates a custom property group in your HubSpot account.

Triggers

You choose when a lead syncs. HeyReach's help article lists two triggers: when a lead is added to a campaign, and when a reply is received. The HubSpot Marketplace listing describes three, adding "when added to a list" and calling first reply the recommended default. The two sources disagree, so check which options your account shows. If you want the fewest false records in HubSpot, sync on reply rather than on campaign add.

What gets written

The integration adds properties in four groups, according to HeyReach's help article:

• Attribution: first touch date and the first campaign.
• Exposure: how many campaigns the lead is in and the last sender.
• Engagement: reply status, reply count and timing.
• Intent: sentiment direction from HeyReach's auto-tagging.

The marketplace listing says the property group holds 20 fields. The help article also says ten event types can be logged to the contact timeline, including connection requests, messages, replies, campaign additions and sends from third-party tools. Per the listing, message content is saved as notes.

Limits to Plan Around

• Not retroactive. Only activity after you connect is synced, so connect before launching campaigns, not after.
• Deleted contacts stay deleted. If you remove a contact in HubSpot, later HeyReach triggers will not recreate it.
• One connection per workspace. Agencies running client workspaces must authorize HubSpot separately in each one, which also keeps client data isolated.
• One-way sync. The help article describes HeyReach to HubSpot. The listing calls it bidirectional because HubSpot lists can be used as campaign sources, which is a separate feature from the activity sync.
• Plan gating. The help article does not name a plan. The listing says Growth, Agency or Unlimited, with Growth shown at $79 per seat monthly or $59.25 billed yearly (directional, may be stale). See our HeyReach pricing guide for current plans.

When Leads Have No Email: Webhooks

HeyReach supports webhooks for events such as connection request accepted, message reply received, InMail replies, tags and profile views. A third-party guide from OutboundSync lists the events and notes that each webhook covers one event and a campaign, that failed deliveries are retried up to five times in 24 hours, and that there are no user-facing webhook logs (directional, third-party source). Build your own alerting for failures.

A reliable pattern, which is our recommendation rather than HeyReach documentation:

1. Trigger: a connection-accepted or reply-received webhook into n8n, Make or Zapier. Use the every-reply event or the first-reply event, not both, to avoid double logging.
2. Create a unique property in HubSpot called "LinkedIn Profile URL" with unique values required. HubSpot allows up to 10 unique-value custom properties per object, and the setting can only be chosen when the property is created.
3. Search then upsert: look up the contact by LinkedIn URL, then by email if you have one, and update or create.
4. Log the activity as a note or engagement, and set source and campaign properties.
5. Create a deal on a positive reply and assign an owner.

We did not verify whether HubSpot's API upsert by property works with custom unique properties, so test with a throwaway contact (directional). For picking the automation tool, see our n8n vs Make vs Zapier comparison.

Clay in the Middle

If email coverage is your real problem, fix it upstream. Enrich the LinkedIn list in Clay, write a deduplicated record to HubSpot first, then send the lead to HeyReach. The native integration then has an email to match on, and the HeyReach properties land on a contact that already exists. Our guides to pushing Clay leads into HeyReach and syncing Clay with HubSpot cover each step.

Failure Modes to Test Before Launch

• Silent skips. Leads without email vanish from the sync. Check the activity log in HeyReach for failures.
• Duplicate contacts. The native sync does not create contacts, so duplicates usually come from your own webhook flow creating without a unique key.
• Double logging. Enabling both every-reply and first-reply events writes the same reply twice.
• Wrong intent. The intent properties rely on HeyReach's auto-tagging, so review positive replies manually before routing deals.
• Multi-sender conflicts. The last sender is stored as a property. How conflicting updates behave when one lead sits in two senders' campaigns was not verified (directional).

Keep LinkedIn volume inside safe limits too: see our LinkedIn outreach limits guide and the LinkedIn automation tools comparison. For the full cross-channel picture, read our guide to syncing cold email and LinkedIn data into HubSpot.

Frequently Asked Questions

Does HeyReach create contacts in HubSpot?

No. HeyReach's HubSpot listing says it does not create new contacts. It updates existing HubSpot contacts matched by email, so the contact must already exist in HubSpot.

Do I need an email address for the HeyReach HubSpot sync?

Yes. HeyReach's help article says a lead must have an email assigned for the contact update, and leads without one are not synced. For email-less leads, use webhooks keyed on the LinkedIn profile URL, or enrich emails in Clay first.

What does the HeyReach HubSpot integration sync?

It writes custom properties for attribution, exposure, engagement and intent, and logs activities such as connection requests, messages, InMails and replies to the contact timeline. The sync runs one way, from HeyReach to HubSpot.

Is the HeyReach HubSpot sync retroactive?

No. Only activity after you connect the integration is synced. Connect HubSpot before launching campaigns, because earlier LinkedIn activity will not be backfilled.

How do I avoid duplicate contacts when syncing LinkedIn leads?

Create a unique-value custom property for the LinkedIn profile URL, search by it before creating a contact, and do not enable overlapping reply events. Email is HubSpot's default dedupe key where one exists.

Which HeyReach plan do I need for the HubSpot integration?

HeyReach's help article does not name a plan. The HubSpot Marketplace listing says Growth, Agency or Unlimited. Check HeyReach's current pricing page and your account before buying, since plans and prices change.

Want LinkedIn replies showing up in HubSpot as real pipeline? Read our multi-channel LinkedIn and cold email playbook, or talk to our team and we will build and run the cold email, LinkedIn and RevOps stack for you.

By the GenFlows GTM engineering team. Integration details from HeyReach's help center and HubSpot Marketplace listing and HubSpot documentation, checked 5 October 2026. Build patterns are our own recommendation. Last updated October 2026.