Email Pattern Finder: Name + Domain to Work Email avatar

Email Pattern Finder: Name + Domain to Work Email

Pricing

from $2.00 / 1,000 email guess returneds

Go to Apify Store
Email Pattern Finder: Name + Domain to Work Email

Email Pattern Finder: Name + Domain to Work Email

Turn a name and company domain into ranked work-email guesses (first.last@, flast@, first@ and the rest), with an MX check on the domain. No SMTP, no LinkedIn, no paid APIs. $2 per 1,000 people with a best guess; no-MX and not-found are free. By Steadyline Data.

Pricing

from $2.00 / 1,000 email guess returneds

Rating

0.0

(0)

Developer

Steadyline Data

Steadyline Data

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Features

Limited permissions

Share

Email Pattern Finder: ranked work-email guesses from a name and company domain

Give it a person's name and a company domain (or a dataset from Company Team Page Scraper). It generates the usual business email patterns (first.last@, flast@, first@, and the rest), ranks them by how common they are, and MX-checks the domain so you only keep guesses at a domain that actually accepts mail.

This is a pattern engine plus an MX check. It does not open an SMTP session, scrape LinkedIn, query a people database or use a paid API. Mailbox-level confirmation is intentionally out of scope: every guess is flagged notMailboxConfirmed: true and catchAllUnknown: true (catch-all domains cannot be detected without SMTP). Pipe bestEmail into Email Deliverability Checker for typo, disposable and SPF/DMARC context.

  • No logins, no search engines, no third-party data brokers.
  • Not-found is free. People we cannot parse, domains with no mail (no MX / null MX) and DNS failures are returned but never charged.

Use cases

  • Team-page follow-up: take names from Company Team Page Scraper and produce ranked work-email guesses for each person.
  • CRM enrichment: you already have a first name, last name and company domain and need a best-guess address to review.
  • List building after a website pass: pair with Website Contact Scraper when the site published a domain but not a named person's mailbox.

Input

{ "people": ["Jane Smith, python.org", {"firstName": "Guido", "lastName": "van Rossum", "domain": "python.org"}] }

Or pass teamDatasetId with the dataset id from a Team Page Scraper run, plus an optional defaultDomain for names that have no site of their own.

Output sample

{
"name": "Jane Smith",
"domain": "python.org",
"bestEmail": "jane.smith@python.org",
"pattern": "first.last",
"confidence": 33,
"candidates": [{"email": "jane.smith@python.org", "pattern": "first.last", "rank": 1, "score": 33, "weight": 33}],
"mxVerified": true,
"notMailboxConfirmed": true,
"catchAllUnknown": true,
"mailProvider": null,
"status": "ok",
"charged": true
}

status is ok, unparsed-name, missing-domain, no-mx, null-mx, no-such-domain, dns-failed or not-found.

Pricing (pay per event)

EventPriceWhen
email-guessed$0.002One person who received a ranked best-guess on a domain that accepts mail

No-MX, not-found, unparsable names and DNS failures are never charged.

Cost example: 1,000 people with a best guess = $2.00.

Use it from AI agents (MCP), Zapier, Make, n8n or the API

AI agents (Claude, Cursor, VS Code, ChatGPT and other MCP clients). Add Apify's hosted MCP server with just this Actor as a tool:

{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com?tools=steadyline/email-pattern-finder"
}
}
}

Sign in with Apify (OAuth) on first connect, or add an Authorization: Bearer <APIFY_TOKEN> header. Then ask your agent, for example:

Use steadyline/email-pattern-finder to suggest the most likely work emails for Jane Smith at python.org and return the ranked candidates with MX flags.

The agent sees this Actor's input schema and output fields, so it can call it without extra prompting. Agents that use the general Apify MCP server can also find it with search-actors.

This Actor uses pay-per-event pricing with limited permissions, so it can also be run through Apify's agentic payments (no Apify account needed for the agent). See the Apify docs.

Zapier, Make and n8n. Use the official Apify app: Zapier "Run Actor" action, Make "Run an Actor" module, or the n8n Apify node. Choose steadyline/email-pattern-finder, paste the input below, then use "Get dataset items" (or the run's dataset) to send results to Google Sheets, Slack, a CRM or a database.

API (any language). Run it and get the results in one call:

curl -X POST "https://api.apify.com/v2/acts/steadyline~email-pattern-finder/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"people": ["Jane Smith, python.org", {"firstName": "Guido", "lastName": "van Rossum", "domain": "python.org"}]}'

Or with the Python client (pip install apify-client):

from apify_client import ApifyClient
client = ApifyClient("<APIFY_TOKEN>")
run = client.actor("steadyline/email-pattern-finder").call(run_input={"people": ["Jane Smith, python.org", {"firstName": "Guido", "lastName": "van Rossum", "domain": "python.org"}]})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item)

Works well with other Steadyline Data tools

FAQ

Is the best guess a confirmed mailbox? No. This Actor only checks that the domain publishes MX (or implicit MX) records. Every row is flagged notMailboxConfirmed: true and catchAllUnknown: true. Catch-all domains accept every local part, and we do not probe SMTP.

Does it scrape LinkedIn or a people database? No. It is a deterministic pattern engine plus a DNS MX lookup. There is no login, no third-party people API and no paid data.

What if the domain has no mail? The row is returned with status = no-mx, null-mx or no-such-domain and is not charged.

Can I pass a Team Page Scraper dataset? Yes. Set teamDatasetId to that run's dataset id. Each row's name plus site or startUrl is used. You can also paste the dataset items into people.

Can I run it on a schedule? Yes. Create an Apify Schedule (or a saved Task with a schedule) and connect a webhook or integration to receive results.

Need a feature or found a bug? Open an issue on the Issues tab of this page or email steadylinedata@proton.me. Built and maintained by Steadyline Data.

Acceptable use and GDPR

Guessed email addresses can be personal data. You need a lawful basis under GDPR, UK GDPR, CCPA and similar laws to store or use them, and you must follow anti-spam laws (CAN-SPAM, PECR, ePrivacy, CASL). Do not treat a guess as a confirmed mailbox. Do not use the results for harassment or to resell personal data.

Steadyline Data provides this tool as is and does not give legal advice.