Lead List Cleaner: Dedupe, Phone, Website and MX avatar

Lead List Cleaner: Dedupe, Phone, Website and MX

Pricing

$1.00 / 1,000 rows

Go to Apify Store
Lead List Cleaner: Dedupe, Phone, Website and MX

Lead List Cleaner: Dedupe, Phone, Website and MX

Clean a lead list or CRM export: find duplicates, normalise phones, check websites and mail servers, and get CRM-ready columns. Failed and duplicate rows are marked, never dropped.

Pricing

$1.00 / 1,000 rows

Rating

0.0

(0)

Developer

Open Data Desk

Open Data Desk

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Features

Limited permissions

Share

Clean a lead list or a CRM export into flat, ready-to-use columns. The Actor finds duplicates, normalises phone numbers, checks whether a website responds, and looks up the mail server for each e-mail domain. Rows that fail a check, or that look like duplicates, are not dropped. They stay in the results with a status and a list of issues.

This Actor does not scrape websites for new contacts. It only works on the rows you give it.

What does Lead List Cleaner do?

Typical uses:

  • Clean a Google Maps, LinkedIn or CSV export before you import it into a CRM.
  • Find duplicate companies and people in a list you already have.
  • Check which websites still respond, and which e-mail domains have a mail server.
  • Standardise phone numbers to international E.164 format.

What data do you get?

Each input row becomes one output row.

FieldWhat it is
inputIndexPosition of the row in your input, starting at 0
rowStatusok, duplicate, invalid, or skipped_limit
issuesA list of problems, for example duplicate_of_0, no_mx, website_timeout
companyName, fullName, firstName, lastNameNames, when they can be read from the input
email, emailNormalizedThe original address and a lower-case trimmed copy
emailSyntaxOk, emailIsRoleAddress, emailIsDisposable, emailTypoSuggestionSyntax, role addresses such as info@, disposable inboxes, and a suggested domain if a typo is likely
emailHasMx, mxHostsWhether the domain has MX records, and the hosts
phone, phoneE164, phoneValid, phoneCountryThe original number and a normalised E.164 number
website, websiteNormalized, websiteRootDomainThe site you gave, a full URL, and the host without www
websiteReachable, websiteStatusCode, websiteFinalUrl, websiteErrorWhether the site answered, the HTTP status, and the URL after redirects
isDuplicate, duplicateOf, duplicateMatchedOnSet when this row matches an earlier one
originalThe input record, unchanged

Nothing is guessed that was not in the input, except typo suggestions (the original address is never rewritten).

Example output

One cleaned row from a test run on a small example list. Duplicate and flagged rows are also kept; they are just marked.

{
"inputIndex": 0,
"companyName": "Example Labs",
"fullName": "Alex Example",
"firstName": "Alex",
"lastName": "Example",
"email": "alex@example.com",
"emailNormalized": "alex@example.com",
"emailSyntaxOk": true,
"emailIsRoleAddress": false,
"emailIsDisposable": false,
"emailTypoSuggestion": null,
"emailDomain": "example.com",
"phone": "+1 415 555 2671",
"phoneE164": "+14155552671",
"phoneValid": true,
"phoneCountry": "US",
"website": "https://example.com",
"websiteRootDomain": "example.com",
"issues": [],
"original": {
"company": "Example Labs",
"name": "Alex Example",
"email": "alex@example.com",
"phone": "+1 415 555 2671",
"website": "https://example.com"
},
"emailHasMx": true,
"mxHosts": [
""
],
"mxError": null,
"websiteNormalized": "https://example.com/",
"websiteReachable": true,
"websiteStatusCode": 200,
"websiteFinalUrl": "https://example.com/",
"websiteError": null,
"isDuplicate": false,
"duplicateOf": null,
"duplicateMatchedOn": [],
"rowStatus": "ok",
"checkedWebsites": true,
"checkedMx": true
}

Nothing is silently dropped

Every input row is written to the results. Duplicates are marked, not removed. Invalid e-mails and failed website checks are marked, not removed. If you set Max rows to check lower than the size of your list, the remaining rows are still written with status skipped_limit.

How to use it

  1. Paste your leads as JSON in Records, or give a dataset ID from a previous Apify run.
  2. Set Default phone country if many numbers have no country prefix (for example DK or US).
  3. Choose how duplicates should be found. The default is matching e-mail or phone number.
  4. Leave the website and MX checks on, unless you only want formatting and deduplication.
  5. Set Max rows to check and click Start.
  6. Download the result as JSON, CSV or Excel, or read it with the API.

Common column names such as email, phone, website, company and name are detected automatically. If your columns are named something else, fill in the column fields.

Limits

  • Website checks follow redirects and wait a few seconds. A site behind a strict bot filter may look down even if a browser can open it.
  • The MX check only looks at DNS. It does not test whether a mailbox exists, and it does not send mail.
  • Disposable-domain detection uses a bundled public list (MIT licence, see src/disposable-domains.LICENSE). The list is a snapshot, not a live feed.

How much does it cost?

You pay for each row that is written, including duplicates, invalid rows and rows skipped because the max was reached. The price per 1,000 rows is shown at the top of this page, and you can set a maximum cost per run.

Data and privacy

The Actor works on data you already have. It does not keep a copy after the run ends, beyond what Apify stores for your run in the usual way. You are responsible for how you use personal data in the list, including e-mail addresses and phone numbers.

Issues and requests

If a column is not picked up, or a check looks wrong, please open an issue on the Issues tab with a couple of sample rows (you can hide personal data).