If your HubSpot workflows use custom code, you have until November 17, 2026 to edit Node.js 20 actions. Here is what freezes, what keeps running, and how to move to Node.js 24.
request library. HubSpot offers an "Upgrade with Breeze" button, but says to review Breeze's changes.On November 3, 2026, HubSpot's developer changelog announced it is retiring older Node.js runtimes for workflow custom code actions, along with serverless functions built in the design manager. Custom code actions are the "run your own JavaScript or Python" step in workflows. HubSpot's docs list them for Data Hub Professional and Enterprise accounts. They are often how small teams patch gaps without paying for a separate automation tool.
The change happens in stages:
| Date | What changes |
|---|---|
| Nov 3, 2026 | No new Node.js 20 custom code actions. No new design manager serverless functions. |
| Nov 17, 2026 | No saving changes to existing Node.js 20 actions or design manager functions. Both keep running. |
| Jan 5, 2027 | Per the custom code docs, Python 3.9 actions can no longer be created or updated. HubSpot recommends Python 3.14. |
| Feb 1, 2027 | Design manager serverless functions stop running. Requests to /_hcms/api/ endpoints fail. |
Node.js 16 actions were already deprecated. You can't save changes to one until you switch its runtime.
HubSpot says existing Node.js 20 actions keep running after both dates, and it gives no date for them to stop. That sounds safe, but it means a frozen action: if an API changes, a field is renamed, or a bug shows up after November 17, you can't edit that code. You would have to rebuild it on Node.js 24 under pressure. HubSpot's guide also says rollback to Node.js 20 is possible only until November 17. Upgrading now gives you a way back if something breaks.
Design manager functions are a harder deadline. They stop on February 1, 2027. HubSpot says it can't migrate them automatically. They need to move into developer projects, where functions are served from /hs/serverless/ instead of /_hcms/api/. Any form, page or script calling the old path needs updating too.
Per HubSpot's upgrade guide, the main code changes are:
exports.main becomes an async function and returns { outputFields: {...} } instead of calling callback().request library. Use axios or the built-in fetch().aws-sdk is now included. Check each library's release notes for changes.throw the error in your catch block.One caution: when we checked, HubSpot's main custom code page still showed older library versions and callback-style examples. Use the dedicated Node.js 24 upgrade guide as the source of truth.
Actions still have a 20-second run limit and 128 MB of memory. If yours are close to that, it is a good moment to ask whether the logic belongs in HubSpot at all.
For most small businesses, no. If you already pay for Data Hub Professional and have only a few custom code steps, the upgrade is usually a short rewrite, and keeping logic inside HubSpot avoids another subscription and another failure point. The case for moving changes when you have many scripts mostly calling outside apps, or nobody on the team who can read JavaScript. A visual tool like Make or Zapier can be easier to maintain than code nobody understands. Our Make vs Zapier comparison covers the pricing tradeoffs, and our HubSpot review covers what each hub includes.
This article is researched from HubSpot's public changelog and developer documentation as of November 11, 2026, not hands-on testing. Dates and details may change, so confirm in your own portal before relying on them.
See what HubSpot's hubs include and where it fits for small teams.
Read our HubSpot review →