Skip to content
← All guides

Can one workflow step replace ten HubSpot actions?

On HubSpot's EMEA credit price list, a chain of property updates is charged per action. One code step does that chain once per record, if HubSpot prices custom code as a single action.

Turbyn · Published · Updated

The short answer

Yes, for a chain of data changes. Ten actions on 10,000 records are 100,000 charged executions. The same work in one code step is 10,000, if a custom code action is priced like any other workflow action. HubSpot has not published a separate custom-code rate. Delays, branches, emails, and tasks still need their own steps.

HubSpot’s new EMEA price list charges each action a record runs. A cleanup that used to be “just a few property steps” is now a line of credits. The useful change is to stop paying for the same record ten times when one step can do the work.

Take a lead-cleanup chain:

  1. Format the phone number.
  2. Split the full name.
  3. Copy the email domain onto the company.
  4. Calculate a fit score.
  5. Write five related properties.
  6. Normalize the country.

That is ten actions. At 10,000 records a month it is 100,000 executions. Priced across the published tiers, that is 142,500 credits: 30,000 for the first 10,000 actions, 90,000 for the next 45,000, and 22,500 for the 45,000 after that. Professional includes 10,000 credits. The rest, at €0.01, is about €1,325, and that pool was also supposed to pay for email.

The same 10,000 records through one code step are 10,000 actions, 30,000 credits, and about €200 of overage after the included credits. The gap is about €1,100 a month of HubSpot credits. How the tiers add up is the arithmetic. HubSpot’s credits article says every workflow action uses credits except branches, delays, and go-to actions. Custom code is not in that exception list, and the rate sheet still gives it no separate price. Confirm it on the order form before you delete the ten steps in a production portal. The full sheet is the seats-and-credits reference.

What belongs in the one step

Put work in the code step when all of these are true:

  • The inputs are properties you already have on the record.
  • The outputs are values a later step can write, or writes the code itself is allowed to make.
  • The rule is stable. A marketer should not need to edit it every week.
  • The record volume is high enough that the extra actions show up in the credit report.

Good fits are the jobs Turbyn already ships as one action: normalize phone numbers, standardize country values, backfill qualification fields, and route by a territory table. A chain of those is one enrollment and one HubSpot action, with several named outputs.

Leave these as HubSpot steps:

  • A delay, a date property that should wait, or a branch on a value the code just returned.
  • An email, a task, a notification, or an enrollment in another workflow.
  • Anything a non-developer owner needs to change from the workflow screen.

The code step hands the branch a clean value. The branch stays visible.

What you give up

The workflow history no longer shows ten green checks. A failure is one failed action, and the log has to say which of the ten jobs inside it failed. A teammate who used to edit a “set property” field now asks for a change to the action. That is a fair trade when the chain is stable and expensive. It is a bad trade when the chain changes every campaign.

HubSpot’s own custom code action can collapse the same chain, inside 20 seconds, 128 MB, and its published libraries. A test of that action writes the record you select. Those limits are in HubSpot custom code limitations. If the cleanup fits, you do not need a second product to get the credit reduction.

When the pack makes this unnecessary

The workflow capacity pack is €150 for 500,000 actions. If your account is under that cap and you already pay for the pack, deleting seven steps saves complexity, not €1,100. Do the credit report first. Collapse steps when you are in the 3-credit and 2-credit tiers, or when the included pool is being eaten by property updates you could do once.

Where Turbyn fits that choice is the next page: the jobs that do not fit HubSpot’s code action, and what you still pay HubSpot for the one remaining step.

Sources and references

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

Questions from this guide

If it is a workflow action, it should spend the normal action rate for that one execution. You are replacing ten charges with one, not removing the charge. A Turbyn step is still one action in the HubSpot workflow, and Turbyn bills its own runtime separately.

Continue reading