Outcome. Job titles entered as free text ("VP Sales", "Vice President of Sales", "Sales VP") collapse into one standard title, so persona-based segmentation and lead scoring can filter on job title reliably.
Workflow map
Enrollment, branches and actions at a glance
data-quality-014
flowchart TD
A[Job title known, not yet standardized] --> B[Custom code: lookup table match]
B --> C{Match found?}
C -->|yes| D[Set standardized title, status = Standardized]
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
Job titleis free text and marketing or sales segmentation depends on grouping similar titles together (all VP-level sales titles into one persona bucket, for example). - UseUse it when lead-scoring rules key off job title keywords and inconsistent phrasing is causing missed matches.
- SkipDo not use it expecting full seniority or department inference from an arbitrary title. This workflow maps known variants to known standard values; a completely new, unmapped title just gets queued for review, it does not get guessed at.
- SkipDo not use it as a replacement for a properly designed persona property if your portal already derives persona from multiple signals (title, industry, company size). This workflow only cleans the title field itself.
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.4 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.
