Outcome. Every contact that survives a manual merge gets flagged for a quick post-merge check, catching the case where the wrong record's values won the conflict before a rep acts on stale or incorrect information.
Workflow map
Enrollment, branches and actions at a glance
data-quality-041
flowchart TD
A[Contact merge history changes] --> B[Set Merge review status: Needs post-merge review]
B --> C[Create confirmation task for record owner]
When to use it, when not to
- UseUse it on portals where merges happen often enough, and by enough different people, that nobody has a consistent rule for which record's values should win a field-level conflict during a merge.
- UseUse it as a lightweight nudge to double check the surviving record's key fields, not as an automated fix. The merge already happened by the time this fires; this only asks a human to confirm the outcome.
- SkipDo not use it if merges in your portal are rare, or a single trained data owner performs every merge personally and already double checks by habit. The extra task volume is not worth it for occasional, careful manual work.
- SkipDo not use it expecting it to catch which specific fields were overwritten incorrectly. It flags that a merge happened, not a field-by-field diff of before and after.
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.2 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.PDF, Markdown, JSON
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.
