CRM

HubSpot Duplicate Company Merge Proposals Logged to Notion

Detects duplicate HubSpot Companies, generates a field-level merge proposal showing each property conflict and its recommended survivor.

CategoryCRM
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled dedupe pass
  • ActionSearch HubSpot for Companies sharing domain or nameHubSpotHubSpot
  • LogicDiff properties and recommend survivor per field
  • LogicFilter to pairs with material conflicts
  • ActionCreate Notion page documenting proposal and recommendationsNotionNotion
  • OutputOn Notion approval, merge Companies in HubSpotHubSpotHubSpot

What it does

This workflow finds duplicate Company records in HubSpot, compares their properties, and produces a merge proposal that lays out every conflicting property with a recommended winning value. Each proposal becomes a Notion page with checkboxes for the reviewer, so the decision and the before/after state are permanently captured as an audit record.

When to use it

Use it when you need HubSpot dedupe decisions to be auditable for compliance or RevOps reviews, and you want the rationale and approval living in your team's Notion workspace rather than buried in CRM history.

How it works

  1. 1A schedule trigger runs the dedupe pass.
  2. 2The workflow searches HubSpot for Companies sharing domain or name.
  3. 3It diffs properties across each duplicate pair and recommends a survivor per field.
  4. 4A filter routes only pairs with material conflicts forward.
  5. 5It creates a Notion page documenting the proposal, conflicts, and recommendations.
  6. 6Once the reviewer checks off approval in Notion, the workflow merges the Companies in HubSpot.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HubSpotCRM, deals, marketing, support.
  2. 2
    Connect NotionPages, databases, comments.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.