# B2B Leads Finder | $1/1K | Emails & Phones | Like Apollo (`x_guru/b2b-leads-finder`) Actor

300M base | Find B2B leads by job title, seniority, location, industry and company size. Get work and personal emails, LinkedIn URLs and available phone numbers from a professional database. Export CSV or JSON.

- **URL**: https://apify.com/x\_guru/b2b-leads-finder.md
- **Developed by:** [Hundevmode Labs](https://apify.com/x_guru) (community)
- **Categories:** Lead generation, Jobs, Automation
- **Stats:** 790 total users, 17 monthly users, 100.0% runs succeeded, 26 bookmarks
- **User rating**: 1.46 out of 5 stars

## Pricing

$19.99/month + usage

To use this Actor, you pay a monthly rental fee to the developer. The rent is subtracted from your prepaid usage every month after the free trial period. You also pay for the Apify platform usage, which gets cheaper the higher Apify subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#rental-actors

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## B2B Leads Finder with Emails and Phones

Build B2B prospect lists by job title, seniority, location, industry and company size. This Apollo alternative returns available contact and company fields from a professional database, without requiring an Apollo subscription.

### How to use

1. Enter your filters or LinkedIn profile URLs in the Input tab.
2. Choose the contact fields and result filters you need.
3. Set the run spending limit and start the Actor.
4. Export the results from the Dataset tab as CSV, JSON or Excel, or retrieve them with the Apify API.

```json
{
  "max_results": 100,
  "job_titles": [
    "Software Engineer"
  ],
  "person_location_country": [
    "United States"
  ],
  "include_emails": true,
  "include_phones": false
}
```

### Input

| Field | Behavior |
| --- | --- |
| `max_results` | Requested output size, up to 100,000 per run. |
| `job_titles`, `job_title_seniority` | Role and seniority filters. |
| `person_location_country`, `person_location_region`, `person_location_locality` | Person location filters. |
| `industries`, `employee_size`, `company_websites` | Industry, company size and domain filters. |
| `include_emails` | Include available email fields. Defaults to true. |
| `include_phones` | Require a phone number. Defaults to false. |
| `start_after_id` | Cursor from the previous run’s `PAGINATION` record. |

The Input tab lists all supported options. This is a database lookup; it does not sign into LinkedIn or scrape live profile pages. Contact availability is not guaranteed, and the database may contain older records.

### Results and matching

Search filters select existing database records. Available fields vary by profile. With email output enabled, the default email filter excludes profiles without an available email. Selecting `include_phones` requires an available mobile phone number. The email-status labels describe database filtering; the Actor does not perform a live SMTP verification.

Returned profiles contain the available name, job and company fields together with the requested contact fields and a LinkedIn URL. CSV and JSON exports use the same underlying results.

### Pricing

**Scheduled migration:** pay-per-event pricing takes effect on **October 14, 2026, at 05:34 UTC**. Before that timestamp, the existing **$19.99/month rental** tariff remains active. The PPE prices below apply from that timestamp. The Store Pricing tab is the source of truth.

Pay per event: **$1 per 1,000 exported results** ($0.001 per result). The synthetic Actor Start event is **$0.00005 per allocated GB, with a minimum of one event**. Apify handles these events automatically. Your run spending limit can stop output before the requested maximum.

**Apify Free plan:** up to **500 exported profiles per UTC calendar month**. This is an output limit, not a promise of zero-cost results: the published event prices still apply and use your Apify credits. Checked URLs that produce no output do not consume this allowance. The allowance belongs to this Actor and does not change the counters of other Actors. Paying Apify users and the Actor owner bypass this monthly cap; per-run limits and the run budget still apply.

Concurrent runs reserve quota before exporting. Successfully unused slots are returned to the allowance. An interrupted upload with an unknown outcome retains its reservation to prevent duplicate exports from bypassing the cap. Quota details are saved in the `QUOTA` key-value record. Errors are saved in `ERROR`, never as paid result rows.

This code supports the rental transition and PPE. The Actor ID stays the same while the technical name now matches the Finder positioning.

### Pagination and integration

For the next page, copy `PAGINATION.next_start_after_id` into `start_after_id` and keep the same filters. The cursor points to the last delivered profile, including when the budget stops a batch partway through. Cursor pagination is preferable to deep offsets.

The Actor ID is preserved. The technical name is now `b2b-leads-finder`, replacing the old rental/subscription URL label. API integrations using the Actor ID keep the same reference; update any integrations that use the old technical name. The visible title and search description distinguish this Finder listing from the paired Scraper.

Powered by [Dievio](https://dievio.com).

# Actor input Schema

## `max_results` (type: `integer`):

Maximum number of profiles to return

## `first_name` (type: `string`):

Person's first name

## `last_name` (type: `string`):

Person's last name

## `job_titles` (type: `array`):

Add one or multiple job titles to search for

## `job_title_seniority` (type: `array`):

Filter by job seniority level (Owner, CXO, VP, Director, Manager, Senior, Entry, etc.)

## `job_departments` (type: `array`):

Filter by department (Engineering, Sales, Marketing, Finance, Operations, HR, Product, Design, Data, Legal, etc.)

## `employee_size` (type: `array`):

Company size filter: 1-10, 11-50, 51-200, 201-500, 501-1000, 1001-5000, 5001-10000, 10001+

## `person_location_country` (type: `array`):

Filter by person's country (select from list)

## `person_location_region` (type: `array`):

Filter by person's state/region (US states + major regions)

## `person_location_locality` (type: `array`):

Filter by person's city

## `industries` (type: `array`):

Filter by industry (multiple selection)

## `industry_keywords` (type: `array`):

Keywords related to industry

## `company_revenue` (type: `array`):

Company revenue range: $0-1M, $1M-10M, $10M-50M, $50M-100M, $100M-500M, $500M-1B, $1B-10B, $10B+

## `inferred_salary` (type: `array`):

Filter by estimated salary range

## `funding_start_date` (type: `string`):

Filter companies funded after this date (YYYY-MM-DD)

## `funding_end_date` (type: `string`):

Filter companies funded before this date (YYYY-MM-DD)

## `business_model` (type: `array`):

Filter by business model: B2B, B2C, B2B2C, Marketplace, SaaS, E-commerce

## `company_location_country` (type: `array`):

Filter by company's country (select from list)

## `company_location_region` (type: `array`):

Filter by company's state/region (US states + major regions)

## `company_location_locality` (type: `array`):

Filter by company's city

## `company_websites` (type: `array`):

Filter by company website domain

## `email_status` (type: `string`):

Filter by email availability

## `include_emails` (type: `boolean`):

Include email addresses in results

## `include_phones` (type: `boolean`):

Only return profiles with phone numbers

## `start_after_id` (type: `string`):

Recommended pagination for large exports. After a run, open the PAGINATION key-value record and copy next\_start\_after\_id here to fetch the next batch without duplicates.

## `page` (type: `integer`):

Simple page number for small exports. Page 2 skips the first Max Results records. For large exports, use Start after ID instead.

## `offset` (type: `integer`):

Optional exact number of matching records to skip. Deep offsets can be slower than Start after ID.

## Actor input object example

```json
{
  "max_results": 10000,
  "funding_start_date": "2020-01-01",
  "funding_end_date": "2024-12-31",
  "email_status": "all",
  "include_emails": true,
  "include_phones": false,
  "start_after_id": "john-smith-123456",
  "page": 1
}
```

# Actor output Schema

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

No description

## `quota` (type: `string`):

No description

## `error` (type: `string`):

No description

## `pagination` (type: `string`):

No description

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("x_guru/b2b-leads-finder").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("x_guru/b2b-leads-finder").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 '{}' |
apify call x_guru/b2b-leads-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,x_guru/b2b-leads-finder"
        }
    }
}
```

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/JZ1PjtruiQSJeMQ6i/builds/P4hTz2GL06Z2rh73t/openapi.json