HubSpot custom code action Node.js 24: locked from November 17

Key takeaways
From November 17, 2026, HubSpot will not save changes to workflow custom code actions on Node.js 20. They keep running, but nobody can edit them. Admins of Data Hub Professional or Enterprise portals should find every custom code action, name an owner, then upgrade and test each one on Node.js 24.

From November 17, 2026, HubSpot will not let you save a change to a workflow custom code action that still runs on Node.js 20. The code keeps running, until the day someone needs to fix it and cannot.

The HubSpot custom code action Node.js 24 upgrade is a short job for whoever wrote the code. If your workflows use custom code, you have under two weeks to find that person.

What changed with HubSpot custom code actions and Node.js 24

HubSpot announced the change in its developer changelog on November 3, 2026. Node.js 20 and earlier no longer get security updates, so HubSpot is retiring them for workflow custom code actions.

  • Since November 3, 2026: new custom code actions cannot use Node.js 20.
  • From November 17, 2026: changes to existing Node.js 20 actions cannot be saved. Node.js 16 actions are already in that state.
  • After both dates: existing Node.js 16 and 20 actions keep running. HubSpot gives no date when they stop.

The same announcement retires design manager serverless functions, which stop running on February 1, 2027; that part belongs to your website developer.

What breaks on November 17 and what does not

Nothing stops on November 17. What ends is the ability to edit a Node.js 20 action: to fix a bug or change a mapping, someone first has to move it to Node.js 24.

That move is more than a dropdown. HubSpot’s upgrade guide explains that Node.js 24 does not accept callback-style handlers and that the bundled libraries changed versions, including a new major version of the HubSpot API client. The request library is no longer included.

The deadline also closes the safety net. Until November 17, a failed upgrade can be switched back to Node.js 20 with a saved copy of the old code. After that, the only way forward is a fix on Node.js 24. And workflow data restore does not reverse changes made by custom-coded actions.

Who must act

Only portals with custom code actions are affected. HubSpot’s list of workflow actions marks Custom code as Data Hub Professional and Enterprise only. The admin finds the actions, the developer or contractor who wrote them upgrades and tests, and RevOps or the revenue leader decides who owns each workflow from now on.

What to do before November 17

  1. Go to Automation > Workflows, add an Action type filter and select Custom code. Open each workflow and check the Language dropdown in every custom code action for Node.js 16 or 20.
  2. Put a name next to each action: who upgrades it and owns it afterward.
  3. Copy the current code of each action into a file or source control before anyone changes it.
  4. Create a dedicated test record: testing writes the action’s changes to the record you select.
  5. Upgrade one workflow at a time, with Upgrade with Breeze or by hand, then run Test action and check status, data outputs and logs before saving.

The guide recommends Breeze, which updates every custom code action in a workflow. The guide also warns that Breeze can make mistakes: compare its version with your saved copy and test before saving.

What to ask whoever wrote the code

  • What does the action do, in one sentence, and which records does it change?
  • Which outside systems does it call, and which secrets or tokens does it use?
  • Does it rely on the request library or on HubSpot API client methods that may have changed?
  • Who tests it before November 17, and who fixes it if it breaks?

If the author has left, ask whoever inherits the workflow. Our workflow audit gives every workflow an owner and a purpose; custom code actions are the place to start it.

Our take

We read every HubSpot deadline the same way: the date is HubSpot’s, the owner list is yours. The runtime switch is a developer task; knowing what each piece of code does and who answers for it is an admin and RevOps task.

The November 17 deadline does not break anything on the day. It freezes code nobody owns. The upgrade is small for the person who wrote the action. The risk is custom code left by a contractor or an admin who moved on, with no notes, that the team is afraid to open. So the first step is an owner per custom code action, and the upgrade comes second.

If an action has no owner and nobody can say what it does, do not let anyone, Breeze included, rewrite it under deadline pressure. Leave it running and decide in the workflow review whether it stays; HubSpot gives no date when Node.js 20 actions stop, so treat the freeze as temporary. The legacy API retirement in 2027 follows the same pattern on a longer clock.

HubSpot admin

No one owns HubSpot on your team?

We run your portal week to week: users, data, workflows, reports.

See how it works

FAQ

Will my HubSpot workflows stop working on November 17?

No. Node.js 20 custom code actions keep running after November 17, 2026; only saving changes stops. As of November 2026, HubSpot has not published a date when they stop running.

How do I find which HubSpot workflows use custom code?

In Automation > Workflows, filter the table by Action type and choose Custom code. Then open each workflow and check the Language dropdown of every custom code action for Node.js 16 or 20.

Can Breeze upgrade custom code actions to Node.js 24 for me?

Yes, Breeze can update all custom code actions in a workflow, and HubSpot recommends it, while noting that Breeze can make mistakes. Save the old code and run Test action on a test record before you save.

This week, run the Custom code filter and put a name next to every action on the list. The upgrades can follow; the names should not wait until November 16.

Alignify

Alignify is a HubSpot implementation and admin team. We set up portals, clean up CRM data and run HubSpot as a service for B2B companies.

On this page

Get the audit checklist

All 25 checks as a spreadsheet with auto-scoring.

By submitting, you agree to our Privacy Policy.

Talk to Alignify

45 minutes, your portal on screen, no slides. We show what we would fix first.

Want a second set of eyes on your HubSpot?

Book a 45-minute portal review. We look at your portal together on a screen share and show what we would fix first. No slides, no sales pitch.