Fast Contact, Lead & Tech Stack Extractor avatar

Fast Contact, Lead & Tech Stack Extractor

Pricing

from $1.28 / 1,000 page scrapeds

Go to Apify Store
Fast Contact, Lead & Tech Stack Extractor

Fast Contact, Lead & Tech Stack Extractor

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.

Pricing

from $1.28 / 1,000 page scrapeds

Rating

0.0

(0)

Developer

Mohit Tripathi

Mohit Tripathi

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

7 hours ago

Last modified

Features

Limited permissions

Share

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

FieldTypeDefaultDescription
startUrlsarray["https://www.apify.com", "https://www.python.org"]Domains or URLs. Bare domains get https://.
maxPagesPerDomaininteger8Hard page cap per domain. Eight covers contact, team and about on most sites.
maxConcurrencyinteger12Domains crawled in parallel.
requestTimeoutSecsinteger8Timeout for one HTTP request.
domainTimeoutSecsinteger20Wall-clock cap per domain; a slow site cannot hang the run.
maxDecisionMakersinteger10Cap on named people per domain.
verifyEmailDomainsbooleantrueDNS MX lookup for each email domain.
impersonateFallbackbooleantrueRetry 401/403/429 with a Safari TLS fingerprint. Still HTTP.

Example input:

{
"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.

{
"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)

EventPriceCharged when
apify-actor-start$0.05 / 1,000 runsSynthetic start event, charged once by Apify.
page-scraped$1.50 / 1,000 pagesPer valid 2xx HTML page that contributed to a pushed record.
lead-verified$35 / 1,000 leadsPer 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

{
"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:

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

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

Run the 20-domain gate:

$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: