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.
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]

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.
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.




