The Workflow Library

Library / Data quality / data-quality-024

Address field standardization (street abbreviations, casing)

Data qualityContactData Hub ProfessionalIntermediate~30 min to buildFull spec

Outcome. Street 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 map Enrollment, branches and actions at a glance data-quality-024
flowchart TD
    A[Street address known or changed] --> B[Custom code: title case + whole-word abbreviation mapping]
    B --> C[Set Street address to standardized value]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse 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.".
  • UseUse it as a light normalization pass; it standardizes format, not accuracy. It does not verify the address exists or correct a wrong street name.
  • SkipDo 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.
  • SkipDo 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.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.3 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.2 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

or the data quality pack, 39 EUR

One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.