Merge CRM duplicates that use a personal and a work email

In a CRM data-quality add-on, find contacts that are the same person stored twice (once with a personal email, once with a work email) and merge them into one record.

Get a free API key + $5 Get a sample run

Free API key
No credit card
Run your sample

Tools named: LinkedIn

Uses POST /person_detail_reverse_lookup/by_email/ · Reverse email lookup API reference

What it costs: 5 credits per email found. A mobile or email lookup that returns nothing costs 0 credits. Enrichment and search are charged per request: credit pricing.

How the data flows

2 inputs → Reverse email lookup + Person enrichment + Work emails → 4 fields sample data

01 · Inputs

Personal email

sam.s@example.net

Work email

sam@example.com

02 · Forager

Reverse email lookup + Person enrichment + Work emails POST /person_detail_reverse_lookup/by_email/

Match found

03 · Outputs

Sam SpecimenVP Revenue Operations · Example Inc.

current employer: Example Inc.
work email: sam@example.com
name: Sam Specimen
title: VP Revenue Operations
mobile: +1 (512) 555-0133

4 fields in the responseexample data

Steps

Resolve personal-email contacts with POST /person_detail_reverse_lookup/by_email/
Match the returned LinkedIn identifier, or full name plus current employer domain from roles, against existing work-email contacts
Propose merges for the user to approve, keeping both emails on the surviving record
Where no work email exists yet, request one via /person_contacts_lookup/work_emails/

import json, os, requests

BASE = "https://api-v2.forager.ai/api/{account_id}/datastorage"
HEADERS = {"X-API-KEY": os.environ["FORAGER_KEY"]}
body = json.load(open("request.json"))  # request fields: see the API reference

# 1. Resolve personal-email contacts with POST
# /person_detail_reverse_lookup/by_email/
r1 = requests.post(f"{BASE}/person_detail_reverse_lookup/by_email/", headers=HEADERS, json=body)

# 2. Match the returned LinkedIn identifier, or full name plus current
# employer domain from roles, against existing work-email contacts

# 3. Propose merges for the user to approve, keeping both emails on the
# surviving record

# 4. Where no work email exists yet, request one via
# /person_contacts_lookup/work_emails/

# 1. POST /person_detail_reverse_lookup/by_email/
curl -X POST \
  https://api-v2.forager.ai/api/{account_id}/datastorage/person_detail_reverse_lookup/by_email/ \
  -H "X-API-KEY: $FORAGER_KEY" \
  -H "Content-Type: application/json" \
  -d @request.json

Generated from the recipe stepsRequest fields: API reference

Run it yourself: Reverse email lookup API reference

Get a free API key + $5 Get a sample run

Free API key
No credit card
Run your sample

Inputs and outputs

Inputs	Outputs
CRM contacts with personal emails	`duplicate pairs`
CRM contacts with work emails	`merged record`
	`current employer`
	`work_email`

Questions about this recipe

How do I find CRM contacts that are the same person under two emails?

Resolve personal-email contacts with POST /person_detail_reverse_lookup/by_email/. Where no work email exists yet, request one via /person_contacts_lookup/work_emails/.

What does it cost to merge CRM duplicates that use a personal and a work email?

Reverse email lookup: 5 credits per request, charged whether or not data comes back. Person enrichment: 1 credit per request, charged whether or not data comes back. Work emails: 5 credits per work email found, and a work email lookup that finds nothing costs 0 credits. Growth's 8,250 monthly credits cover 1,650 emails or 8,250 person enrichments, or a mix. Self-serve plans are Starter, Growth, Pro and Scale. See plans and prices

What do I need to run this recipe, and what comes back?

You send CRM contacts with personal emails and CRM contacts with work emails. You get back current employer, duplicate pairs, merged record and work_email, as JSON. You also need a Forager API key, which comes with a free account.

Can I match a personal email to a work email contact?

In a CRM data-quality add-on, find contacts that are the same person stored twice (once with a personal email, once with a work email) and merge them into one record. Reps see one contact per person with full activity history, and reporting stops double-counting people.

Can I test reverse email lookup for free?

Yes. Create a free account at app.forager.ai: it comes with $5 in free credits and an API key, and there is no credit card to sign up. Run it on records you already know, or book a demo and send us a list: we run it and show you what we find.

When should I run this workflow?

When a scheduled dedupe run, or a new contact is created with a personal email. Reps see one contact per person with full activity history, and reporting stops double-counting people.

Which Forager products does this recipe use?

Reverse email lookup, person enrichment and work emails. Reverse email lookup: turn an email address into a full person profile: name, title, company, location and social links. Person enrichment: a full professional profile for a person from a LinkedIn URL, email or phone: experience, education, skills and contact channels.

How accurate is Forager data?

The test that counts is your own: send a list of profiles you care about. We run it and show you what we find, number by number, so you can measure hit rate and connect rate yourself.

How do I match gmail contacts to company contacts?

Resolve personal-email contacts with POST /person_detail_reverse_lookup/by_email/. Match the returned LinkedIn identifier, or full name plus current employer domain from roles, against existing work-email contacts.

Which tools can run this workflow?

Native in Clay and Zapier, partner-built in Deepline and Cargo and called through the API from Make, n8n and your own code. Or call the endpoints in the steps above from your own code with one API key.

How many steps is this workflow?

4 steps: resolve personal-email contacts with POST /person_detail_reverse_lookup/by_email/, match the returned LinkedIn identifier, or full name plus current employer domain from roles, against existing work-email contacts, propose merges for the user to approve, keeping both emails on the surviving record and where no work email exists yet, request one via /person_contacts_lookup/work_emails/.

Do I need a subscription?

Not to test: a free account comes with $5 in credits. To keep using Forager, choose a monthly or yearly plan. Monthly plans cancel anytime and unused credits roll over; yearly plans grant all credits upfront and cost 10% less. Larger volumes are agreed with our team.

Merge CRM duplicates that use a personal and a work email

How the data flows

Steps

Inputs and outputs

Questions about this recipe

How do I find CRM contacts that are the same person under two emails?

What does it cost to merge CRM duplicates that use a personal and a work email?

What do I need to run this recipe, and what comes back?

Can I match a personal email to a work email contact?

Can I test reverse email lookup for free?

When should I run this workflow?

Which Forager products does this recipe use?

How accurate is Forager data?

How do I match gmail contacts to company contacts?

Which tools can run this workflow?

How many steps is this workflow?

Do I need a subscription?

More recipes for CRM add-ons

Detect CRM contacts who changed jobs and alert on moved champions

Pre-build each new customer's TAM on day one inside an AI-native CRM

Power a CRM's native contact-enrichment button

Alert account owners when a customer posts a job naming a competitor

Keep one canonical company record per account in a CRM add-on

Back a sales-intelligence database with an additional mobile source

Put people, company and job data your users can act on inside your product