Outcome. State and province entries such as "California", "calif.", and "CA" all collapse into one standard two-letter code, so territory routing and address-based reports read the same value.
Workflow map
Enrollment, branches and actions at a glance
data-quality-012
flowchart TD
A[State and country known, not yet normalized] --> B[Custom code: lookup table match by country]
B --> C{Match found?}
C -->|yes| D[Set two-letter code, status = Normalized]
C -->|no| E[Status = Needs manual review]
E --> F[Add to review list + create task]
When to use it, when not to
- UseUse it when
State/Regionis, or was, free text, and existing data has many spellings for the same state or province. - UseUse it before territory-based lead routing that filters on state, since inconsistent spellings silently miss records that should match.
- SkipDo not use it on portals operating only outside the United States and Canada, where "state" is not the relevant administrative unit. Adapt the lookup table to the country's actual regions, or skip this workflow entirely.
- SkipDo not use it to normalize country values. See data-quality-004 for
that; run it first, since state normalization here assumes a clean
Country/Regionto pick the right lookup table (US versus Canada).
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.5 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.7 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.
