Company Employee & Email Finder: Team Pages to Leads avatar

Company Employee & Email Finder: Team Pages to Leads

Pricing

from $1.40 / 1,000 person founds

Go to Apify Store
Company Employee & Email Finder: Team Pages to Leads

Company Employee & Email Finder: Team Pages to Leads

Find the people companies list on their own websites: names, job titles, work emails and LinkedIn profiles from team, about and contact pages. Pay per person.

Pricing

from $1.40 / 1,000 person founds

Rating

0.0

(0)

Developer

earlytern

earlytern

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

an hour ago

Last modified

Features

Limited permissions

Share

Turn a list of company domains into a list of people: the founders, leaders and staff each company publishes on its own website (team, leadership, about, contact and press pages), with job title, work email when the website publishes it, and LinkedIn profile when the website links it. Optionally, learn the company's email pattern (first.last@) from the emails it publishes and fill in a guessed email for the other people. One row per person, ready for your CRM or lead list. You pay only for people found.

What does Company Employee & Email Finder do?

  • Finds the pages that list people: reads the home page, follows its links to team, leadership, management, board, about, contact and press pages (in English, German, French, Spanish and Dutch), and looks in the website's sitemap when the home page links no team page.
  • Reads people, not noise: names come from organization data (schema.org Person), from rows of team cards, from name-and-title lists and from email links with a name. A name must look like a person's name and come with a job title, an email or a LinkedIn profile. Menus, headings, testimonials and customer quotes are left out.
  • Work emails as published: an email next to a person, on the company's own domain, goes in email with emailSource: "found". Team addresses (info@, sales@) and addresses on other domains are never given to a person.
  • Email pattern and guessed emails (optional): with Guess missing emails on, the Actor learns the pattern from at least two published emails that follow the people's names and builds the same kind of address for people without one, in guessedEmail. Guessed emails are not checked.
  • One person once per company: the same person on several pages is merged into one row.
  • Light and polite: plain HTTP requests, no browser; always obeys robots.txt and never logs in. LinkedIn and other platforms are never visited.

Who uses it?

  • Sales and SDR teams finding decision makers (CEO, founders, heads of sales, marketing or engineering) at target accounts.
  • Lead generation agencies turning a domain list into contacts with job titles.
  • Recruiters mapping the team of a company.
  • Investors and researchers listing the leadership of many companies.
  • AI agents that need "who works at example.com?" in structured form.

How to use it

  1. Click Try for free.
  2. In Domains, paste company domains or website addresses, one per line: example.com, https://www.example.com/about.
  3. Optional: turn on Guess missing emails, or change Pages per website (15 by default, up to 50).
  4. Click Start. Download the results as JSON, CSV or Excel, or use the API. The People view shows one row per person.

Use with AI agents (MCP)

AI assistants and AI agents can call this Actor through Apify's MCP server at mcp.apify.com or through the Apify API. Send the whole list of domains in one call. Questions it answers well:

  • "Who leads example.com?" Read name and jobTitle of the rows for that domain.
  • "Find the head of sales at these 50 companies." Filter jobTitle.
  • "What is the email of Jane Doe at example.com?" Read email; with guessing on, guessedEmail (not checked).

Only domains is required. Rows with type other than person are free and say why in message.

Input example

{
"domains": ["creativecommons.org", "mozilla.org"],
"maxPagesPerDomain": 15,
"guessEmails": true
}

Output example

A real row from a test run:

{
"type": "person",
"input": "mozilla.org",
"domain": "mozilla.org",
"companyName": "Mozilla",
"name": "Mark Surman",
"firstName": "Mark",
"lastName": "Surman",
"jobTitle": "President, Mozilla",
"email": null,
"emailSource": null,
"guessedEmail": null,
"emailPattern": null,
"linkedinUrl": "https://www.linkedin.com/in/msurman",
"pageUrl": "https://www.mozilla.org/en-US/about/leadership/",
"message": null,
"scrapedAt": "2026-11-16T05:52:57.816Z"
}

This website publishes no emails for its people. For a company that does, with Guess missing emails on, two rows look like this:

[
{ "name": "Jane Doe", "jobTitle": "Head of Sales", "email": "jane.doe@example.com", "emailSource": "found", "guessedEmail": null, "emailPattern": "first.last@example.com" },
{ "name": "John Roe", "jobTitle": "CTO", "email": null, "emailSource": "guessed", "guessedEmail": "john.roe@example.com", "emailPattern": "first.last@example.com" }
]

