Outcome. Every contact carries one normalized dedupe key computed automatically at submission, so a later import or integration can match against it reliably instead of each process separately trying to normalize email casing and formatting itself.
Workflow map
Enrollment, branches and actions at a glance
data-quality-039
flowchart TD
A[Contact created or Email changed] --> B[Custom code: lowercase, trim email]
B --> C[Set Dedupe key = computed_key]
When to use it, when not to
- UseUse it when contacts arrive through a form and you also periodically import lists from other sources, an event scan, a partner list, that need to match against existing records using something more forgiving than an exact-case, exact-format email string.
- UseUse it as a building block other processes read, not a matching engine by itself. The key is precomputed once, an external import tool or a scheduled cleanup workflow does the actual comparison against it.
- SkipDo not use it as your only deduplication mechanism at submission. HubSpot already deduplicates by exact primary email natively; this fiche is for near-duplicate prevention on subsequent bulk operations, see data-quality-002 for the review-queue pattern that acts on it.
- SkipDo not use it if your only import source is a clean, already-deduplicated CRM export. The extra property and logic add maintenance for a problem you do not actually have.
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.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.
