Reference · built on requestOperator by FibricSales, quotes & revenue

Duplicate Lead

Matches new leads against existing accounts and customers and proposes a merge or owner handoff before two reps call the same buyer.

Request accessPricing ↗

About

A lead arrives from a form, a list, or an identity call, and a rep starts dialling. Duplicate Lead checks first. It compares the new record's email, phone, and domain with the contacts and companies already in the CRM, the persons in Pipedrive, and the customers in your store, and it looks up who already owns any match.

A strong match becomes a merge proposal with both records side by side and the values that will win. A match to an owned account becomes a handoff proposal to that owner. A weak match is flagged for a person to compare. Merges happen only after approval, because a HubSpot merge cannot be undone.

This is a reference listing. It documents what Fibric would read from Duplicate Lead and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • New HubSpot contacts and companies, and form submissions through the Forms API with submittedAt, values, and pageUrl
  • Existing HubSpot contacts matched on email, the primary unique identifier, and companies matched on domain and hs_additional_domains
  • Pipedrive persons through GET /api/v2/persons/search on email, phone, and name, with exact_match set
  • Identity traits from Segment Identify calls: userId, anonymousId, and traits such as email, phone, and company
  • Store customers: Shopify customers with defaultEmailAddress, defaultPhoneNumber, numberOfOrders, and amountSpent
  • Owners through GET /crm/v3/owners with their teams, so a lead is handed to the rep who already owns the account

Proposed actions

  • Target capability: propose a merge of two HubSpot contacts or companies, naming which record stays primary and which property values win
  • Target capability: propose a Pipedrive merge through PUT /api/v1/persons/{id}/merge with merge_with_id set to the record that keeps its data
  • Target capability: propose an owner handoff: hubspot_owner_id on the lead set to the owner of the matched company, with a note to both reps
  • Target capability: propose a possible-duplicate flag on a weak match, for a person to compare the two records side by side
  • Target capability: propose a Slack message to both reps through chat.postMessage before either one calls

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Stop two reps calling one buyer

    When a new HubSpot contact's email or company domain matches an owned company, propose the handoff to that owner and a Slack message to both reps before the first call.

    With HubSpot, Slack

  • Merge a Pipedrive person found in Shopify

    Search persons by the customer's defaultEmailAddress and phone, and propose PUT /persons/{id}/merge with the older record as merge_with_id, showing numberOfOrders on the proposal.

    With Pipedrive, Shopify

  • Match a form fill to an existing account

    Read the submission's values and any Segment traits for the same email, compare with existing contacts, and propose a merge or a flag with the fields that differ.

    With HubSpot, Twilio Segment

  • Hand a lead to the account owner

    When the lead's domain matches a company with an owner, propose hubspot_owner_id on the lead and a Teams chat message to the owner naming the lead and its source.

    With HubSpot, Microsoft Teams

Requirements

  • A CRM whose records can be merged by API: HubSpot or Pipedrive
  • Lead sources you can read: HubSpot forms, or Segment Identify traits
  • A store with customer records to match against: Shopify, BigCommerce, or Magento
  • A rule for which record stays primary: the oldest, the one with orders, or the one with an owner
  • A person who approves every merge
Authentication
A CRM OAuth app or private-app token with contact and company read and write scopes and the forms scope, read access to your customer data platform's identity traits, and store API access with read_customers.

Limits

  • HubSpot states it is not possible to unmerge records. Every merge is proposed and approved first, with the differing values listed.
  • HubSpot refuses a merge once the two records have been part of 250 or more merges combined. Such a pair is flagged, not merged.
  • A match on name alone is a possible duplicate, never a merge. A merge needs an email, phone, or domain in common.
  • It matches what the systems hold. A buyer using two email addresses and no shared phone looks like two people until a person links them.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Duplicate Lead ↗

Questions and answers

What does a person approve?
Each merge or handoff. A merge proposal shows both records side by side, which one stays primary, and each property where they differ with the value that will win. A handoff shows the lead, the matched account, and its owner. Approve, swap the primary, or reject.
Can a merge be undone?
Not in HubSpot. Its documentation states records cannot be unmerged. That is why the operator never merges on its own and why the proposal lists every differing value before approval. In Pipedrive, the record named in merge_with_id keeps its data.
What record is left?
One entry per pair: both record ids, the fields matched, the primary chosen, the values that won, the owner set, who approved, and when. For HubSpot the entry keeps the merged record's id so its history can still be traced.
Ask about Duplicate Lead

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy