HeyReach Close CRM Integration: Options & Setup

If your team sells from Close, LinkedIn outreach has a familiar problem. Connection requests and replies live inside the automation tool, reps work in Close, and the CRM never shows that a deal started with a LinkedIn conversation.

HubSpot users get a native HeyReach integration. Close users do not appear to. This guide covers the options, what each one does and does not do, and a safe way to build the sync yourself. For the HubSpot equivalent, see our HeyReach HubSpot integration guide, and for the email side of Close, our Close CRM cold email integration guide.

Sourcing note: OutboundSync details come from its HeyReach–Close page, and Close object details from Close's developer docs, both read on 6 October 2026. HeyReach event names come from OutboundSync's HeyReach webhook guide. We could not open HeyReach's own webhook documentation, so we do not list payload fields. Anything we could not confirm is marked (directional), and the build pattern is our own recommendation.

The Short Answer

Use OutboundSync if you want LinkedIn activity in Close with the least build effort and can live with a one-way beta sync. Use HeyReach webhooks plus Zapier, Make or n8n if you want control over matching, field mapping and deal creation. Whichever you pick, the hard part is not the connection. It is deciding how a LinkedIn prospect maps onto Close's lead and contact model, and matching before you create.

Your Options at a Glance

OutboundSync: What It Does

OutboundSync's page describes a near-real-time log of HeyReach activity as Close lead activity. It lists eight activity types: connection requests sent and accepted, messages and replies, follows, post likes, profile views and tag updates, including auto-tags.

• Setup: a Close admin authorises the integration through the Close App Marketplace, you add your HeyReach API key, confirm contact matching, test with one event, then go live.
• Direction: one-way, HeyReach to Close. The page labels the pairing beta.
• Objects: it "matches or creates" Close leads. There are no prebuilt Smart Views, but you can build your own from the synced tag data.
• Plans: the page says webhooks and the API are included on all HeyReach plans.
• Limit: Close records cannot be used as a block list. That option is available only for HubSpot lists or Salesforce reports.

The DIY Route: HeyReach Webhooks

HeyReach lets you subscribe to events and receive an HTTP POST at an endpoint you choose. According to OutboundSync's HeyReach webhook guide, the useful events are: Connection Request Sent, Connection Request Accepted, Message Sent, Inmail Sent, Every Message Reply Received, Follow Sent, Liked Post, Viewed Profile, and the tag events (Lead Tag Updated and the auto-tag variants). The same guide suggests skipping campaign lifecycle events.

For most teams, three events are enough: Connection Request Accepted (a warm signal), Every Message Reply Received (the one reps must act on), and Lead Tag Updated (sentiment or status). Logging every profile view and like in the CRM adds noise without helping a rep decide what to do next.

We could not read HeyReach's own payload documentation, so check the exact field names in your account's test event before mapping. Pick your middleware using our n8n vs Make vs Zapier comparison.

Mapping LinkedIn Prospects to Close's Data Model

Close's developer docs describe a lead as a company or organisation that can hold contacts, tasks, opportunities and activities. A contact is an individual person and must be a child of a lead. Custom fields can be stored on leads, contacts, opportunities and custom activities. When you create a lead through the API, you can nest contacts and custom fields in the same request.

That model is built for company-first selling, and LinkedIn data is person-first. Pick one pattern and apply it everywhere:

Matching Before You Create

This is where most syncs go wrong. A LinkedIn tool will happily send a "reply received" event for someone Close already knows from cold email, and a naive flow creates a second lead.

1. Store a normalised LinkedIn URL in a custom field on the contact. Strip tracking parameters and trailing slashes, and lowercase it, so the same profile always produces the same string.
2. Search Close first. Close documents an advanced filtering API for finding leads or contacts by criteria. Search by LinkedIn URL, then by email.
3. Create only on a miss, and write the URL on creation so the next event matches.
4. Guard against repeat events. Webhooks can arrive more than once (directional), so store an event or message identifier and skip ones you have already logged.
5. Clean up with merge. Close has a merge-leads endpoint for the duplicates that slip through.

What to Write Into Close

Keep a single custom field such as "LinkedIn status" so reps can build a Smart View of replied prospects. Rate limits matter if you sync in bulk: Close applies limits per endpoint group, returns a RateLimit header, and expects you to wait for the reset value after a 429 response. We do not quote numbers because Close's page did not give any.

Before you scale any LinkedIn campaign, check your sending volumes against our LinkedIn outreach limits guide, and keep the CRM tidy with our CRM data hygiene guide.

Close or HubSpot for LinkedIn-Heavy Outbound?

If LinkedIn is a core channel and you want a native integration, the HubSpot route is simpler today, though it has its own gaps (we cover them in the HeyReach HubSpot guide). Close tends to win on calling and speed for small outbound teams (directional). Our Close vs HubSpot comparison covers that trade-off in full. If you enrich leads in Clay first, our Clay to HeyReach guide covers the upstream half, and the LinkedIn automation tools comparison covers the alternatives.

Frequently Asked Questions

Does HeyReach integrate natively with Close CRM?

We found no native HeyReach-built Close integration. We could not open HeyReach's CRM integrations article, so treat this as "none found" rather than a vendor-confirmed "none exists". The routes we found are OutboundSync (a third-party beta), Zapier, and HeyReach webhooks into a flow you build.

Can I sync LinkedIn replies into Close?

Yes. OutboundSync lists messages and replies among the events it logs as Close lead activity. With webhooks, HeyReach's "Every Message Reply Received" event can trigger a flow that writes a note on the matching Close lead.

How do I avoid duplicate leads in Close from LinkedIn campaigns?

Search before you create. Match on a normalised LinkedIn profile URL stored in a custom field, with email as a second key, and only create a lead when nothing matches. We did not find Close documentation describing automatic duplicate handling on lead creation (directional), so do not rely on it. Close has a merge-leads endpoint for cleanup.

Should a LinkedIn prospect be a Close lead or a contact?

In Close, a lead represents a company and contacts sit under it. Decide once: create a company lead with the prospect as a nested contact, or attach the contact to an existing company lead. Mixing both is the usual source of messy data.

Do I need a paid HeyReach plan for the Close sync?

OutboundSync states that webhooks and the API are included on all HeyReach plans, so the sync works on any of them. Plan terms change, so confirm in your own account before you buy.

Is the sync two-way?

OutboundSync is one-way, HeyReach to Close, and labels the pairing beta. Sending Close changes back to HeyReach, such as adding a lead to a campaign when a Close status changes, needs a separate Zapier or webhook flow.

Want LinkedIn and cold email activity flowing into Close or HubSpot without the duplicate mess? Start with our Close cold email integration guide, or talk to our team and we will build the sync for you.

By the GenFlows GTM engineering team. Vendor features and pricing change often, so confirm in your own accounts. Last updated October 2026.