Find every HubSpot serverless function and Node.js 20 custom code action

HubSpot serverless functions end of life: the dates

HubSpot announced the change in its developer changelog on 3 November 2026 (HubSpot developer changelog, checked 5 November 2026; also posted in the HubSpot Community).

• Design manager serverless functions: since 3 November 2026 you cannot create new ones. From 17 November 2026 you cannot edit existing ones. On 1 February 2027 they stop running, and requests to /_hcms/api/ endpoints fail.
• Workflow custom code actions on Node.js 20: since 3 November 2026 you cannot create new ones. From 17 November 2026 you cannot save changes to existing Node.js 20 actions. Existing Node.js 16 and 20 actions keep running; HubSpot recommends moving them to Node.js 24, which still receives security updates.

How to find all custom code actions in workflows

HubSpot’s upgrade guide does this by hand, one workflow at a time (Upgrade custom code actions to Node.js 24, checked 5 November 2026):

1. Go to Automation > Workflows.
2. Add an Action type filter at the top of the table and choose Custom code.
3. Open each workflow in the list with Edit workflow.
4. Click each custom code action and check its Language dropdown. Actions set to Node.js 16 or 20 need an upgrade.

Save a copy of each action’s code outside HubSpot first. The guide then offers Upgrade with Breeze, which updates the custom code actions of a workflow to Node.js 24 (review its changes before you save), or a manual upgrade: choose Node.js 24.x, make exports.main an async function that returns its result instead of calling callback, check the libraries you use, then test the action and save.

Design manager serverless function migration to developer projects

HubSpot’s migration guide moves each function into a developer project, where it is served from /hs/serverless/ instead of /_hcms/api/ (Migrate design manager serverless functions to projects, checked 5 November 2026). Finding what to migrate is the first phase:

1. List your functions with hs cms function list and note each endpoint, method and secret.
2. Back up your design manager files with hs cms fetch and look for folders ending in .functions.
3. Search the backup for _hcms/api and for the last part of each endpoint path, because paths are often built at runtime.
4. Check the HTML outside your templates too: site and blog header and footer HTML, each page’s head and footer HTML, and rich text and HTML modules.
5. On the live site, filter the browser’s Network tab on _hcms/api to see which requests your pages make.

Then, one function at a time, the callers change from /_hcms/api/ to /hs/serverless/ with the rest of the path unchanged. The guide lists Content Hub Enterprise and HubSpot CLI 8.4.0 or later as prerequisites.

What the scan will do

• List the design manager serverless functions in a portal, with the pages, templates and modules that call /_hcms/api/.
• List every workflow custom code action with its runtime, and flag the ones on Node.js 16 or 20.
• Give one checklist per portal as CSV, ready to hand to your team or to a client.
• Read only: it will not change anything in your portal.

This is a plan, not a product yet. We will build it if enough people ask for it, and only with what HubSpot’s APIs let us read without changing anything. It is for HubSpot admins, RevOps teams, and agencies and Solutions Partners who look after several portals.

Get early access