People Finder & Email Verifier

👤 What can People Finder do?

Give it a company domain and it returns the senior decision-makers you actually want to reach, with a verified work email and the evidence behind every match. One flat row per person.

It runs a four-layer cascade, company-match scores every candidate so you do not get ex-employees or people at similarly named companies, then runs a two-provider email waterfall and a two-stage deliverability check that resolves catch-all domains instead of shrugging at them.

📦 What you get	⚙️ Features and integrations
👤 Name, title, LinkedIn URL, verified email 🪜 9 seniority levels and 14 departments, normalized 🎯 match_confidence, so no wrong-company results 🧾 27 flat fields, snake_case, one row per person	🚫 This actor never requests linkedin.com, enforced in its own transport layer 🪜 Four-layer cascade, cheapest source first ✅ Catch-all resolution, not a shrug ⬇️ Export to JSON, CSV, Excel, HTML or XML

Bought by outbound teams, recruiters and RevOps for Clay enrichment, CRM fill and prospecting.

🚫 People Finder sends zero requests to linkedin.com. No page fetches, no cookies, no authentication, no session. Profile URLs come from a search provider's public index and from licensed database APIs. This is enforced in People Finder's own code at the HTTP transport layer, not left to convention. It describes how this actor works. It is not a statement about other Mamba Labs actors, which use whatever sources their own job needs.

💡 Why use People Finder?

If you want	Read these fields
The person	full_name, job_title, linkedin_profile_url
To filter by rank or function	seniority, department
A deliverable address	email, email_status, email_verified
To trust the match	match_confidence, matched_filters, source
Where they are	country, city
Email provenance	email_provider, email_source, verification_source, email_confidence

🎯 Company matching, not keyword matching

A search for "Stripe" ("CRO" OR "VP of Sales") returns everyone whose page mentions Stripe: former employees, investors, advisors, and people at Stripes Clothing Co.

This actor parses the current-position clause of the headline, the profile subtitle, semicolon-delimited role history and comma-form employer names, then drops anyone who cannot be shown to currently work at the target.

Measured on a 20-company benchmark: 554 candidates in, 219 kept, zero wrong-company results in the delivered set.

✅ Verification that resolves catch-alls

Most verifiers stop at "risky" on a catch-all domain and leave you guessing. This one escalates those addresses to a second provider that determines whether that specific mailbox exists.

email_verified is true only on a definitive answer, false only on a definitive bounce, and null when genuinely unresolved. Three distinct facts, never collapsed into two.

🪜 The four-layer cascade, cheapest first

The cascade stops as soon as it has enough people who would survive your filters, not merely enough raw candidates.

Layer	Source	Notes
0	Cache	Keyed by domain and your exact filter set, so a narrow search never reads a broad one's rows. 7 day TTL, 14 days for search-backed results. A cache hit costs nothing.
1	The company's own website	robots.txt honored, then /team, /about, /leadership, /people and four more. Free, and the strongest evidence available.
2	Search API	At most three searches per company. Requires your Serper key.
3	Licensed database	Fires only on a shortfall, asks only for the shortfall. Requires your Icypeas key.

Then: dedupe and merge across layers, normalize titles and locations, suppress opted-out profiles, enforce your filters, discover email, verify email.

📋 What data can People Finder extract?

27 fields per person. The ones buyers use:

Field	What it holds
full_name, first_name, last_name, name_normalized	The person's name, split and normalized
job_title, headline	The title as published, and the fuller headline
seniority	One of 9: founder, c_suite, vp, director, head, manager, senior, individual_contributor, entry
department	One of 14, from executive and sales through revops, legal and other
linkedin_profile_url	From a public index or licensed API, never scraped
country, city	Normalized location
email, email_status, email_confidence	The address and how sure we are
email_verified, verification_source, email_provider, email_source	Who found it and who confirmed it
position_verified, position_verification_reasoning	Optional current-role check
match_confidence, matched_filters, source	Why this person is on your list
company_domain, company_name, linkedin_company_url	The company they were matched to
run_date	When the run happened

⚠️ email_verified: null is not false. true means a provider confirmed delivery, false means a provider confirmed a bounce, and null means nobody could resolve it. Treating null as a bad address throws away deliverable contacts; treating it as good sends into the dark. It is a separate fact and it is reported as one.

