HubSpot ends design manager serverless functions on 1 February 2027

HubSpot ends design manager serverless functions on 1 February 2027

3 November 2026: HubSpot will switch off serverless functions built in its design manager on 1 February 2027, after which requests to their /_hcms/api/ endpoints will fail. The company says they run on Node.js 18 or 20, which it cannot upgrade and which no longer get security updates. A second change, for workflow custom code actions on Node.js 20, shares two of the dates but does not end in a switch-off.

Not yet independently verified. HubSpot gives no end date for existing Node.js 20 custom code actions and no figure for how many customers use either feature. This rests on HubSpot's own changelog entry. We will update this when it can be confirmed, and remove this note.

Three dates for design manager functions

The sunset runs in stages, and the first has already passed:

• from 3 November 2026, no new design manager serverless functions can be created;
• from 17 November 2026, existing ones can no longer be edited, including staging and deploying packages through the design manager private beta;
• from 1 February 2027, they stop running.

Between the second and third dates the functions keep working, so the first sign of trouble for a site that does nothing will be on 1 February, when a form, calculator or lookup that calls one stops answering. HubSpot cannot migrate them for the owner, because each function's code and the pages that call it are specific to a site. The migration is a rebuild in a developer project, where the function is served from /hs/serverless/ instead of /_hcms/api/, followed by changes to every template, module and setting that calls the old path.

Code actions: new Node.js 20 blocked, old ones left running

For workflows, Node.js 24 is now available for custom code actions. From 3 November no new Node.js 20 actions can be created, and from 17 November changes to existing ones cannot be saved, as is already true for Node.js 16. Existing actions continue to run, and HubSpot states no end date for them. It warns that the upgrade is not only a version number: Node.js 24 does not support callback-style handlers, and the libraries available to the code have new versions, so each action needs updating and testing. Its Breeze assistant can update the actions in a workflow.

Developer projects on older platform versions

The same page reminds teams with functions in developer projects that the Node.js version follows the project's platform version. Projects on 2026.03 and 2026.09 run Node.js 24 and need nothing now. Those on 2023.1, 2023.2 or 2025.1 run Node.js 18 or 20 without security updates, and HubSpot says builds and deploys on those versions are already blocked; the fix is hs project migrate and a redeploy.

What is new since the CLI notice

This is separate from the end of Node.js 20 support in HubSpot's developer command line tool on 8 January 2027, which we covered in an earlier item. That change affects the tooling developers run; this one affects code already running inside customers' websites and workflows.

Related on TrustList:

• HubSpot developer CLI needs Node.js 22 or later from 8 January 2027

Sources

• HubSpot Developer Changelog: Sunsetting design manager serverless functions and older Node.js runtimes for custom code actions (updated 4 November), 3 November 2026