The Workflow Library

Library / Data quality / data-quality-008

Duplicate company detection by domain match

Data qualityCompanyOperations Hub ProfessionalIntermediate~40 min to buildFull spec

Outcome. New company records sharing a domain with an existing record are flagged into a review queue at creation, before two versions of the same account start accumulating separate deals and contacts.

Workflow map Enrollment, branches and actions at a glance data-quality-008
flowchart TD
    A[Company created with a domain] --> B[Custom code: normalize domain, search for exact match]
    B --> C{Match found?}
    C -->|yes| D[Flag Possible duplicate, store match ID]
    D --> E[Add to review list + create review task]
    C -->|no| F[Status: Confirmed unique]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when companies get created from multiple entry points: manual creation by reps, list imports, and contact-triggered auto-creation, all of which can independently create the same account.
  • UseUse it alongside HubSpot's native duplicate management tool (Companies > Actions > Manage duplicates) for bulk cleanup of records that already exist. This workflow only catches new duplicates going forward.
  • SkipDo not use it expecting an automatic merge. HubSpot workflows have no native "merge records" action. A human merges through the native duplicate management UI or the CRM API.
  • SkipDo not use it as the only signal for company matching in data-quality-006. That workflow searches for a single confident domain match to associate a contact; this one is about catching two company records that should not both exist.
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.5 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.