# Fast Contact, Lead & Tech Stack Extractor (`structlabs/fast-contact-lead-extractor`) Actor

B2B contact extractor and lead enrichment API: company emails, phones, social profiles, decision-makers, website tech stack and ad pixels in one fast HTTP run. No browser, no residential proxy.

- **URL**: https://apify.com/structlabs/fast-contact-lead-extractor.md
- **Developed by:** [Mohit Tripathi](https://apify.com/structlabs) (community)
- **Categories:** Lead generation, Business
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.28 / 1,000 page scrapeds

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?

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

## Fast Contact, Lead & Tech Stack Extractor

Extract **company emails, phones, social profiles, decision-makers, tech stack and ad pixels** from public websites in seconds — no browser, no residential proxy, no extra requests.

Built for lead-gen pipelines, CRM enrichment, and AI agents that need clean company contact data at scale. Every record is extracted from public HTML, obfuscated emails are decoded, and email domains are checked against live DNS MX records before you pay for a lead.

### What it does

- Crawls a company site with a **hard cap per domain**, prioritizing `/contact`, `/about`, `/team`, `/impressum`, `/legal`, and similar paths.
- Decodes **`[at]` / `[dot]` obfuscation**, **Cloudflare `data-cfemail`** hex strings, `mailto:` links, and **JSON-LD** `Organization` / `ContactPoint` data.
- Extracts **LinkedIn, X, Instagram, Facebook, YouTube, and TikTok** profile URLs.
- Finds **named decision-makers** (CEO, founder, CTO, VP, director, partner, head of…) on team/about pages.
- Detects **Shopify, WooCommerce, WordPress, Webflow, HubSpot, Klaviyo, Intercom, Stripe, Cloudflare, Google Analytics, GTM, Meta/TikTok/LinkedIn pixels and Google Ads IDs** from the HTML and headers already fetched (zero extra HTTP cost).
- Runs a **zero-cost async DNS MX check** per email domain and returns `email_domain_valid` plus per-domain status.
- Uses **plain HTTP with TLS impersonation** (`curl_cffi`). A second TLS fingerprint is tried on 401/403/429. No JS rendering, no proxy bandwidth bill.

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `startUrls` | array | `["https://www.apify.com", "https://www.python.org"]` | Domains or URLs. Bare domains get `https://`. |
| `maxPagesPerDomain` | integer | `8` | Hard page cap per domain. Eight covers contact, team and about on most sites. |
| `maxConcurrency` | integer | `12` | Domains crawled in parallel. |
| `requestTimeoutSecs` | integer | `8` | Timeout for one HTTP request. |
| `domainTimeoutSecs` | integer | `20` | Wall-clock cap per domain; a slow site cannot hang the run. |
| `maxDecisionMakers` | integer | `10` | Cap on named people per domain. |
| `verifyEmailDomains` | boolean | `true` | DNS MX lookup for each email domain. |
| `impersonateFallback` | boolean | `true` | Retry 401/403/429 with a Safari TLS fingerprint. Still HTTP. |

Example input:

```json
{
  "startUrls": ["https://stripe.com", "https://grafana.com"],
  "maxPagesPerDomain": 8,
  "maxConcurrency": 12,
  "verifyEmailDomains": true
}
```

### Output

One record per domain that produced at least one email, phone, or named person. Empty domains are **not pushed and not charged**.

```json
{
  "domain": "apify.com",
  "website": "https://apify.com",
  "start_url": "https://www.apify.com",
  "emails": ["hello@apify.com", "support@apify.com"],
  "phones": [],
  "social_profiles": {
    "linkedin": ["https://www.linkedin.com/company/apify"],
    "x": ["https://twitter.com/apify"],
    "youtube": ["https://www.youtube.com/@apify"]
  },
  "technologies": ["AWS", "Google Analytics", "Google Tag Manager", "HubSpot", "Intercom", "Next.js", "Nginx"],
  "ad_pixels": {"gtm_id": ["GTM-MNGXGGB"]},
  "decision_makers": [
    {
      "name": "Jan Curn",
      "title": "Founder & CEO",
      "email": null,
      "phone": null,
      "source_url": "https://apify.com/about"
    }
  ],
  "verified_decision_makers": 0,
  "email_domain_valid": true,
  "email_domains": [
    {"domain": "apify.com", "mx_found": true, "status": "mx_found"}
  ],
  "pages_scanned": 6,
  "pages_succeeded": 6,
  "error": null,
  "elapsed_ms": 1840,
  "scraped_at": "2026-11-20T05:20:00+00:00"
}
```

Field notes:

- `verified_decision_makers` counts people with **name + title + email**. Each one is billed as a `lead-verified` event.
- `email_domain_valid` is `true` when at least one email domain has an MX record, `false` when none do, and `null` when there is no email or verification is off.
- `pages_succeeded` counts valid 2xx HTML responses only. 404s, blocks, and timeouts are never billed.

### Pricing (pay per event)

| Event | Price | Charged when |
|---|---:|---|
| `apify-actor-start` | $0.05 / 1,000 runs | Synthetic start event, charged once by Apify. |
| `page-scraped` | **$1.50 / 1,000 pages** | Per valid 2xx HTML page that contributed to a pushed record. |
| `lead-verified` | **$35 / 1,000 leads** | Per person with name + title + email in the same domain. |

**Cost example:** 1,000 domains × 8 pages = 8,000 pages → $12.00. If 250 of those domains yield one verified decision-maker each → $8.75. Total **$20.75 per 1,000 domains**, about 2.1¢ per domain.

No charge for empty domains, 404s, blocks, timeouts, or records without contact data.

### MCP / AI-agent use

```json
{
  "mcpServers": {
    "apify": {
      "command": "npx",
      "args": [
        "-y",
        "@apify/actors-mcp-server",
        "--actors",
        "structlabs/fast-contact-lead-extractor"
      ],
      "env": {
        "APIFY_TOKEN": "<your token>"
      }
    }
  }
}
```

Or call the Actor directly:

```bash
curl -X POST "https://api.apify.com/v2/acts/structlabs~fast-contact-lead-extractor/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"startUrls":["https://stripe.com"]}'
```

### Limits and honest notes

- **HTTP-only.** Sites that render contact data exclusively with JavaScript, or sit behind a CAPTCHA/login, may return no data. That is deliberate: it keeps runs at 128–256 MB and avoids residential proxy costs.
- **MX is not SMTP verification.** `email_domain_valid` proves the domain can receive mail; it does not prove the mailbox exists.
- **Decision-makers are heuristic.** Names and titles come from team/about page structure. Always verify before a high-stakes outreach.
- **Respect robots.txt and terms of service.** You are responsible for how you use the extracted data and for applicable privacy law (GDPR/CCPA).

### Local development

```bash
apify run -i '{"startUrls":["https://apify.com"]}'
```

Run the 20-domain gate:

```bash
ACTOR_TEST_PAY_PER_EVENT=true apify run --input-file test_input_20.json
```

### Changelog

- **0.4.2** — Dataset schema is now a valid object schema; every optional field accepts `null`, so a record with no `error` or MX result cannot trigger a schema-validation failure.
- **0.4** — Zero-cost tech-stack and ad-pixel detection from the same HTML/headers; 19/20 gate, 25s, 118 pages; title updated to Contacts + Leads + Tech Stack.
- **0.3** — Cross-page lead matching: team-page people are linked to an existing name-matched email on the same MX-valid domain (`email_source: cross_page`), never guessed.
- **0.2** — Interleaved contact/team/about frontier and 8-page default: 19/20 domains on the real-world gate, prefill 4.7s.
- **0.1** — First release: HTTP crawler, email/phone/social/decision-maker extraction, Cloudflare decoding, MX validation, per-page and per-lead PPE billing.

### Pricing source

Canonical store-discount ladder (FREE/BRONZE/SILVER/GOLD/PLATINUM/DIAMOND) lives in `pricing.json`. Apify `actor.json` cannot carry pricing and `apify push` does not change account pricing; after any manual API change, the newest `pricingInfos` record must match `pricing.json`.

### n8n Workflow & MCP Quickstart

Run this Actor from an AI agent over MCP, or import the ready-made n8n workflow:

- n8n workflow, MCP config and quickstarts: https://github.com/structlabs-hq/fast-contact-lead-extractor-n8n-mcp
- MCP endpoint: https://mcp.apify.com/?actors=structlabs/fast-contact-lead-extractor

# Actor input Schema

## `startUrls` (type: `array`):

Company domains or URLs to scan. A bare domain is treated as https://<domain>. Each domain is capped by Max pages per domain.

## `maxPagesPerDomain` (type: `integer`):

Hard cap on HTML pages fetched per domain. Eight covers contact, team and about on most sites; lower is faster and cheaper.

## `maxConcurrency` (type: `integer`):

How many domains are crawled in parallel. Keep at 12 or below for datacenter IP friendliness.

## `requestTimeoutSecs` (type: `integer`):

Timeout for a single HTTP request. No browser is used.

## `domainTimeoutSecs` (type: `integer`):

Hard wall-clock cap per domain so a slow site cannot hang the run.

## `maxDecisionMakers` (type: `integer`):

Cap on named people with a C-level, founder, director, partner or head-of title found on team/about pages.

## `verifyEmailDomains` (type: `boolean`):

Run a zero-cost async DNS MX lookup for each email domain and return email_domain_valid plus per-domain status.

## `impersonateFallback` (type: `boolean`):

On 401/403/429, retry once with a Safari TLS fingerprint. This is still plain HTTP, not browser rendering.

## Actor input object example

```json
{
  "startUrls": [
    "https://www.apify.com",
    "https://www.python.org"
  ],
  "maxPagesPerDomain": 8,
  "maxConcurrency": 12,
  "requestTimeoutSecs": 8,
  "domainTimeoutSecs": 20,
  "maxDecisionMakers": 10,
  "verifyEmailDomains": true,
  "impersonateFallback": true
}
```

# Actor output Schema

## `results` (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 = {
    "startUrls": [
        "https://www.apify.com",
        "https://www.python.org"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("structlabs/fast-contact-lead-extractor").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 = { "startUrls": [
        "https://www.apify.com",
        "https://www.python.org",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("structlabs/fast-contact-lead-extractor").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 '{
  "startUrls": [
    "https://www.apify.com",
    "https://www.python.org"
  ]
}' |
apify call structlabs/fast-contact-lead-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,structlabs/fast-contact-lead-extractor"
        }
    }
}
```

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/ycK4zBX3doVEGAq5n/builds/Y8VbPhi3vJe56cWMn/openapi.json
