Skip to content
The Workflow Library
Get the full library

Address field standardization (street abbreviations, casing)

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.

Contact2 stepsUpdated for HubSpot seat pricing
OutcomeStreet addresses land in one consistent format, title case with standard abbreviations for street, avenue, suite, and similar terms, so mailing labels, exports, and address-based matching all read the same value.
Workflow mapdata-quality-024
Street address known or changed leads to Custom code: title case + whole-word abbreviation mapping. Custom code: title case + whole-word abbreviation mapping leads to Set Street address to standardized value. Street address known or changed Custom code: title case + whole-word abbreviation mapping Set Street address to standardized value
Street address known or changed leads to Custom code: title case + whole-word abbreviation mapping. Custom code: title case + whole-word abbreviation mapping leads to Set Street address to standardized value. Street address known or changed Custom code: title case + whole-word abbreviation mapping Set Street address to standardized value

When to use it, when not to

Use it

  • Use it when addresses arrive from multiple sources, forms, imports, manual entry, with inconsistent abbreviations and casing: "123 MAIN ST", "123 main street", "123 Main St.".
  • Use it as a light normalization pass; it standardizes format, not accuracy. It does not verify the address exists or correct a wrong street name.
Read more on when to use itShow less

Skip it

  • Do not use it expecting full address validation or geocoding. That needs a dedicated address-verification service called from custom code with its own API key and cost, which is out of scope for this fiche.
  • Do not use it on portals where the address field is rarely used or not relied on for anything operational; the cleanup effort is not worth it there.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 3 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 · 2 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 · 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, 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

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 Duplicate contact detection and merge review queueContact7 steps Phone number formatting to a standard international formatContact4 steps Country name normalization to a standard picklistContact7 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