Email Finder 📧 Work Email by Name & Domain ✅ No API Key

Email Finder — Work Email by Name & Domain ✅ No API Key

Email Finder turns a first name, last name and company domain into that person's work email address. Every found email comes back with a confidence level and the provider that resolved it, so you can decide how to use it before you send. Powered by the Neuralverge API. No API key or account required, and every lookup returns exactly one flat row — the email, or an explicit no result row that says why, so a batch never silently loses an input.

Use this email finder for cold outreach, lead generation, recruiting, sales prospecting and CRM hydration — anywhere you already know who the person is and where they work, but not how to reach them.

✨ Why this email finder

• 📄 One flat row per lookup, always — a found email or a no result row that echoes your query and explains what happened. Nothing vanishes from a batch, and a failed run (invalid input, API error, timeout) writes nothing and is never charged.
• 📧 Name + domain → work email — the classic B2B email finder flow, in one call: Steve + Sewell + builder.io → steve@builder.io.
• 🎯 Confidence & provider on every result — the email finder tells you how sure it is and which source resolved the address, instead of handing you a bare string.
• 🔑 No API key, account or credentials — the lookup runs on the Neuralverge backend.
• ⚡ Real-time & structured — a fresh lookup each run, one flat row ready for a spreadsheet, a CRM or an AI pipeline.

🔧 How this email finder works

1. Provide a company domain, first name and last name — e.g. builder.io, Steve, Sewell. One person per run.
2. Run the Actor. The email lookup happens on the Neuralverge backend — no browser, no login, no proxy of your own.
3. Get one flat dataset row per lookup — 8 columns, all at the top level (domain, firstName, lastName, found, email, confidence, provider, message). Export to CSV, JSON or Excel, or pull it over the Apify API.

If no email can be resolved, the run still writes one no result row with found: false and a message — billed like any other row (see Pricing).

Input

One person per run. To work a list, call the Actor once per person from the Apify API or from a Make / Zapier / n8n scenario.

Field	Type	Notes
domain	string	The company domain, e.g. builder.io (with or without www / https).
first_name	string	The person's first name.
last_name	string	The person's last name.

{
  "domain": "builder.io",
  "first_name": "Steve",
  "last_name": "Sewell"
}

What you'll receive

One flat row per lookup. Every field sits at the top level of the row, so the Output tab shows a single table with all 8 columns — there are no nested objects and no views to switch between. Exports (CSV, JSON, XML, Excel) contain exactly the same fields.

Columns: domain, firstName, lastName, found, email, confidence, provider, message.

Nulls are normal. The column set is the same on every run, so a field the source does not expose for this lookup comes back null rather than disappearing — a spreadsheet or CRM mapping built on one run keeps working on the next.

Example output (real run)

A real dataset row, shown in full.

{
  "domain": "builder.io",
  "firstName": "Steve",
  "lastName": "Sewell",
  "found": true,
  "email": "steve@builder.io",
  "confidence": "low",
  "provider": "GOOGLE",
  "message": "Verified mailbox exists"
}

When nothing is found

A lookup that runs but resolves no address still returns a row, so a batch never silently loses an input:

Column	Value
your query fields	domain, firstName, lastName echoed back exactly as submitted
found	false
message	why nothing was returned

Filter these out with found != false (or drop rows where email is empty). This row is billed as one result — see Pricing.

Pricing

Pay per event — $0.010 per email ($10 per 1,000) written to the dataset. There is no run fee and no start fee.

Event	Price	Charged
Actor start	free	never
Failed run — invalid input, API error, timeout	free	never
Row written to the dataset	$0.010 ($10 / 1,000)	every row, including the "no result" row

A completed lookup is billed as one email, found or not. When the source resolves nothing, the Actor writes one explicit no-result row — the query you submitted plus found: false and a message explaining it — and that row is charged at the normal per-email price. A run that fails (missing input, bad key, upstream error) writes no row and costs $0.00.

Pricing is on top of your Apify platform usage.

Rate limit

There is a ceiling on how fast one Apify account can pull from the Neuralverge backend: 10 requests per second for this Actor, counted separately from the other Neuralverge Actors. One run is normally one request, so this is about how many runs you start at once, not about the size of a single run — at typical run times that is dozens of runs in flight at once, which is well above ordinary use.

Updated August 2026: this ceiling was doubled from 5 to 10 requests per second. Bulk jobs that used to hit 429s now go through.

Above the ceiling the backend answers HTTP 429. The Actor waits out the Retry-After it asks for and retries a few times before giving up; a run that does give up writes no row and is not charged.

If you need a higher rate for a bulk job, get in touch.

Free plan limits

Users on any paid Apify plan are not affected by anything in this section.

On the Apify Free plan this Actor may be started 5 time(s) per calendar month per user. A run that finds nothing still counts, because the lookup is performed either way. Every Neuralverge Actor carries its own allowance — running one never uses up another's. When a limit is reached the Actor stops gracefully with a status message naming it; everything resets on the 1st of every month, and any paid Apify plan removes all of it.

Integrations & API

Results are stored in a standard Apify dataset — export as CSV, JSON, XML or Excel, or fetch on demand through the Apify API. The Actor also plugs into Apify's integrations (Make, Zapier, n8n, webhooks) and can be called from any MCP client, so an AI agent can use it as an email finder tool.

🔗 Related Neuralverge Actors

• Email Validation — verify deliverability and mailbox status of an address this email finder returned.
• Reverse Email Lookup — the opposite direction: an email in, the person behind it out.
• LinkedIn People Search — build the list of names and companies to feed this email finder.
• LinkedIn Email Scraper — a work email starting from a LinkedIn profile URL instead of a name + domain.

FAQ

What is this email finder for? Finding a person's professional email address when you know their first name, last name and the domain of the company they work at.

Do I need an account or API key? No. The email lookup runs on the Neuralverge backend, so there is nothing to sign up for and no credentials to share.

Am I charged if no email is found? Yes — a lookup that ran is billed as one result even when it found no address, and you get a no result row that says so. A run that fails (missing input, API error, timeout) writes no row and is not charged.

Can I run this email finder in bulk? The Actor takes one person per run. For a list, call it once per person over the Apify API or from a Make / Zapier / n8n scenario, and the rows land in the same dataset.

What does the confidence level mean? It reflects how likely the email is correct based on the resolving provider. It's a guide, not a delivery guarantee — verify before high-volume sending, e.g. with the Email Validation Actor above.

Why does an email finder ever miss? Some people have no discoverable work address at that domain, and some domains hide their mail entirely. When that happens you still get a row: found: false plus a message telling you which case it was.

---

Disclaimer: This Actor is an independent tool. Use the resulting email addresses in compliance with applicable laws (e.g. GDPR, CAN-SPAM) and only where you have a lawful basis.