Skip to content

Country name normalization to a standard picklist

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.

7 steps
Per-hub plans: also Marketing Hub Professional

On per-hub plans, one of its steps belongs to another subscription: add to static list needs Marketing Hub Professional. Both are required to build it as written. On seat pricing the edition covers both.

Updated for HubSpot seat pricing
OutcomeFree-text country entries such as "USA", "U.S.", "United States", and "us" all collapse into one standardized value that reports, territory routing, and phone formatting can rely on.
Workflow mapdata-quality-004
Country/Region known, not yet normalized leads to Custom code: lookup table match. Custom code: lookup table match leads to Match found?. Match found? leads to yes: Set standardized value, status = Normalized; no: Status = Needs manual review. Status = Needs manual review leads to Add to review list + create task. yes no Country/Region known, not yet normalized Custom code: lookup table match Match found? Set standardized value, status = Normalized Status = Needs manual review Add to review list + create task
Country/Region known, not yet normalized leads to Custom code: lookup table match. Custom code: lookup table match leads to Match found?. Match found? leads to yes: Set standardized value, status = Normalized; no: Status = Needs manual review. Status = Needs manual review leads to Add to review list + create task. yes no Country/Region known, not yet normalized Custom code: lookup table match Match found? Set standardized value, status = Normalized Status = Needs manual review Add to review list + create task

When to use it, when not to

Use it

  • Use it when the Country/Region property is, or was, free text, and existing data has many spellings for the same country.
  • Use it before phone formatting (data-quality-003) or territory-based routing, since both depend on a clean country value.
Read more on when to use itShow less

Skip it

  • Do not use it if Country/Region is already a native dropdown with no legacy free-text data behind it. There is nothing to normalize.
  • Do not use it to normalize state or province values. See data-quality-012 for that, which needs its own lookup table.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 4 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 · 7 numbered actions

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 · 4 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, code

The properties JSON creates the fields in one call. The workflow JSON documents the build. The custom coded action ships as a ready-to-paste .js file.

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

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