# B2B People Search ✅ Work Emails ✅ Apollo | ZoomInfo | Lusha (`lead_king/people-search`) Actor

🔥 Find decision-makers by job title, seniority, department, industry, location & company size. Returns verified work ✉️ emails, LinkedIn profiles & firmographics. Cheap Apollo, ZoomInfo & Lusha alternative — no API key needed.

- **URL**: https://apify.com/lead\_king/people-search.md
- **Developed by:** [Lead King](https://apify.com/lead_king) (community)
- **Categories:** Lead generation, Agents, AI
- **Stats:** 10 total users, 5 monthly users, 73.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 lead fetcheds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## B2B People Search — Work Emails, LinkedIn & Firmographics

Find decision-makers by **job title, seniority, department, industry, location
and company size** — and get back their **work email**, LinkedIn profile and
company firmographics.

A cheap alternative to Apollo, ZoomInfo, Lusha and Seamless. **No API key and
no subscription** — you need only Apify credits, and you pay per lead returned.

### What you get per lead

| Field | Example |
| --- | --- |
| Full name | Dana Whitfield |
| Job title | Head of Revenue Operations |
| Headline | Scaling RevOps at Series B SaaS |
| Seniority | Head |
| **Work email** | dana@acme.com |
| Email risk score | A |
| LinkedIn URL | https://linkedin.com/in/… |
| Company | Acme Analytics |
| Company website | acme.com |
| Company size | 51-200 |
| Company revenue | $10M - $20M |
| Company industry | Information Technology |
| Country | United States |

Export to **CSV, Excel, JSON** or pull via API — straight into your CRM or
sequencer.

### How to use it

1. Set **Job title / keywords** (e.g. `Head of Sales`) and/or any exact filter.
2. Optionally narrow by **seniority, department, industry, company size,
   revenue, country, state, city, company domain**.
3. Set **Max leads** (up to 500 per run).
4. Run. Results land in the dataset as they are found.

**You must set at least one filter** — the run fails fast if none are given
rather than charging you for an untargeted dump.

#### Getting good results

- **Country is the safest filter to combine** — it is present on ~99% of
  records. Seniority, department and industry are present on ~60%, and NAICS /
  LinkedIn industry on ~50%, so stacking several exact filters at once narrows
  results sharply.
- **Company domain beats company name.** `salesforce.com` is unambiguous;
  `Salesforce` is not.
- **State and city need full names with standard capitalization** — `Texas`,
  not `TX`.
- If a run comes back empty, remove your narrowest filter first (usually city,
  NAICS or LinkedIn industry).

### Pricing

**Pay per result.** You are charged one `lead-fetched` event per person pushed
to the dataset, plus the platform's standard per-run start fee.

- Leave **"Only people with a work email"** on (the default) and you are
  charged only for people who have a deliverable work email.
- Turn it **off** to also receive profiles that have a name, role, company and
  LinkedIn but no email — these are still charged as leads.

Emails graded as hard-bounce risk are removed before you are charged for them.
Set a **max cost per run** in the Console to cap spend; the run stops cleanly
when it is reached.

### Limits

- **500 leads per run.** Run again with a different filter set (or a different
  city/industry) to build a larger list.
- The upstream source enforces a rolling rate budget. If it is reached mid-run,
  you get the leads found so far, a clear status message, and you are charged
  only for what was delivered. Trying again a few hours later gets more.

### Support

Found a problem or need a filter that isn't here? Open an issue on the Actor's
Issues tab.

# Actor input Schema

## `searchQuery` (type: `string`):

Free-text keyword search. ⚠️ Keyword-only searches cannot return work emails — the provider serves them from a reduced index — and they match on the NAME field, so "Head of Sales" also returns people surnamed Head. For work emails and accurate targeting, use the exact filters below instead.

## `maxLeads` (type: `integer`):

Maximum number of leads to fetch (up to 500 per run). You are charged per lead actually returned.

## `requireEmail` (type: `boolean`):

Skip records that have no deliverable work email. Turn this off to also receive profiles that have a name, role and LinkedIn but no email — note these are still charged as leads.

## `seniority` (type: `string`):

Target one seniority level. Present on roughly 60% of records — leave empty for the widest reach.

## `department` (type: `string`):

Target one department. Present on roughly 60% of records.

## `industry` (type: `string`):

Target one industry. Present on roughly 60% of records.

## `employeeRange` (type: `string`):

Target companies with this many employees.

## `revenueRange` (type: `string`):

Target companies with this annual revenue.

## `companyName` (type: `string`):

Only people working at this company, e.g. "Salesforce". For precise targeting use the company domain below instead.

## `companyDomain` (type: `string`):

Most precise company targeting, e.g. "salesforce.com". Beats company name when you know the domain.

## `country` (type: `string`):

Target one country. Present on roughly 99% of records, so this is a safe filter to combine with others.

## `state` (type: `string`):

Full name with standard capitalization, e.g. "Texas" — not "TX". Combine with Country to disambiguate.

## `city` (type: `string`):

Standard capitalization, e.g. "Austin". Combine with State and Country to disambiguate.

## `linkedinIndustry` (type: `string`):

Exact LinkedIn industry label, e.g. "Software Development". Uses LinkedIn's own vocabulary. Present on roughly 50% of records.

## `naicsCode` (type: `string`):

Exact NAICS industry code, e.g. "541120". Works at any level of the hierarchy (2–6 digits).

## Actor input object example

```json
{
  "maxLeads": 25,
  "requireEmail": true,
  "seniority": "Head",
  "department": "Sales",
  "country": "United States"
}
```

# Actor output Schema

## `results` (type: `string`):

Open the dataset of people found.

## `resultsConsole` (type: `string`):

Browse the leads in the Apify Console.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "maxLeads": 25,
    "seniority": "Head",
    "department": "Sales",
    "country": "United States"
};

// Run the Actor and wait for it to finish
const run = await client.actor("lead_king/people-search").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "maxLeads": 25,
    "seniority": "Head",
    "department": "Sales",
    "country": "United States",
}

# Run the Actor and wait for it to finish
run = client.actor("lead_king/people-search").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "maxLeads": 25,
  "seniority": "Head",
  "department": "Sales",
  "country": "United States"
}' |
apify call lead_king/people-search --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,lead_king/people-search"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/kGwipmDg0tHbBEis2/builds/mLVC7LjxJJNTIsyzZ/openapi.json