# B2B Hiring Intent & Executive Lead Pipeline (All-in-One MCP) (`apexsignal/b2b-hiring-intent-lead-pipeline`) Actor

All-in-one B2B outbound pipeline: detect open ATS jobs (Greenhouse, Lever, Ashby), enrich company domains with emails & tech stack, generate executive emails, and verify DNS MX deliverability in one run.

- **URL**: https://apify.com/apexsignal/b2b-hiring-intent-lead-pipeline.md
- **Developed by:** [Burapa Jaiwat](https://apify.com/apexsignal) (community)
- **Categories:** Lead generation, Jobs, AI
- **Security:** Limited permissions
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.15 / 1,000 complete b2b hiring-intent & verified executive lead dossiers

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
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?

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 Hiring Intent & Executive Lead Pipeline — All-in-One Outbound Intelligence (MCP Ready)

Run a complete **4-stage B2B Hiring-Intent & Lead Enrichment Pipeline in a single click**: detect live open roles on **Greenhouse, Lever & Ashby**, enrich the company's domain with **public emails, social links & 24+ tech stack signals**, generate **decision-maker email permutations**, and **verify every email via deduplicated DNS MX lookup** — with zero LinkedIn/Apollo cookie bans and zero charge for dead domains.

***

### Use Cases

- **One-Click Hiring-Intent Outbound (All-in-One Pipeline):** Instead of chaining 4 separate tools in n8n or Make, pass target companies (`domain` + optional `atsTarget` + optional `executives`) and receive a complete outbound-ready dossier in a single dataset row.
- **Recruiting & Staffing Agency Automation:** Spot companies actively hiring (`HIGH_ACTIVE_HIRING` vs `MODERATE_HIRING`), inspect their open roles (`matchingJobs`), and immediately get MX-verified executive and HR/recruiting contact emails.
- **AI SDR & RevOps Agent Tool (`/mcp`):** Native Apify Standby Mode (`/mcp`) exposes `run_b2b_hiring_intent_pipeline` to Claude Desktop, Cursor, and LangGraph agents for sub-3-second account research.
- **Zero-Waste Pay-Per-Event Protection:** Powered by `@fleet/ppe-guard`, inactive/dead domains with no DNS MX records, no discovered emails, and zero open jobs are automatically filtered out at `$0` charge.

***

### Input Parameters

| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| `companies` | `object[]` | Yes | `[{"domain":"cloudflare.com","atsTarget":"greenhouse:cloudflare","executives":[{"fullName":"Matthew Prince","role":"CEO"}]}]` | Array of `{ domain, atsTarget?, executives? }` targets. If `atsTarget` is omitted, the Actor automatically probes Greenhouse, Lever, and Ashby using the domain label. |
| `jobKeyword` | `string` | No | `""` | Optional keyword filter for open ATS job titles or departments (e.g., `"Engineer"`, `"Security"`, `"Sales"`). |
| `maxJobsPerCompany` | `integer` | No | `5` | Maximum number of matching open jobs embedded per company dossier (`1` to `100`). |
| `maxItems` | `integer` | No | `10` | Maximum number of company dossiers to return and bill (`1` to `5,000`). |

#### Example Input

```json
{
  "companies": [
    {
      "domain": "cloudflare.com",
      "atsTarget": "greenhouse:cloudflare",
      "executives": [
        { "fullName": "Matthew Prince", "role": "CEO" }
      ]
    }
  ],
  "jobKeyword": "Engineer",
  "maxJobsPerCompany": 5,
  "maxItems": 10
}
```

***

### Output Fields

| Field | Type | Description |
|---|---|---|
| `domain` | `string` | Normalized company domain. |
| `companyName` | `string` | Company name extracted from website or ATS board. |
| `hiringIntentStrength` | `string` | `HIGH_ACTIVE_HIRING` (`>= 10` open roles), `MODERATE_HIRING` (`1–9` open roles), or `NO_OPEN_ROLES_FOUND`. |
| `openJobsCount` | `integer` | Total matching open roles found on the company's ATS career board. |
| `matchingJobs` | `object[]` | Top open roles (`id`, `title`, `department`, `location`, `isRemote`, `url`, `atsProvider`). |
| `mxValid` | `boolean` | `true` if the company domain has active DNS `MX` records. |
| `emailProvider` | `string` | Detected enterprise mail gateway (`Google Workspace`, `Microsoft 365`, etc.). |
| `emailPatternHint` | `string` | Inferred corporate email naming pattern (`{first}.{last}@domain` or `{first}@domain`). |
| `verifiedExecutiveLeads` | `object[]` | Array of `{ fullName, role, recommendedEmail, candidateEmails, deliverabilityStatus, qualityScore, mxProvider }`. |
| `verifiedCompanyEmails` | `object[]` | DNS MX & syntax verification results for all public emails discovered on the company domain. |
| `phones` | `string[]` | Public phone numbers found on the company website. |
| `socials` | `object` | Company social profile links (`linkedin`, `twitter`, `github`). |
| `techSignals` | `string[]` | Detected web technologies (`Next.js`, `Cloudflare`, `HubSpot`, `Stripe`, etc.). |
| `scrapedAt` | `string` | ISO 8601 UTC timestamp. |

#### Example Output

```json
{
  "domain": "cloudflare.com",
  "companyName": "Cloudflare",
  "hiringIntentStrength": "HIGH_ACTIVE_HIRING",
  "openJobsCount": 42,
  "matchingJobs": [
    {
      "id": "greenhouse:cloudflare:7581920",
      "title": "Systems Engineer",
      "department": "Engineering",
      "location": "Austin, TX",
      "isRemote": false,
      "url": "https://boards.greenhouse.io/cloudflare/jobs/7581920",
      "atsProvider": "greenhouse"
    }
  ],
  "mxValid": true,
  "emailProvider": "Google Workspace",
  "emailPatternHint": "{first}.{last}@cloudflare.com",
  "verifiedExecutiveLeads": [
    {
      "fullName": "Matthew Prince",
      "role": "CEO",
      "recommendedEmail": "matthew.prince@cloudflare.com",
      "candidateEmails": [
        "matthew.prince@cloudflare.com",
        "matthew@cloudflare.com",
        "mprince@cloudflare.com",
        "matthewprince@cloudflare.com"
      ],
      "deliverabilityStatus": "DELIVERABLE_MX_VALID",
      "qualityScore": 95,
      "mxProvider": "Google Workspace"
    }
  ],
  "verifiedCompanyEmails": [],
  "phones": [],
  "socials": {
    "linkedin": "https://www.linkedin.com/company/cloudflare"
  },
  "techSignals": ["Cloudflare"],
  "scrapedAt": "2026-11-07T03:00:00.000Z"
}
```

***

### Pricing (Pay-Per-Event)

| Event Name | Price (USD) | When is it charged? |
|---|---:|---|
| `apify-actor-start` | `$0.00005` | Once when the Actor run starts after input validation passes. |
| `result-item` | `$0.00450` | Charged per complete, verified company hiring-intent & executive lead dossier (`$4.50` per 1,000 full company dossiers — 28% cheaper than running all 4 atomic Actors separately). Dead domains with no MX, no emails, and 0 open jobs cost `$0`. |

***

### Standby MCP & AI Agent Integration

Supports **Apify Standby Mode** (`webServerMcpPath: "/mcp"`). AI Agents (Claude Desktop, Cursor, Windsurf, LangGraph) can call `run_b2b_hiring_intent_pipeline` via JSON-RPC 2.0 MCP or `POST /run`.

***

### Part of the B2B Intelligence Suite

| Actor Slug | Primary Use Case | Input → Output |
|---|---|---|
| **`b2b-hiring-intent-lead-pipeline`** *(This Actor)* | All-in-one ATS Hiring Intent + Domain Contact + Executive Lead + MX Verifier | `companies[]` → Complete Outbound Dossier |
| **`b2b-domain-contact-enricher`** | Fast company domain, DNS MX provider & tech stack enrichment | `domain` → Emails, Socials, MX Provider, Tech Stack |
| **`bulk-email-mx-verifier`** | High-speed bulk email syntax, DNS MX & disposable verification (`$0.60/1k`) | `emails[]` → Deliverability Status & Quality Score (`0–100`) |
| **`ats-career-job-listing-api`** | Real-time hiring signals from Greenhouse, Lever & Ashby career boards | `boardSlug` → Normalized Open Roles & Departments |
| **`b2b-company-lead-finder`** | Decision-maker email permutation & MX-verified company lead generation | `domains[] + contacts[]` → Verified Executive Emails & Firmographics |

***

### Data Privacy & Responsible Use

- **Public Corporate Signals Only:** This Actor queries official public ATS job board APIs, public company web pages, and public DNS `MX` records. It does not access private personal databases or bypass authentication.
- **Compliance:** Always adhere to GDPR, CCPA, and CAN-SPAM regulations when conducting B2B outreach.

***

### FAQ & Support

- **Am I charged if a target domain is dead and has 0 open jobs?** No. `@fleet/ppe-guard` verifies that each dossier contains active DNS `MX` records, discovered emails, or open ATS roles before charging `result-item`.
- **Support & Issues:** Open an issue on the Apify Store **Issues** tab for support.

# Actor input Schema

## `companies` (type: `array`):

List of target company objects: { domain, atsTarget, executives }. Example: \[{ "domain": "cloudflare.com", "atsTarget": "greenhouse:cloudflare", "executives": \[{ "fullName": "Matthew Prince", "role": "CEO" }] }]

## `jobKeyword` (type: `string`):

Filter open ATS job postings by role or department keyword (e.g. "Engineer", "Sales", "AI", "Security").

## `maxJobsPerCompany` (type: `integer`):

Maximum number of matching ATS job postings embedded in each company dossier.

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

Maximum number of enriched & MX-verified company dossiers to return and bill.

## Actor input object example

```json
{
  "companies": [
    {
      "domain": "cloudflare.com",
      "atsTarget": "greenhouse:cloudflare",
      "executives": [
        {
          "fullName": "Matthew Prince",
          "role": "CEO"
        }
      ]
    }
  ],
  "maxJobsPerCompany": 5,
  "maxItems": 10
}
```

# Actor output Schema

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

Structured items stored in the default dataset.

# 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 = {
    "companies": [
        {
            "domain": "cloudflare.com",
            "atsTarget": "greenhouse:cloudflare",
            "executives": [
                {
                    "fullName": "Matthew Prince",
                    "role": "CEO"
                }
            ]
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("apexsignal/b2b-hiring-intent-lead-pipeline").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 = { "companies": [{
            "domain": "cloudflare.com",
            "atsTarget": "greenhouse:cloudflare",
            "executives": [{
                    "fullName": "Matthew Prince",
                    "role": "CEO",
                }],
        }] }

# Run the Actor and wait for it to finish
run = client.actor("apexsignal/b2b-hiring-intent-lead-pipeline").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 '{
  "companies": [
    {
      "domain": "cloudflare.com",
      "atsTarget": "greenhouse:cloudflare",
      "executives": [
        {
          "fullName": "Matthew Prince",
          "role": "CEO"
        }
      ]
    }
  ]
}' |
apify call apexsignal/b2b-hiring-intent-lead-pipeline --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,apexsignal/b2b-hiring-intent-lead-pipeline"
        }
    }
}
```

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/6iln2HJk10VsEwOJ9/builds/dSH41q6bz85a5tPLX/openapi.json