⚠️ false and null mean different things on every row. false is a measurement: the actor looked and the answer was no. null is the absence of one: the actor could not look. When something it needed fails, the row comes back with degraded: true, a plain-language degradation_reason, and every field it could not measure set to null rather than to a confident false or 0. Filter on degraded before you trust a negative.

🛠️ How to find decision-makers at a company

1. Open the Input tab and put a bare domain in domain.
2. Set targetCount to how many people you want per company.
3. Narrow with seniority, departments, jobTitles or countries.
4. Add your provider keys. See the key section below for which layers need which.
5. Click Start, then filter on match_confidence and email_verified.

🧪 Using it in Clay

Add an Apify enrichment column and map your domain column to domain. One row per person lands directly in a contact table.

Use suppressLinkedInUrls to feed one run's output back as the next run's suppression list. URLs are canonicalized before matching, so locale subdomains, tracking parameters, casing and trailing slashes all match the same person.

🔑 Which keys you need

Key	Unlocks
serpApiKey (Serper)	Layer 2, search discovery
icypeasApiKey	Layer 3, licensed database fallback
prospeoApiKey	Email discovery
reoonApiKey, bounceBanApiKey	Email verification, including catch-all resolution
claudeApiKey	Optional position verification

Third-party API costs are separate and are not marked up. Your providers bill your own accounts directly.

💵 How much does it cost to find people at a company?

You are billed for what the actor delivers, not for attempts. The primary event is person-found.

Event	Free	Bronze	Silver	Gold	Charged when
person-found	$0.020	$0.019	$0.018	$0.017	Per person returned that passed company matching and all your filters
company-searched	$0.020	$0.019	$0.018	$0.017	Once per company that reaches a paid layer
email-found	$0.040	$0.038	$0.036	$0.034	Only when an email is actually returned
email-verified	$0.015	$0.01425	$0.0135	$0.01275	Per email confirmed deliverable
position-verified	$0.015	$0.01425	$0.0135	$0.01275	Per position check, when verifyPosition is on
serp-query	$0.003	$0.00285	$0.0027	$0.00255	Per search issued, at most three per company

There is also an Actor start event at $0.00005, charged once per run per GB of memory.

Worked example at Free-plan prices, 10 companies, targetCount: 10, full pipeline:

Line	Calculation	Cost
Companies searched	10 × $0.020	$0.20
Search queries	up to 30 × $0.003	$0.09
People found	100 × $0.020	$2.00
Emails found	100 × $0.040	$4.00
Emails verified	100 × $0.015	$1.50
Total		about $7.79

That is roughly $0.078 per fully enriched, verified contact. Names and titles only, with no email discovery, comes to about $2.29 for 100 people, or $0.023 each.

💳 A cache hit costs nothing: no company-searched, no person-found. Suppressed profiles are removed before any billing event fires, so anyone on your suppression list costs you nothing either. Free Apify plans get 50 people per month and no email discovery or verification; those runs still return fully resolved, company-verified, seniority-classified people, and the run summary says so explicitly rather than leaving you to infer it.

⌨️ Input

Everything is on the Input tab. The options worth explaining:

Field	Type	Default	What it does
domain	string	none	The company domain.
company_name, linkedin_company_url	string	none	Sharpen company matching.
domains	array	none	Batch.
targetCount	integer	5	People wanted per company.
jobTitles, excludeJobTitles	array	none	Title include and exclude lists.
seniority, departments	array	none	Filter on the normalized taxonomies.
countries	array	none	Location filter.
includeEmails	boolean	true	Run email discovery.
verifyEmails	boolean	true	Run verification, including catch-all resolution.
verifyPosition	boolean	false	Confirm the person currently holds the role.
suppressLinkedInUrls	array	none	Profiles to exclude, before billing.
batchSize	integer	5	Companies in flight at once.
skipCache	boolean	false	Ignore the cache.

📤 Output

One flat row per person, exportable as JSON, CSV, Excel, HTML or XML.

{
  "full_name": "Jane Doe",
  "first_name": "Jane",
  "last_name": "Doe",
  "job_title": "VP of Revenue Operations",
  "seniority": "vp",
  "department": "revops",
  "linkedin_profile_url": "https://www.linkedin.com/in/example",
  "country": "United States",
  "city": "San Francisco",
  "company_domain": "example.com",
  "company_name": "Example Inc",
  "email": "jane.doe@example.com",
  "email_status": "valid",
  "email_verified": true,
  "email_provider": "prospeo",
  "verification_source": "bounceban",
  "email_confidence": 0.97,
  "match_confidence": 0.94,
  "matched_filters": ["seniority:vp", "department:revops"],
  "source": "website",
  "run_date": "2026-07-23T13:02:40.980Z"
}

