Contact Enrichment โœ… Bulk Email & Phone Finder โœ… Any Field avatar

Contact Enrichment โœ… Bulk Email & Phone Finder โœ… Any Field

Pricing

from $50.00 / 1,000 contact matches

Go to Apify Store
Contact Enrichment โœ… Bulk Email & Phone Finder โœ… Any Field

Contact Enrichment โœ… Bulk Email & Phone Finder โœ… Any Field

๐Ÿ”ฅ Enrich any list by matching on the fields you ALREADY have โ€” name + company, email, phone, address or LinkedIn. Get verified โ˜Ž๏ธ mobile numbers โœ… work & personal emails. Pay only for contacts found. Apollo, ZoomInfo, Lusha, Clay & Seamless alternative.

Pricing

from $50.00 / 1,000 contact matches

Rating

0.0

(0)

Developer

Lead King

Lead King

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Contact Enrichment โœ… Bulk Email & Phone Finder โ€” Match on ANY Field ๐ŸŽฏ

Enrich the list you already have. Names and companies but no emails? A column of phone numbers with no names? A half-finished CRM export? Send it in and get back verified โ˜Ž๏ธ mobile numbers, โœ… work & personal emails, job titles, and company data โ€” matched against a database of hundreds of millions of profiles.

A pay-as-you-go alternative to Apollo, ZoomInfo, Lusha, Clay, Seamless, Hunter, Dropcontact and Clearbit โ€” no subscription, no seats, no export credits, no API key. You pay only for contacts actually found.

๐Ÿง‘โ€๐Ÿ’ผ What does this Contact Enrichment Actor do?

Most enrichment tools demand one specific identifier โ€” usually an email or a LinkedIn URL. Real lists are messier than that.

This Actor lets you match on any combination of 13 identity fields, so you can enrich the list you actually have instead of the one you wish you had. Give it a name and a company, or just a phone number, or an address โ€” whatever you've got. More fields simply mean a more precise match.

Export to CSV, Excel, or JSON, or push straight into your CRM.

โš–๏ธ Why use this instead of Apollo, ZoomInfo, or Clay?

This ActorApollo / ZoomInfo / Clay
PricingPay per contact foundMonthly subscription + credits
Minimum spendCents$50โ€“$15,000+/year
Match fieldsAny of 13, in any combinationUsually email or domain only
Failed matchesFree โ€” you're never chargedOften burns a credit anyway
SetupClick StartSales calls, seats, contracts
Export limitsNone โ€” it's your datasetCredit-capped exports

๐Ÿ”‘ What can I match on?

Any combination of these โ€” mix and match freely:

FieldExample
first_nameJane
last_nameDoe
emailjane@acme.com
email_domainacme.com
sha256_email4d1a...
phone+15555550123
personal_address123 Main St
personal_cityAustin
personal_stateTX
personal_zip78701
company_nameAcme Corp
company_domainacme.com
linkedin_urlhttps://linkedin.com/in/janedoe

โœจ Your existing column names usually just work. Full Name, Company, Work Email, Mobile, LinkedIn, Zip Code and dozens more are recognized automatically. Anything unusual can be pointed at the right field with the Field mapping input. Extra columns are ignored โ€” paste a whole CRM export without cleaning it up first.

๐Ÿ“ฅ Example input

{
"records": [
{ "first_name": "Jane", "last_name": "Doe", "company_domain": "acme.com" },
{ "linkedin_url": "https://linkedin.com/in/johnsmith" },
{ "phone": "+15555550123" },
{ "Full Name": "Maria Garcia", "Company": "Globex" }
],
"requireEmail": true
}

๐Ÿ•ต๏ธ What data do I get for each contact?

  • ๐Ÿ‘ค Full name (first & last)
  • ๐Ÿ“ง Personal email(s) โ€” all known, not just one
  • ๐Ÿ’ผ Business email(s)
  • ๐Ÿ“ž Phone numbers โ€” personal and business
  • ๐ŸŽฏ Job title
  • ๐Ÿข Company, company domain, industry
  • ๐Ÿ“ City, state, ZIP, address
  • ๐Ÿ”— LinkedIn URL

Output sample:

{
"matched": true,
"fullName": "Jane Doe",
"email": "jane.doe@example.com",
"businessEmail": "jdoe@acmecorp.com",
"phone": "+15550101234",
"jobTitle": "VP of Marketing",
"company": "Acme Corp",
"companyDomain": "acmecorp.com",
"linkedinUrl": "https://linkedin.com/in/janedoe",
"city": "Austin",
"state": "TX",
"input": { "first_name": "Jane", "last_name": "Doe", "company_domain": "acme.com" }
}

Every row carries the input filter that produced it, so you can join results straight back onto your source list. Records that match nothing stay in the dataset with matched: false โ€” you can see exactly what didn't resolve.

๐ŸŽš๏ธ Matching modes

  • ALL fields (default) โ€” a contact must match every field you supply. Precise, with few false positives. Best when your data is clean.
  • ANY field (matchAny: true) โ€” a contact matches if any single field matches. Great for recovering data from partial or slightly inaccurate records, but it can return unrelated people, so review before use.

๐Ÿ’ฐ Pricing โ€” you only pay for what you find

Pay-per-event: you're charged only for contacts actually returned.

  • โŒ Input records that match nothing โ†’ free
  • โœ… Set requireEmail: true โ†’ never pay for phone-only records
  • โœ… Set requirePhone: true โ†’ never pay for email-only records
  • ๐ŸŽ›๏ธ maxResultsPerRecord caps how many alternates you'll accept per row

To protect your budget, a single overly broad filter (like company_domain alone, which can match hundreds of thousands of people) is refused with a clear message instead of billing you for ten random strangers. Add a name, or use a strong identifier such as email, phone, or LinkedIn URL.

๐Ÿ’ก Tips for the best match rate

  • More fields = better matching. A name alone is rarely enough; name + company or name + city works well.
  • Strong identifiers match best โ€” email, phone, LinkedIn URL, or postal address will pin down one specific person.
  • LinkedIn URLs are canonicalized automatically, so www. and trailing-slash variants both match.
  • Try ANY mode on records that fail in ALL mode โ€” often one field in the source data is stale or misspelled.

โ“ FAQ

Do I need an API key? No. Just Apify credits โ€” everything else is handled for you.

What if a record doesn't match? It's returned with matched: false and an explanation, and you are not charged for it.

Can I run a whole CSV through this? Yes. Upload it as the records input; unrecognized columns are ignored, so most exports work as-is.

Is this GDPR/CCPA compliant to use? You are responsible for having a lawful basis for processing and contacting the people you enrich. Use it for legitimate B2B outreach and honor opt-outs.