What This Update Actually Is
HubSpot is ending support for Node 18.x and Node 20.x as available runtimes inside Chatflows custom code snippets. The deadline is July 13, 2026.
Custom code snippets let you run JavaScript logic directly inside a chatflow, things like pulling external data, formatting values, or triggering conditional branches. Right now, those snippets can run on Node 18.x, 20.x, or 24.x. After July 13, only Node 24.x will be supported.
This isn't a soft warning. Snippets still running on Node 18.x or 20.x after the deprecation date will stop working. That means chatflow branches that depend on custom logic will fail silently or error out.
Why HubSpot Shipped This
Node 18.x reached its end-of-life date in April 2025. Node 20.x will reach end-of-life in April 2026. Once a runtime hits end-of-life, it no longer receives security patches from the Node.js project.
Running unpatched code on a customer-facing chat tool is a real security risk, not a theoretical one. Any vulnerability discovered in Node 18.x or 20.x after those dates simply won't get fixed.
Node 24.x is the current long-term support release. It's actively maintained and will receive security patches for years. HubSpot is moving the platform to a foundation that's actually safe to build on.
The external frustration here is real: most humans who built these chatflows years ago didn't think about runtime versions. They just wrote the code, tested the bot, and moved on. Now there's a deadline with a technical migration attached, and that feels like a surprise tax on work that was already done.
How to Use It Step by Step
HubSpot doesn't auto-migrate these snippets. You need to do it manually. Here's exactly how:
- Go to Conversations, then Chatflows in your HubSpot portal.
- Open each chatflow that contains a custom code snippet. Check the runtime version listed on the snippet block.
- Copy the full code from any snippet running on Node 18.x or 20.x. Paste it somewhere safe, like a text editor, before you touch anything.
- Add a new custom code snippet block to the same chatflow. Select Node 24.x as the runtime.
- Paste your saved code into the new snippet. Don't assume it's a clean copy/paste. Some Node 18.x and 20.x syntax is not valid in Node 24.x.
- Run HubSpot's built-in snippet tester and walk through the chatflow manually. Confirm every branch that touches the snippet still resolves correctly.
- Delete or archive the old Node 18.x or 20.x snippet once the new one is confirmed working. Don't leave both active in the same flow.
One practical flag: if your snippet uses older CommonJS patterns like require() in ways that have been deprecated in newer Node versions, or if it relies on any third-party packages, test especially carefully. Behavior differences are most common around async handling and module imports.
What It Touches in Your HubSpot Strategy
This update is scoped to one specific tool: custom code snippets inside Chatflows. But the downstream effects are wider than they first appear.
If your chatflow uses custom code to set contact properties, route conversations, call webhooks, or pull in external data, those results feed into your CRM. A broken snippet doesn't just stop the bot. It can produce missing property values, failed enrollments into workflows, or skipped lead routing steps.
Key Takeaway
A failed custom code snippet in a chatflow doesn't always throw a visible error. It often just returns nothing. That means properties don't get set, workflows don't enroll, and leads slip through without a single alert fired.
On the reporting side, if your chatflow feeds data into contact records or deal pipelines, corrupted inputs from a broken snippet will surface as data quality issues later. We've seen this pattern in portals where one quiet automation failure quietly distorts months of pipeline data before anyone notices.
This is also a good moment to audit every custom code snippet in your portal, not just chatflows. If you're using custom code in workflows or other automation tools, check the runtimes there too. HubSpot has been steadily modernizing its runtime support across the platform.
If you're managing several platform changes at once this month, the June 2026 HubSpot updates roundup covers the full picture of what's shipping and what has a deadline attached.
Key Takeaway
Don't wait until July 12 to start this migration. Give yourself time to test. Broken chatflow logic in a live bot is a customer-facing problem, not just a back-end one.
For RevOps teams who are already working on data hygiene and property management, the habit of auditing automation tools regularly pays off here. The same discipline that helps you manage calculated properties and avoid CRM bloat applies directly to keeping your custom code snippets clean and current.
Who Should Care Most
This update is gated to Data Hub Professional and Data Hub Enterprise. If you're not on one of those tiers, custom code snippets in chatflows aren't available to you and this doesn't apply.
If you are on those tiers, here's who needs to act:
- Operations leads and RevOps managers who own the chatflow architecture and automation layer
- HubSpot admins responsible for keeping automations healthy and documented
- Developers or technical consultants who wrote the original snippet code and understand the logic
- Service and support teams who rely on chatflow routing to get conversations to the right place
Company size matters less than portal complexity here. A 20-person company with one sophisticated chatbot can be more exposed than a large team with simple, code-free chatflows. If you built custom logic, you need to act.
George's Take
I'll be honest: this is the kind of update that gets ignored until it becomes an incident. Humans who build sophisticated chatflows tend to move on once the bot works. They don't schedule a date to revisit runtime versions. But the portals I've seen that flourish long-term are the ones where someone owns the health of the automation layer, not just the strategy layer. This is a clean, low-drama migration if you do it now. It becomes a real problem at 9pm on a Tuesday if you don't.
“The portals that flourish aren't the ones with the most automations. They're the ones where someone actually maintains what was built.”
This also isn't the only July deadline HubSpot has on the calendar right now. If you haven't reviewed the July 31 Notetaker and meeting record changes, those need attention too. Stack your prep work now so you're not scrambling across multiple tools at the same time.
If you've got custom code snippets and you're not sure where to start, or if you're not certain what's running in your portal right now, we can help. Book a strategy call with the Sidekick team and we'll audit your automation layer so nothing breaks quietly on July 13.
Frequently Asked Questions
What happens to my HubSpot chatflow if I don't migrate from Node 18.x or 20.x by July 13, 2026?
Any custom code snippet still running on Node 18.x or 20.x will stop working after the July 13, 2026 deprecation date. The chatflow branches that depend on that logic will fail. Properties may not get set, workflows may not enroll, and leads can slip through without any visible error alert.
How do I migrate my HubSpot chatflow custom code snippet to Node 24.x?
Open your chatflow, copy the code from your existing snippet, and create a new code snippet block in the same flow. Select Node 24.x as the runtime, paste your code in, and test carefully. Some Node 18.x and 20.x syntax may not be compatible with Node 24.x, so manual testing is required before you delete the old snippet.
Which HubSpot plans are affected by the Node 18.x and 20.x deprecation for chatflows?
This deprecation affects Data Hub Professional and Data Hub Enterprise customers. These are the tiers that have access to custom code snippets inside Chatflows. If you're on a different tier without custom code access, this change doesn't apply to your portal.
Why is HubSpot deprecating Node 18.x and 20.x for chatflow custom code?
Node 18.x and 20.x have reached end-of-life status and no longer receive security patches from the Node.js project. Running unpatched runtimes on customer-facing tools introduces real security risk. Node 24.x is the current long-term support version and receives ongoing security maintenance.
Will HubSpot automatically migrate my chatflow snippets to Node 24.x?
No. HubSpot does not auto-migrate custom code snippets. You need to manually create a new snippet using Node 24.x, transfer your code, test it for compatibility issues, and delete the old snippet. Give yourself enough time before July 13 to test thoroughly in a live chatflow environment.
Can I just change the runtime version on my existing snippet instead of creating a new one?
HubSpot's migration guidance says to create a new snippet and select Node 24.x as the runtime, rather than editing the runtime on the existing snippet. Always test after migrating since syntax differences between Node versions can cause code that previously worked to behave differently or fail.
