Skip to content
The Workflow Library
Get the full library

Merge-conflict source-of-truth flag after a manual merge

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

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.

Contact2 stepsUpdated for HubSpot seat pricing
OutcomeEvery 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 mapdata-quality-041
Contact merge history changes leads to Set Merge review status: Needs post-merge review. Set Merge review status: Needs post-merge review leads to Create confirmation task for record owner. Contact merge history changes Set Merge review status: Needs post-merge review Create confirmation task for record owner
Contact merge history changes leads to Set Merge review status: Needs post-merge review. Set Merge review status: Needs post-merge review leads to Create confirmation task for record owner. Contact merge history changes Set Merge review status: Needs post-merge review Create confirmation task for record owner

When to use it, when not to

Use it

  • Use 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.
  • Use 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.
Read more on when to use itShow less

Skip it

  • Do 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.
  • Do 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.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 2 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 2 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 3 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Data quality spec

Not the workflow you needed?

More in Data quality

50 specs in this section

See all 50 This category, 39 EUR
FreeRequired field enforcement on contact creation (email or phone missing)Contact9 steps Association hygiene: prevent duplicate association labels on the same record pairDeal6 steps Duplicate contact detection and merge review queueContact7 steps Phone number formatting to a standard international formatContact4 steps

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.

149 EUR199

Full library, 565 specs
Get the full library