# B2B Buying Committee Builder (`thenetaji/linkedin-buying-committee-builder`) Actor

Map the whole group who decides on a purchase at a company, not just one contact. Returns the likely economic buyer, champion, technical evaluator and blocker for the department you sell into, each with a work email. Everyone is confirmed to hold a current role at the company.

- **URL**: https://apify.com/thenetaji/linkedin-buying-committee-builder.md
- **Developed by:** [The Netaji](https://apify.com/thenetaji) (community)
- **Categories:** Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 committee members

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#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 Buying Committee Builder

Enterprise deals are not won by finding one contact. They are won by reaching the person who signs, the person who feels the problem, and the person who can stop it on technical or legal grounds. The Actor returns that whole group for a company, for the department you sell into, with a work email for each.

Everyone returned is confirmed to hold a current role at the target company. Ex-employees, people who merely mention the company, and similarly named companies are excluded rather than returned for you to filter.

### Accepted input

| Field | Type | Default | Description |
|---|---|---|---|
| `target_company` | array of strings | `["Stripe"]` | Required. One line per company. A name, a LinkedIn company URL, or a website — all work. |
| `department` | select | `sales` | Required. The function you sell into. Determines how each person is labelled. |
| `verify_emails` | boolean | `false` | Confirm each address against the company's mail server. |
| `search_depth` | integer | `3` | Batches of seniority titles to sweep, `1`–`5`. Higher finds more people and takes longer. |
| `max_candidates` | integer | `3` | Ranked candidate addresses per person. |
| `maxItems` | integer | `100` | Maximum committee members saved. `0` removes the limit. |
| `email_domain` | array of strings | `[]` | Override. Leave empty unless the company mails from a domain other than its website. |
| `github_org` | array of strings | `[]` | Override. Leave empty unless the company publishes code under an unrelated name. |

```json
{
  "target_company": ["Northwind Robotics"],
  "department": "engineering",
  "verify_emails": true
}
```

The company's email domain and GitHub organisation are worked out from the company line; the overrides are there for the rare case those lookups get wrong.

### The four roles

| `committee_role` | Who it is |
|---|---|
| `economic_buyer` | Holds the budget. Chief officers, and VP-level leaders above the target department. |
| `champion` | Senior inside the department you sell into. Feels the problem and argues for the purchase internally. |
| `technical_evaluator` | Engineering leadership on a purchase engineering does not own. Judges whether it works. |
| `blocker` | Legal and finance leadership outside their own remit. Can stop a deal regardless of who wants it. |

These are inferred from job titles, which is the only public signal for them. They are a starting map for multi-threading a deal, not a statement about how the company actually runs.

### What comes back

Each row carries the person's name, headline, seniority, committee role, LinkedIn profile URL, and their best-match work email with a confidence score. With `verify_emails` enabled, `email_status` reads `verified` only when the mailbox is confirmed to exist.

Some company domains accept mail addressed to anything, so no service can confirm a mailbox there. The Actor detects this before spending anything, says so on each row via `domain_verifiable`, and does not charge the verified add-on for those companies.

### What it cannot do

Coverage depends on what search engines have indexed for the company, so this is discovery rather than a complete directory. Small companies and those whose staff keep sparse public profiles will return fewer people.

Email confidence is reported per person rather than per company, because a compound surname or a hyphenated given name can render differently from a simple one at the same employer.

### Pricing

Charged per committee member returned. A company that yields nobody costs nothing. The verified add-on is charged only when a mailbox is actually confirmed.

# Actor input Schema

## `target_company` (type: `array`):

One line per company. A name (Stripe), a LinkedIn company URL, or a website (stripe.com) — all work. The email domain and everything else is worked out from this.

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

The function whose buying committee you want. Each person is labelled economic buyer, champion, technical evaluator, or blocker for a purchase in this department.

## `verify_emails` (type: `boolean`):

Confirm each address against the company's mail server before returning it. Around 40% of company domains accept every address (catch-all), where no mailbox can be confirmed by anyone — those are reported as unverifiable rather than guessed at, and are never charged for.

## `alternate_emails` (type: `boolean`):

Return the runner-up addresses alongside the best one, each with the format rule and confidence behind it. Off by default: one address per person is the answer, and a column of near-identical alternates next to it reads as uncertainty rather than as options. Turn it on when you intend to try the alternates after a bounce.

## `maxItems` (type: `integer`):

Maximum committee members to save across all companies. Set 0 for no limit.

## Actor input object example

```json
{
  "target_company": [
    "https://www.linkedin.com/company/datadog/"
  ],
  "department": "sales",
  "verify_emails": false,
  "alternate_emails": false,
  "maxItems": 20
}
```

# Actor output Schema

## `dataset` (type: `string`):

All records scraped by this run

# 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 = {
    "target_company": [
        "https://www.linkedin.com/company/datadog/"
    ],
    "maxItems": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("thenetaji/linkedin-buying-committee-builder").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 = {
    "target_company": ["https://www.linkedin.com/company/datadog/"],
    "maxItems": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("thenetaji/linkedin-buying-committee-builder").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 '{
  "target_company": [
    "https://www.linkedin.com/company/datadog/"
  ],
  "maxItems": 20
}' |
apify call thenetaji/linkedin-buying-committee-builder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,thenetaji/linkedin-buying-committee-builder"
        }
    }
}

```

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/DOHg58KLy1s5UKCAL/builds/bt6aVfqN6p57iBEMY/openapi.json