Placeholder and junk value flag in name fields (test, n/a, asdf)
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.
Per-hub plans: also Marketing Hub
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.
One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.
When to use it, when not to
Use it
- Use it on portals fed by public forms, where testers, bots, and impatient form-fillers commonly leave junk in required name fields to get past validation.
- Use it as a periodic sanity check after a bulk import from a source with unknown data quality.
Read more on when to use itShow less
Skip it
- Do not use it expecting it to catch every kind of bad data. This workflow matches a known list of placeholder patterns and a few structural heuristics (repeated characters, keyboard-row strings); it will miss creative junk it was not built to recognize.
- Do not use it to validate that a name is a real person's name (as opposed to a business name typed in the wrong field, for example). That is a different check, out of scope here.
Read more on when to skip itShow less
The rest of this spec
Not the workflow you needed?
More in Data quality
50 specs in this section
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.
Here it is. Download the pack now (.zip) The link is in your inbox too.
Read the free Data quality spec