Quick win · Workflows and automation

Move HubSpot custom code actions to Node 24

HubSpot custom code actions on Node 20 can't be edited from 17 Nov 2026, and design-manager serverless functions stop on 1 Feb 2027. We move each action to Node 24, update the libraries it uses, and test it on a real record before switching it on. $49 per action, in 1 working day.

Do it yourself

Free. Try these first, in order.

  1. List every workflow with a custom code action and note the Node.js version set on each action.
  2. Copy each action's code and secrets list somewhere safe before you change anything.
  3. Switch the action's language version to Node.js 24 in the action editor.
  4. Check the code for libraries or syntax that changed between Node 20 and 24, and for any HTTP library calls that need updating.
  5. Use the action's test option with a real record and compare the output with the old version.
  6. Turn the workflow back on and watch the action logs for errors over the next day.

We do it

$49, 1 working day. An agent prepares, a RevOps specialist checks, you approve.

Scope

3
  • One custom code action per $49
  • Node 24 upgrade (newer code engine) with its libraries updated
  • A test on a real record before and after

Not included

2
  • Rewriting what the action does
  • Design-manager serverless functions (quoted separately)

We need

3
  • Read-only access first: a view-only user invite or private-app token
  • The workflows that use custom code
  • Edit rights after you approve the plan; all access removed when done

You get

3
  • Each action on Node 24, tested, with the test output saved
  • Before and after evidence: screenshots, record counts or test records
  • A root-cause note: what keeps causing this and how to stop it

Who does what

Work only moves right when the lane before it is done.

  1. AI

    AI agents audit and draft

    • Finds every custom code action and its Node version
    • Drafts the Node 24 changes
  2. Specialist

    A RevOps specialist signs off every change

    • Reviews the code changes
    • Tests on a real record and switches it on
  3. You

    You approve before anything goes live

    • Approve the plan before anything changes in your portal
    • Check the result and sign it off

Root cause

If this keeps coming up, custom code needs an owner, or every runtime change becomes urgent. Growth Ops keeps code actions current and tested.

The root cause · $990 a month

Growth Ops

Your RevOps team, monthly: HubSpot requests handled, a monthly health check, and every change approved by you before it goes live.

The details

HubSpot set the dates in its developer changelog: custom code actions on Node 20 can’t be edited from 17 Nov 2026, and design-manager serverless functions stop on 1 Feb 2027.

Order this quick win

Move HubSpot custom code actions to Node 24, $49. No payment now. Send this and a RevOps specialist replies by email within 2 business hours (9am to 5pm ET, Monday to Friday) to confirm the scope. You get the invoice after delivery.

  1. A RevOps engineer replies by email within 2 business hours (9am to 5pm ET, Monday to Friday).
  2. We confirm the scope and ask for the details and access we need. Nothing starts until you say go.
  3. We do the work; you approve it before it goes live.
  4. You get the invoice after delivery, by email. No payment now.

We'll only use this to reply to you. Privacy policy

FAQ

How can the price be fixed?

The scope is written down before you pay, and AI does the repetitive reading, measuring and drafting. You pay for the result on the done list, not for hours.

Who actually does the work?

AI agents audit your portal and draft each change. A RevOps specialist checks and signs it off. Nothing goes live until you approve it. Our AI agents run on Claude, GPT, Gemini and Grok models, picked for each task. A person stays in the loop at every step. Technical builds are done by a RevOps engineer and outbound by a GTM engineer. Our team is based in India and covers US business hours.

What access do you need to our HubSpot?

Read-only access first, scoped access only for the changes you approve, and we tell you how to remove our access when the work is done.

What happens after 17 Nov 2026 if we do nothing?

Actions on Node 20 can no longer be edited. HubSpot's changelog sets out the next steps; plan the upgrade before you need a change.

We have 12 actions. Is that 12 times $49?

Yes, each action is one fix. For many actions we can quote a fixed price for all of them.

Does the action's behaviour change?

It shouldn't. We test the output before and after on the same record.

What if it takes longer than 1 working day?

You get a full refund. If the job turns out bigger than one scoped task, we stop, explain why and quote it before doing anything else.

Will you change anything without asking?

No. We read first, send you the plan, and edit only after you approve it. Every change is logged so it can be undone.

What happens before any work starts?

You get the scope in writing before you pay: what is included, what is not, what we need from you and what "done" means. If something needs a higher HubSpot edition, it says so there.

Sound familiar?

A small HubSpot problem costs you every week.

  • A form, workflow or report that quietly stopped working
  • A setting nobody on the team has time to check
  • A job too small for a project and too fiddly to do yourself

How we’re different

  • Fixed prices, published on every page
  • You approve every change before it goes live
  • Read-only access first, scoped access for builds, and access removed at the end

Not fixed, full refund.

Prefer to talk? Pick a time

Next step