💡 Tips

• Feed each run's linkedin_profile_url values back in as suppressLinkedInUrls. Suppression happens before billing, so repeat runs get cheaper as your contacted list grows.
• Filter on seniority rather than on title strings. Head of Revenue Operations, VP, RevOps and CRO all become filterable values.
• Set targetCount honestly. The cascade stops as soon as it has enough people who pass your filters, so a lower number costs less at every layer.
• Leave verifyEmails on. Catch-all resolution is the part most verifiers skip.

⚠️ Known limits

Coverage depends on which keys you supply. With no search or database key, the actor runs on layer 1 only, which finds people the company publishes about itself and nobody else.

email_verified: null is a real outcome, not a failure. Some mailboxes cannot be resolved by any provider.

Free Apify plans get names and titles only. Email discovery and verification are unavailable on the free plan, capped at 50 people per month.

Position verification is optional and off by default. When on, it bills per check and needs a Claude key.

Third-party provider costs are yours. The event prices above cover this actor's compute and orchestration only.

Results are cached for 7 days, or 14 for search-backed results, keyed by domain and your exact filter set.

❓ FAQ

Does it scrape LinkedIn?

No. People Finder makes zero requests to linkedin.com, with no cookies, no authentication and no session, enforced at its own HTTP transport layer. Profile URLs come from a search provider's public index and from licensed database APIs.

Why did I get fewer people than targetCount?

The cascade stops when it runs out of candidates who survive your filters. Loosening seniority or departments usually finds more.

What is the difference between email_verified: false and null?

false means a provider confirmed the address bounces. null means nobody could resolve it. Do not treat them the same way.

Can I stop someone appearing in future runs?

Yes. Put their profile URL in suppressLinkedInUrls. They are removed before any billing event fires, so they cost you nothing, and URLs are canonicalized so one form matches all.

Who is the data controller?

You are. See Support below.

🧩 Want other GTM data?

Mamba Labs builds custom actors for B2B go-to-market teams. The public versions of that work live here on the Store, so our users get the same tooling we build under contract.

🧑‍💼 GTM Hiring Signal Scraper	🧱 Tech Stack Detector
📡 B2B Buying Signals Aggregator	🔑 Job Board Keyword Scanner
🔗 Domain to LinkedIn URL Resolver	🎯 ICP Fit Scorer
📋 Job Posting Monitor	📬 Domain Deliverability Checker
🏢 Company Firmographic Enricher	🌐 Company Social Presence Mapper
🪪 Company Identity Resolver	💰 Funding and Press Signal Scanner
🔄 Company Change-Event Feed	🚀 Prospect Engine
🤖 AI Tooling Detector	📮 Outbound Stack Detector
📝 Publishing Frequency Tracker	✉️ Work Email Waterfall Finder
⏩ Sequencer Lead Push	🏅 Workplace Program Detector
👥 Team Page People Extractor	🧭 Company Discovery List Builder

Every actor in the suite takes a domain or a company and returns one flat row, so they stack in the same Clay table without reshaping anything.

🛠️ Need something custom built for you or your team? Tell us what you are trying to find and we will build it. Talk to Mamba Labs.

🆘 Support

Something wrong, or a person matched to the wrong company? Open an issue on the Issues tab with the domain and the row, and we will look at it.

ℹ️ GDPR, privacy and sourcing. This actor returns B2B contact data from publicly accessible sources and licensed provider APIs. You are the data controller under GDPR, CCPA and applicable privacy laws. Use it for legitimate B2B prospecting only, and comply with transparency and opt-out obligations when using enriched data in outreach. People Finder sends no requests to linkedin.com, uses no cookies, and transmits no authentication tokens or session credentials to any social network, and retains no personal data after a run completes: results live in your own Apify dataset, under your control. suppressLinkedInUrls lets you honor removal requests so someone who asked to be excluded never re-enters your pipeline. To submit a data subject request, contact privacy@mambabuilt.com.

Built by Mamba Labs.