Bulk Email Verifier & Finder

Apify Actor for bulk email verification and email discovery from a person's name and company domain. Uses remote SMTP verification, MongoDB prior-result cache, and Puppeteer browser checks (Gmail/Outlook) for difficult domains.

Input modes

You only need one of these — the Actor auto-detects verify vs finder:

1. Verify emails (inline list)

{
  "emails": ["john@example.com", "alice@acme.com"]
}

2. Find emails (name + domain records)

{
  "records": [
    { "fullName": "John Doe", "domain": "company.com" },
    { "fullName": "Jane Smith", "domain": "acme.com" }
  ]
}

3. Upload a file

Upload CSV, XLSX, or JSON via the Upload file field in the Apify Console.

File type	Required columns	Mode
CSV / XLSX	email	verify
CSV / XLSX	fullName + domain (or name + website)	finder
JSON	{ "emails": [...] }	verify
JSON	[{ "fullName", "domain" }]	finder

Mixed input is rejected: do not combine emails and finder records in one run unless you set legacy mode explicitly.

Output

Each dataset row includes:

Field	Description
mode	verify or finder
status	valid, invalid, unknown, found, not_found, etc.
email / foundEmail	Verified or discovered address
verificationMeta	SMTP, MX, catch-all, provider, browser flags
fromCache	true when served from MongoDB prior cache
isSummary	Final row with batch stats

Advanced options (collapsed in Console)

• mode — force verify or finder (overrides auto-detection)
• inputFileUrl / inputFileKey — programmatic file input
• batchSize, maxConcurrency, priorCacheEnabled — throughput and cache toggles

Infrastructure (Actor owner / maker pays)

This Actor requires owner-configured environment variables on the Apify Actor (not in user input):

• MONGO_URL — prior verification cache
• REMOTE_SMTP_* — remote SMTP API
• WEBSHARE_PROXY_* — residential proxy for browser checks

Users only provide emails, records, or files. Apify Proxy is not used; browser checks use Webshare.

Limits

• Default memory: 4096 MB
• Max run timeout: 24 hours
• Recommended batch sizes: up to 100 items per run for reliable finder browser checks; larger lists use checkpointing but may take longer per item on Google/Outlook MX domains.

Example API run

apify actors start opalescent_zygote/email-verifier-finder \
  --input '{"emails":["test@example.com"]}' \
  --memory 4096

Legacy input (backward compatible)

{
  "mode": "verify",
  "emails": ["john@example.com"]
}

{
  "mode": "finder",
  "records": [{ "fullName": "John Doe", "domain": "company.com" }]
}