Skip to content
The Workflow Library
Get the full library

Round and format a numeric property (revenue estimate)

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Data Hub Professional.

Company1 stepUpdated for HubSpot seat pricing
OutcomeA revenue estimate field always lands as a clean rounded number, instead of mixing precise-looking decimals next to plain guesses that both claim a precision they do not have.
Workflow mapdata-quality-038
Annual revenue estimate known or changed leads to Format Data: round to nearest 10,000. Format Data: round to nearest 10,000 leads to Set Annual revenue estimate = rounded value. Annual revenue estimate known or changed Format Data: round to nearest 10,000 Set Annual revenue estimate = rounded value
Annual revenue estimate known or changed leads to Format Data: round to nearest 10,000. Format Data: round to nearest 10,000 leads to Set Annual revenue estimate = rounded value. Annual revenue estimate known or changed Format Data: round to nearest 10,000 Set Annual revenue estimate = rounded value

When to use it, when not to

Use it

  • Use it whenever a numeric estimate, revenue, employee count, deal size guess, comes from a source that returns more precision than the number is actually accurate to, and inconsistent precision across records makes sorting and reporting look noisier than the data really is.
  • Use it as formatting only. It does not correct a wrong estimate, only standardizes how a given value displays and rounds.
Read more on when to use itShow less

Skip it

  • Do not use it on a property where exact precision matters, an actual invoiced amount, a measured quantity. Rounding there destroys real information rather than cleaning up false precision.
  • Do not use it if your reporting tool already handles display-level rounding on its own. Adding a second rounding layer on the stored value itself is redundant and makes the raw and displayed numbers diverge from any other system reading the same property.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 2 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 1 numbered action

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 3 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Data quality spec

Not the workflow you needed?

More in Data quality

50 specs in this section

See all 50 This category, 39 EUR
FreeRequired field enforcement on contact creation (email or phone missing)Contact9 steps Currency normalization on deal amount to a home-currency propertyDeal4 steps Duplicate contact detection and merge review queueContact7 steps Phone number formatting to a standard international formatContact4 steps

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library