Skip to content
← All guides

When does a Turbyn step spend fewer HubSpot credits?

A Turbyn action can replace a chain of HubSpot workflow actions with one step. You still pay HubSpot for that step, and you pay Turbyn for the run. Here is when that is the cheaper design.

Turbyn · Published · Updated

The short answer

Use one Turbyn step when several data actions would each be charged, and the job does not fit HubSpot's 20-second custom code action. The Turbyn step is still one HubSpot workflow action, so it spends HubSpot credits once per record, plus Turbyn's own runtime credits. It is the wrong trade when a capacity pack already covers your volume, or when a marketer needs to edit each step by hand.

Turbyn is one workflow action that runs your JavaScript or Python and returns values to the next HubSpot step. On a price list that charges per action, that shape is the saving: ten data steps become one execution. The step does not opt the portal out of HubSpot credits.

The bill with both products

Using the ten-step cleanup of 10,000 records from one code step, fewer credits:

Design HubSpot actions HubSpot credits HubSpot overage after 10,000 included Turbyn
Ten native actions 100,000 142,500 about €1,325 —
One Turbyn action 10,000 30,000 about €200 10,000 short runs

Ten thousand short runs fit in Turbyn Pro, which is $99 a month and 25,000 credits, counted as 25,000 runs of about 2 seconds at 1 vCPU and 512 MiB. Longer runs and larger machines cost more Turbyn credits. The HubSpot side of that design is still about €200 of action overage, plus the Professional seat.

That comparison is worth making when the ten steps are data work and the account is paying the 3-credit and 2-credit tiers. It is a weak comparison when you already buy the €150 pack for 500,000 actions and you are under the cap. Then Turbyn is a runtime decision, not a HubSpot-invoice decision.

When the one block is the right block

Choose Turbyn for a chain that has at least one of these:

  • It needs a package HubSpot’s custom code runtime does not ship. The native list is closed. See npm packages in workflows.
  • It cannot finish in 20 seconds or 128 MB. A paginated sync, a document, or a slow vendor API belongs here. The native limits are in HubSpot custom code limitations.
  • You are not on a plan that includes HubSpot’s own code action. Starter does not. Outside the EMEA seats-and-credits release, HubSpot’s docs still require Data Hub Professional or Enterprise for native custom code.
  • The same recipe should be readable, tested, and published once, then reused on more than one workflow.

A short format-and-write that fits in HubSpot’s runtime can stay a native custom code action. The credit maths is the same one-action charge, and you do not add a second bill. New EMEA Professional is the case where that native action is easiest to justify, because the edition already includes it. Seats and credits is who that sentence applies to. Existing customers are not on that list yet.

What to keep in HubSpot

Keep the delay, the branch, the email, and the task. A Turbyn action should return the score, the owner, the formatted phone, and a status the branch can read. The workflow screen still shows the routing. The code owns the calculation.

Also keep a failure visible. One block that hides ten jobs needs outputs for the invalid case, so a later step can skip the write instead of retrying a half-finished chain. HubSpot may retry a failed action. A write that is not safe to repeat will repeat.

A practical order

  1. Export or read the month’s workflow action count before changing anything.
  2. If you are under a capacity pack you already pay for, stop. Complexity is the only win.
  3. Find chains of property updates with no delay between them.
  4. If the chain fits in 20 seconds and HubSpot’s libraries, use HubSpot’s code action.
  5. If it does not, put it in one Turbyn action, publish it, and count one HubSpot action per enrollment plus the Turbyn run.
  6. Recheck the credit report after a week. If the action count did not drop by roughly the number of steps you removed, the portal is not pricing the code step the way this page assumes. Put the steps back until HubSpot confirms the rate.

The recipes are the shortest way to see a one-block version of a job you already run as many steps. Start with the recipe library, or with the phone, routing, and scoring examples called out in custom code examples.

Sources and references

Source documentation checked for this update. Availability can vary by subscription and account.

Questions from this guide

No. If HubSpot bills the Turbyn action as a workflow action, each record that reaches it spends the normal action rate once. Turbyn also spends its own credits for the compute. The saving is the actions you no longer run.

Continue reading