HubSpot custom code actions on Node.js 20 after Nov 17

From November 17, 2026, any HubSpot workflow custom code action still on Node.js 20 keeps running but can’t be edited. If one breaks after that date, someone has to rewrite it for Node.js 24 before it can be fixed.

For an owner, the code isn’t the risk. The risk is that nobody on your team can say which actions exist, what they touch, or who wrote them.

We’re ProfitPad, a HubSpot partner. We write custom code actions for clients, which is why this deadline is on our list too.

What happens and when

November 3, 2026: no new custom code actions on Node.js 20. Node.js 24 is available.
November 17, 2026: you can’t save changes to existing Node.js 20 actions. Rolling an upgraded action back to Node.js 20 only works before this date.
After November 17: Node.js 20 actions keep running. HubSpot hasn’t announced a date when they stop.

Actions still on Node.js 16 are already deprecated. You can’t save changes to one until it’s on a newer version.

What’s at risk in your portal

Custom code actions do the jobs native workflow actions can’t, like copying contacts and companies onto a new deal, checking an address before it’s saved, or reshaping data before it reaches the ERP. They run quietly, so nobody looks at them until a number is wrong.

After November 17, a Node.js 20 action that breaks can’t be patched. The fix is a rewrite and a test, on the day you need it working. If the person who wrote it has left, that day gets longer.

Three questions for whoever runs your portal

How many workflows use a custom code action, and what does each one do?
Which ones touch orders, quotes, ERP data or record ownership?
Who is upgrading them, and will it be done before November 17?

If nobody can answer the first question, start there.

How to upgrade HubSpot custom code actions to Node.js 24

For the admin or developer who maintains your portal.

Three things change.

The handler. Node.js 20 actions hand back results through a callback. Node.js 24 only accepts async handlers that return the result.
The libraries. @hubspot/api-client moves from version 11 to 13.4.0, and axios to 1.13.5. A major version jump can change how calls work.
The request library is gone. Use axios or the built-in fetch().

The handler change, in a simple action:

// Node.js 20
exports.main = async (event, callback) => {
  const dealId = event.object.objectId;
  // ...work...
  callback({ outputFields: { result: "success" } });
};

// Node.js 24
exports.main = async (event) => {
  const dealId = event.object.objectId;
  // ...work...
  return { outputFields: { result: "success" } };
};

Every callback(...) becomes a return, including the one in your error handling. HubSpot says Breeze can make the update. Read what it changed and test it anyway.

The order of work:

Rank by damage. Actions touching orders, quotes, ERP data or record ownership go first.
Upgrade one at a time. Run each on a real test record and check that later workflow steps still get the outputs they read.
Finish before November 17, while a rollback to Node.js 20 is still possible.

If you’re reviewing the rest of the portal at the same time, work through our HubSpot audit checklist.

Not sure what’s running in your portal? Request your free HubSpot audit →

If your website uses serverless functions built in the design manager, those have a separate deadline. They stop running February 1, 2027.

FAQ

Will my HubSpot custom code actions stop working on November 17?

No. Existing custom code actions on Node.js 20 keep running after November 17, 2026. What stops is editing: from that date, you can’t save changes to a Node.js 20 action. HubSpot hasn’t announced when Node.js 20 actions stop running, so upgrade them now, while a rollback is still possible.

Can I just switch a custom code action to Node.js 24?

Not safely. Node.js 24 only accepts async handlers that return the result, so any action that uses a callback needs its code changed. The HubSpot API client also moves from version 11 to 13, and the request library is removed. Change the code, then test each action on a real record.

Can Breeze upgrade custom code actions for me?

Yes, HubSpot says Breeze can update a custom code action to Node.js 24. Treat the result as a first draft. Read what changed, check library calls against the new versions, and test it on a real record. Any action that touches orders, quotes or ERP data deserves a person’s review first.

Does this affect serverless functions on my HubSpot website?

Yes, on a different timeline. Serverless functions built in the design manager stop running February 1, 2027, and calls to their endpoints fail after that. HubSpot can’t migrate them for you. Each one has to be rebuilt in a developer project, and the templates and modules that call it pointed to the new path.

HubSpot custom code actions on Node.js 20: what changes November 17