Node 18.x and 20.x Runtimes Deprecated for Chatflow Custom Code Snippets

Developer Support
1

Node 18.x and 20.x are being deprecated as supported runtimes for Chatflows custom code snippets. If you have bot code snippets running on either of these versions, you need to upgrade them to Node 24.x before August 31st, 2026, or you will lose the ability to edit those snippets until the upgrade is completed.

What’s Changing

Node 18.x and 20.x have reached end of life and no longer receive security patches. To keep Chatflows custom code snippets on a secure, maintained foundation, HubSpot is deprecating support for these runtimes in favor of Node 24.x, the current long-term support (LTS) release.

To make upgrading easier, you can now change the Node.js runtime version of an existing bot code snippet in-place, without deleting and recreating the snippet. In the bot snippet editor, look for the option to change the runtime version. Your code, environment variables, and configuration are preserved through the switch. This capability is rolling out gradually over the next 2 weeks.

example of updating node version

After August 31st, 2026, any snippet still running on Node 18.x or 20.x will become read-only. You won’t be able to edit it until you upgrade the runtime to a supported version.

When Is It Happening?

Upgrade your Chatflow bot code snippets to Node 24.x before August 31st, 2026. After that date, snippets on unsupported runtimes will be locked from editing until upgraded. The in-place runtime switching feature is rolling out to Data Hub Professional and Enterprise customers now.

2

Hey @dennisedson, Keeping Chatflows on a supported Node.js runtime is definitely the right move for both security and long-term maintainability.

For anyone planning the upgrade, I’d recommend this approach:

  1. Audit your Chatflows to identify snippets still running on Node 18.x or 20.x.

  2. Switch the runtime to Node 24.x using the new in-place upgrade option - your code, environment variables, and configuration stay intact.

  3. Test each snippet in a staging or test chatflow, especially if you’re using third-party packages or Node-specific APIs.

  4. Republish and validate the end-to-end bot experience before the August 31, 2026 deadline.

The in-place runtime switch is a great improvement - it removes the need to recreate snippets and makes upgrading significantly less disruptive. A quick compatibility check now can help avoid read-only snippets later.