Fields

FieldWhat it holds
typeperson for a person (charged); other values are free rows, see below
inputThe line as you typed it
domainThe company's domain, without www
companyNameThe company's name, from its home page
name, firstName, lastNameThe person's name as the website writes it, without titles such as Dr.; lastName is everything after the first name, without middle initials
jobTitleJob title as the website writes it
emailThe person's work email, published on the website next to their name
emailSourcefound (published) or guessed (built from the pattern); empty when there is no email
guessedEmailOnly with Guess missing emails: an address built from the website's email pattern. Not checked
emailPatternOnly with Guess missing emails: the pattern learned from the website's emails, such as first.last@example.com
linkedinUrlThe person's LinkedIn profile, when the website links it next to the person
pageUrlThe page the person was found on
messageWhy a domain has no people, or why rows were not saved
scrapedAtWhen the row was saved (UTC)

Row types

typeMeaningCharged
personOne person the company publishes on its websiteYes
no_peopleThe website was read, but no person with a name and job title was foundNo
not_foundThe domain is parked or for sale, or its home page is not a web pageNo
needs_browserThe home page is built with JavaScript in the browser, so its links could not be readNo
blockedThe website refused the request or shows a bot checkNo
robots_txtThe website's robots.txt does not allow reading itNo
unreachableThe domain does not exist, did not answer, or answered with an errorNo
not_allowedA large platform, an IP address, a local or private network address; never contactedNo
invalidThe line is not a domain or website addressNo
skippedNot saved because the run reached your maximum cost per runNo

How much does it cost?

You pay only for people found. No start fee, and pages read cost nothing. Prices per 1,000 people, by Apify plan:

EventFreeBronzeSilverGold and up
Person found$2.50$2.00$1.70$1.40
  • Free: domains without people, blocked or unreachable websites, websites that need a browser, invalid lines and duplicates (the same domain twice is read once).
  • Guessed emails cost nothing extra: a person row is charged once, with or without an email.
  • Set a maximum cost per run and the Actor stops cleanly before going over it. People found but not saved, and domains not read, get a free skipped row that says so.

Example on the Free plan: 1,000 domains where 300 websites list 15 people each give 4,500 people and cost $11.25.

FAQ

Why does a company have no people? Many websites do not list their team, or show it only as pictures or inside a script. The Actor returns only people the website itself names in its pages; it does not guess people or look them up elsewhere. Such domains get a free no_people row.

Are guessed emails verified? No. A guessed email follows the pattern of the emails the same website publishes, but it is not checked and may not exist. The Actor never contacts mail servers. Check guessed emails before you send to them, and keep them apart from email, which the website publishes.

When is an email pattern learned? Only when the website publishes at least two work emails that follow the people's names in the same way (for example jane.doe@ for Jane Doe and john.roe@ for John Roe). Otherwise emailPattern stays empty and nothing is guessed.

Does it visit LinkedIn? No. linkedinUrl is a link the company's website puts next to the person. LinkedIn and other platforms are never opened.

Why blocked or needs_browser? Some websites refuse automated requests or only work in a browser. The Actor does not try to get past blocking and does not run a browser; such rows are free.

Can I read more pages? Raise Pages per website (up to 50). Team, leadership and about pages are read first, then contact and press pages.

Limits

  • Up to 10,000 domains per run; 10 websites are read at the same time.
  • Per website: robots.txt, the home page and up to Pages per website pages, with a pause between requests; a robots.txt Crawl-delay is always obeyed. When it asks for a long pause, only the two best pages are read.
  • Pages on the company's own host only; other subdomains (often the same pages in another language) are not read.
  • Up to 500 people per website.
  • Pages larger than 3 MB are read up to 3 MB.
  • The run stops in time to save its results before the run timeout; for very large lists give the run more time.

The Actor reads only public pages of company websites, always obeys robots.txt, never logs in and never tries to get past blocking. It keeps only the fields shown above; no page text is stored.

Personal data: every person row is personal data under laws such as the GDPR: names, job titles, work emails and LinkedIn profiles of people. You need a lawful basis (for example legitimate interest, with a balancing test) to store and use it, you must tell people where you got their data and let them object, and you must follow the anti-spam rules for cold email where you send it. Guessed emails are personal data too, and may reach the wrong person.

Questions and feedback

Open an issue on the Issues tab.