TL;DR
Recent Sales Email Replied Date only fires on mail reaching a connected inbox. Cold replies land on your sending domains, so that field stays permanently empty — and any report built on it reads zero.Every outbound team eventually hits the same wall. The cold email tool says 40 replies this month. The LinkedIn tool says 60 conversations. HubSpot shows a pipeline that appears to have materialised from nowhere, reports that credit none of it, and a lead scoring model that cannot see a single positive reply. The data is technically "synced." It is just not in a shape HubSpot can do anything with.
This post is the plumbing guide. What each tool actually writes into HubSpot, the one HubSpot mechanic that determines whether any of it is usable, the four ways to build the pipe with real costs, and the specific failures that follow from getting it wrong.
Two adjacent posts cover the neighbouring problems, so this one does not repeat them: our Clay + HubSpot integration guide covers pushing enrichment data into the CRM, and our HubSpot lead scoring setup guide covers what to do with the signals once they land. This post is strictly about the return path: getting engagement and reply data out of your sending tools and into fields HubSpot can act on.
Every integration behaviour below was read from the vendor's own help center or HubSpot's own documentation, with source behaviour stated as each vendor states it. Where vendors contradict themselves or each other, we say so rather than picking the tidier answer. Claims we could not confirm on a first-party page are flagged directional. Product gating and pricing change — verify before you buy a tier for a feature.
Write outbound engagement into HubSpot as two things at once: a logged activity for timeline visibility, and a set of custom contact properties for automation. Trigger your workflows on the properties, never on the activity. Then route on a datetime property such as a last-reply timestamp, which is re-enrollment-eligible, rather than on the engagement record, which is not.
If you use HeyReach, its native integration already does most of this correctly and publishes its field map. If you use Smartlead, the native integration gets you deals and activities but leaves properties for you to build. If you use Instantly, there is no native activity logger to rely on — you are building the pipe yourself or buying one.
HubSpot supports activities as a filter enrollment trigger. You can start a workflow from a logged note, a one-to-one email, a call or a meeting. That much works, and it is why the naive setup appears to work in testing.
Then HubSpot's re-enrollment documentation states the constraint flatly: "Activities and activity properties cannot be used for re-enrollment." For workflows on objects other than contacts, the wording is "activities and lists cannot be used for re-enrollment." HubSpot also documents that a record will not re-enroll while it is still enrolled — re-enrollment happens only when a record moves from not matching to matching a trigger.
Why this is fatal specifically for outbound. Inbound is mostly a one-shot event — a form fills once, and a workflow fires. Outbound is a repeating relationship with the same person: they reply to sequence one in March, ignore sequence two, reply again in September. Every one of those replies matters and needs to reach a rep. With an activity-only setup, only the March reply ever triggers anything. September is silent, and nothing errors — which is precisely why teams do not catch it for months.
A custom contact property does not have this limitation. Property values are the primary re-enrollment mechanism in HubSpot, with only calculation properties carved out. So the architecture writes itself: the reply becomes a datetime property that gets overwritten on every reply, and the workflow re-enrolls on that property changing.
Logging the engagement properly is still worth doing, because HubSpot maintains a set of read-only rollup properties off the back of it. Per HubSpot's default contact properties documentation, Last Activity Date tracks the most recent logged note, call, tracked sales email, meeting, LinkedIn/SMS/WhatsApp message or chat. Last Contacted, Number of Times Contacted and Number of Sales Activities move similarly. Those are useful for hygiene, dormancy filters and rep dashboards — and you get them at no extra cost once activities are logged as real engagements rather than notes.
This is where the vendors differ far more than their marketing pages suggest.
| Tool | Writes contact properties? | How activities land | Direction | Documentation quality |
|---|---|---|---|---|
| HeyReach | Yes — auto-creates a dedicated property group, all identifiers published | 12 toggleable timeline activities + a structured conversation Note | One-way to HubSpot | Best in category |
| Smartlead | Only ones you build yourself first | Split: sends/replies as Email activities, opens/clicks/bounces/unsubscribes as Notes | Two-way (pulls from a List or View) | Setup documented, no field map |
| Lemlist | Field mapping exists; direction configurable (directional) | Sends/replies as Email objects; LinkedIn messages as LinkedIn Message objects; everything else as Notes | Two-way options | Good activity map, internal contradiction |
| Instantly | Only via per-action Automations you configure | No documented native activity logger | Pulls in; pushes via Automations/webhooks | No field map published |
Smartlead's native integration enriches HubSpot with leads, deals, updates and activities, and can pull leads into campaigns from a HubSpot List or View with field mapping. The detail that matters is in its own setup article, and it is asymmetric: sent emails and replied emails are tracked as Email activities, while opens, link clicks, unsubscribes and bounces are tracked as Notes.
That distinction is not cosmetic. An Email engagement is a first-class CRM object with direction and status fields; a Note is a body of text. If your reporting or list logic assumes clicks are queryable engagement data, it will quietly return nothing.
Two more Smartlead specifics worth knowing before you build. Its deal automation creates deals at a chosen stage for a chosen lead category, and its documentation is explicit that it does not move deals between stages — stage progression stays yours to automate, which is where our HubSpot deal stages guide for outbound teams picks up. And for leads uploaded to Smartlead by CSV rather than pulled from HubSpot, Smartlead warns that you must also push those leads into HubSpot or no activity tracking will attach to them at all. Half-populated CRMs after a CSV campaign usually trace back to exactly this.
Custom fields are not auto-provisioned. Smartlead instructs you to create the properties in HubSpot first, grouped under a property group, before its data has anywhere to go. If you are already running Clay upstream of Smartlead, our Clay to Smartlead handoff guide covers the enrichment side of that same field-mapping problem.
HeyReach's HubSpot integration is the most transparent in this category, and it is the model to copy. It auto-creates a dedicated property group on the Contact object spanning attribution, exposure, engagement and intent, and it publishes every field identifier — including heyreach_reply_received, heyreach_reply_count, heyreach_first_reply_date, heyreach_last_reply_date, heyreach_time_to_first_reply, heyreach_intent, heyreach_positive_intent_count and heyreach_last_activity_date. Fields are documented with their update behaviour: set once, overwrites, or increments.
Those are exactly the property shapes the previous section argued for — a datetime you can re-enroll on and a counter you can score on, rather than a note you can only read.
On the activity side it writes 12 toggleable timeline activities, split into recommended (on by default, described as essential for accurate reporting) and optional. Message Sent, Message Received, InMail Sent and InMail Received all share a single event identifier and are distinguished in the HubSpot UI by a message-type property — worth knowing before you build a report expecting four separate event types. Connection request cards also flag whether a personalised message was included. Separately, it writes a LinkedIn conversation transcript as a HubSpot Note titled after the contact, appended rather than duplicated across campaigns, and associated to the Contact only — HeyReach states these notes are never associated with companies or deals.
Three constraints to plan around. It matches contacts by email and states it updates existing contacts only. LinkedIn profile data — name, company, job title, profile URL — is explicitly not synced in the current version, which is a real gap given that LinkedIn is where that data is richest. And each HeyReach workspace needs its own independent HubSpot connection, which matters if you run client workspaces. For choosing the tool itself, see our LinkedIn automation tools comparison.
An unresolved contradiction inside HeyReach's own docs. Its property article and its setup FAQ both say the integration updates existing contacts and does not create new ones. Its activities article refers to what happens "when HeyReach creates a new contact." We are not going to resolve that for you by guessing — test it in a sandbox before you assume either behaviour, particularly if contact-creation volume affects your billing or your data hygiene rules. Its published property count (20) is also one short of the identifiers actually listed on the page (21), so treat the count as approximate and the identifier list as authoritative.
Instantly presents two separate HubSpot connectors in its integrations tab, and its writeback path is not a background sync — it runs through Automations, where you assemble discrete HubSpot actions (create or update contact, create note, create task, create record, find contact) against Instantly triggers such as lead interest status changed, reply received, or a positive custom label. That is workable, but it means every field that lands in HubSpot is one you explicitly configured, and there is no documented native engagement logger behind it.
The most quotable fact here is that Instantly's own help center documents a third-party tool as the route for logging Instantly data as CRM activity. When a vendor's documentation points outside itself for the core integration job, that is the clearest possible signal about the native connector's scope. Note also that Instantly's webhooks — the foundation of any custom build — are documented as available on the Hyper Growth plan or above. Budget for that tier before you design around webhooks. If you are still choosing between platforms, our Smartlead vs Instantly comparison covers the sending side.
| Route | Published cost | Best when | Main limitation |
|---|---|---|---|
| Native integration | Included (tier gating varies and is often unpublished) | HeyReach, or Smartlead where deals + basic activities are enough | You get the vendor's data model, not yours |
| Dedicated sync layer (e.g. OutboundSync) | $99/mo (2,000 sent messages), $249/mo (10,000), $499/mo (25,000); billed on sent events only | Multiple sending tools into one CRM model | No public field map — you cannot design against it before buying |
| n8n | Cloud from €20/mo (2,500 executions) annually; self-hosted Community Edition free for internal business use | You want exact control of the field map and per-execution pricing | You own it forever; one active HubSpot trigger webhook at a time |
| Zapier / Make | Zapier Professional from $19.99/mo annual; Make Core from $9/mo | Low volume, or you need breadth of prebuilt connectors | Per-task and per-credit billing scales badly with send volume |
Three notes on that table that will change what you pick.
The billing unit matters more than the sticker price. n8n charges per workflow execution regardless of step count; Make charges a credit per module action; Zapier charges per task. A twelve-step enrich-and-sync workflow is one n8n execution and roughly twelve Make credits. At outbound volumes that gap compounds fast. Our n8n vs Make vs Zapier comparison works through the economics properly.
Connector availability is uneven, and this is a real constraint. Instantly has genuine apps on both Zapier and Make — and Make's Instantly app documents the same Hypergrowth plan gate for API access. Smartlead has an app on Make, but we could not confirm a first-party Smartlead app on Zapier; the plausible URLs return 404 and Zapier's own community threads point users at generic webhooks instead. Plan for Smartlead-on-Zapier meaning raw webhooks (directional — verify against Zapier's current app directory).
OutboundSync bills on sent events only — its pricing page is explicit that replies, opens, clicks and warmup activity do not count against the quota, which for a high-send/low-reply motion is the favourable direction. It writes contacts and companies and stores events as activities and timeline events, and states that leads and deals are untouched unless you build a HubSpot workflow. What it does not publish anywhere is a field map or property list, which is the one thing a technical buyer most needs. Its integration pages also describe custom properties as optional — so if you buy it expecting re-enrollment-eligible fields by default, confirm that during trial.
This is the build we would ship, in order. It assumes HubSpot Professional; the tier gates are called out where they bite.
datetime for last outbound reply, a number for reply count, a single-select for reply sentiment or intent, a datetime for last outbound touch, and a text field for last campaign name. Custom property limits are generous on paid tiers — HubSpot's catalog publishes 1,000 custom properties per object on Starter, Professional and Enterprise, against just 10 total on Free. Free portals cannot do this properly.POST /crm/v3/objects/emails with a required hs_timestamp, using hs_email_direction of EMAIL for your sends and INCOMING_EMAIL for replies, and hs_email_status from the documented set including SENT and BOUNCED. This is what moves the rollup properties and what a rep actually reads.POST /events/v3/send, which accepts up to 1,250 requests per second and batches of 500, with 50 properties per occurrence. But they do not give you a re-enrollment-eligible field, so they supplement properties rather than replacing them.On throughput: you will almost certainly not hit HubSpot's API ceiling. A private app gets 190 requests per 10 seconds with a documented daily cap of 625,000 on Professional and 1,000,000 on Enterprise, against 250,000 on Free and Starter. (Directional note: HubSpot's live usage-guidelines page states 625,000 for Professional, while a large volume of third-party writing repeats 650,000. We are citing what the page says today rather than the figure in circulation.)
1. Recent Sales Email Replied Date will never populate from cold outbound. HubSpot defines it as the last time a contact sent an email to your connected personal or team email. Cold replies arrive at your sending domains, which are not connected inboxes. Any dashboard, list or score built on that property reads zero forever and looks like a data problem rather than a definitional one. Use your own datetime property.
2. "Custom behavioral events are Enterprise-only" is a retired claim. HubSpot's current knowledge base lists custom events at Professional and Enterprise across six hubs, and the event definitions API states Professional tier or higher. Most guides on this topic still say Enterprise. Note the reverse gate that is real: webhook-triggered workflow enrollment requires Data Hub Professional or Enterprise, which is the one that quietly blocks "just webhook it into HubSpot" builds.
3. n8n's HubSpot Trigger node allows one active webhook at a time. Its documentation is explicit that activating a second trigger stops the previous one. Any n8n build needing several HubSpot-side triggers should not lean on that node — drive it from a HubSpot workflow webhook action or a plain n8n webhook node and route internally.
4. Calls dialled outside HubSpot do not satisfy HubSpot's call scoring event. HubSpot documents that its Call ended event only includes calls initiated through HubSpot calling. Externally logged call engagements will not trigger it.
5. Your CSV-sourced leads may be tracking nothing. Smartlead's documentation is direct about this: leads uploaded by CSV need to be pushed into HubSpot as well, or activity tracking will not attribute to them. This is the most common source of the "half our campaign is missing from the CRM" complaint, and it is a hygiene issue as much as an integration one — see our CRM data hygiene guide for outbound teams.
Attribution. If outbound touches are notes, no attribution model can see them, and outbound gets credited as direct or organic — which is how working outbound programmes get defunded in budget reviews. Our B2B revenue attribution guide covers that misallocation.
Reporting. HubSpot's custom report builder is Professional and Enterprise and refreshes roughly every two hours. It can surface event fields under the Events section of certain data sources — but it cannot report on something that exists only as note text.
Reply handling SLA. A positive reply that triggers no routing workflow sits until someone opens the sending tool. That is the most expensive failure in the list — the handling side is covered in our guide to handling cold email replies.
One caveat on measurement: do not rebuild your model on opens regardless of how cleanly they sync. Apple Mail Privacy Protection has made per-contact open data unreliable, as our Apple Mail Privacy Protection explainer unpacks. Sync replies, meetings and clicks; treat opens as decoration.
Worth stating plainly, because it explains why this stays unsolved in so many portals. HubSpot publishes no first-party guidance whatsoever on ingesting third-party cold email or LinkedIn outreach data — no reference architecture, no object model, no worked example. It also does not enumerate which logged activities are selectable as lead scoring criteria, or catalogue the report builder's data sources; both are discoverable only in your own portal. Meanwhile Smartlead offloads its webhook catalogue to an off-domain document, Instantly publishes no field map, and the dedicated sync vendors publish no property identifiers. HeyReach is the exception. If this feels like it should be a solved, documented problem — it should be, and it is not.
Not from the logged activity alone. Activities and engagements can be used as filter enrollment triggers, but HubSpot documents that activities and activity properties cannot be used for re-enrollment, and a record will not re-enroll while it is still enrolled. That means the first reply can fire a workflow and subsequent replies cannot. The fix is to have your integration stamp a custom datetime property such as a last-outbound-reply field alongside the logged activity, and build re-enrollment on the property instead.
Both, because they serve different consumers. The logged email engagement is what a rep reads on the record, and it automatically updates HubSpot's read-only rollups including Last Activity Date, Last Contacted, Number of Times Contacted and Number of Sales Activities. The custom property is what your automation reads, because it is the only one of the two that supports workflow re-enrollment. Treating them as alternatives rather than as a pair is the most common design mistake in this integration.
Per Smartlead's own setup documentation, sent emails and replied emails are tracked as Email activities, while opens, link clicks, unsubscribes and bounces are tracked as Notes. It can also create deals at a chosen stage for a chosen lead category, though it explicitly does not move deals between stages. Custom fields are not auto-created — you build the properties in HubSpot first. And leads uploaded to Smartlead by CSV must also be pushed into HubSpot or no activity tracking will attribute to them.
Both, and it is the best-documented integration in this category. HeyReach auto-creates a dedicated property group on the Contact object covering attribution, exposure, engagement and intent, and publishes every field identifier along with whether each one is set once, overwritten or incremented. It also writes 12 toggleable timeline activities and a structured LinkedIn conversation note associated to the contact only. Two limits to plan around: it matches by email and states it updates existing contacts only, and LinkedIn profile data such as name, company and job title is not synced in the current version.
Professional or above, not Enterprise — the Enterprise-only claim is a retired figure still repeated widely. HubSpot's knowledge base lists custom events at Professional and Enterprise across six hubs, and the event definitions API documents Professional tier or higher. Published limits include 500 event definitions, 50 custom properties per event and 50 properties per occurrence. The separate gate that catches people is webhook-triggered workflow enrollment, which requires Data Hub Professional or Enterprise.
Because HubSpot defines that property as the date a contact last sent an email to your connected personal or team inbox. Cold outbound replies arrive at your dedicated sending domains, which are not connected inboxes, so the property never populates no matter how many replies a campaign generates. Anything built on it — a list, a report, a score — will read zero indefinitely. Create your own reply-timestamp property and write it from your integration or middleware instead.
Running cold email or LinkedIn outreach into HubSpot and not sure whether your reply data is actually reaching your workflows? Start with our HubSpot lead scoring setup guide for what to do with the signals once they land, or talk to our team. We build and run cold email, LinkedIn outreach and HubSpot RevOps systems for B2B teams — and this integration layer is where most of the value gets won or lost.
By the GenFlows GTM engineering team. HubSpot mechanics, limits and tier gates were read from HubSpot's own knowledge base, developer documentation and published Product and Services Catalog at the time of writing. Integration behaviour is stated as each vendor documents it on their own help center. Where vendors contradict themselves or third-party sources, the conflict is named rather than resolved. Claims we could not confirm on a first-party page are flagged directional in-text. Gating and pricing change — verify against your own portal and current vendor pricing before purchasing. Last updated August 2026.