Website Email, Phone and Social Media Extractor avatar

Website Email, Phone and Social Media Extractor

Pricing

from $2.10 / 1,000 results

Go to Apify Store
Website Email, Phone and Social Media Extractor

Website Email, Phone and Social Media Extractor

Extract publicly visible business emails, telephone numbers and social links from websites supplied by the user. Export normalized evidence with source URLs for authorized B2B research, contact verification and outreach preparation. No private databases or personal-account access.

Pricing

from $2.10 / 1,000 results

Rating

0.0

(0)

Developer

Rafael Barreto Haddad

Rafael Barreto Haddad

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

7 days ago

Last modified

Features

Limited permissions

Share

Extract publicly visible business emails, telephone numbers and social links from websites supplied by the user. Export normalized evidence with source URLs for authorized B2B research, contact verification and outreach preparation. No private databases or personal-account access.

Why use this Actor

Teams waste time opening company websites one by one to find public contact and social-profile data for enrichment and research.

Key features

  • Buyer-native inputs aligned to website email extractor.
  • Predictable structured output in the default Apify Dataset.
  • Pay Per Event pricing tied to measurable result rows or reports.
  • Optional MCP connector delivery for downstream automation and AI agents.

Quick start

Start with this working example and replace the target values with your own:

{
"urls": [
"https://www.python.org"
],
"max_pages_per_site": 2
}

The Actor writes structured results to the default Apify Dataset and can be used from the Store, API, schedules, Tasks, automations and MCP-compatible AI workflows.

Input

  • urls — Business website URLs: Public HTTP/HTTPS websites to inspect.
  • max_sites — Maximum sites: Process at most this many URLs from the list.
  • max_pages_per_site — Pages per site: Homepage plus likely contact/about pages on the same domain.
  • timeout_secs — Request timeout: Maximum seconds to wait for each public website request.
  • previous_results — Previous contact snapshots: Optional map keyed by input URL. Enables added/removed contact detection, confidence and freshness intelligence.

All integration and advanced analysis fields are optional. The default example is intentionally runnable without configuring MCP or a previous-run baseline.

Output

The Dataset exposes predictable machine-readable output. Representative fields include results.

Pricing

This Actor uses Pay Per Event. The current factory base price is $0.003000 per result event. The Apify Store remains the source of truth for the price and plan/tier details shown to the buyer.

Use cases

  • Run the buyer-ready workflows exposed as Apify Tasks without preparing a custom integration first.
  • Use the Actor from API or schedules for recurring collection, comparison or monitoring.
  • Feed the structured Dataset output into spreadsheets, databases, automations or AI agents.
  • Compare repeat runs when the product supports snapshots or previous-run inputs.

Automation and AI

Use the same Actor through Apify API, schedules, public Tasks and the Apify MCP server. Outputs are structured for downstream workflows and AI agents rather than requiring manual copy/paste.

Limitations

  • Public websites and upstream APIs can change markup, access rules, rate limits or field availability without notice.
  • Fields that are not publicly available are returned as unavailable or omitted rather than fabricated.
  • Analytical outputs depend on the quality and coverage of the supplied or collected source data.
  • Treat marketplace, reputation, workforce, safety or commercial signals as decision support and validate material decisions against the underlying source evidence.

Detailed documentation

Business use and first result

For: B2B business-research teams.

Why run it: Extract openly published business contact channels from user-supplied websites.

What to inspect: Visible business email, phone and public social profile URLs.

First run: use the documented sample input below, inspect the Dataset rows and source links, then reuse the saved output for a later comparison only where snapshots are supported. Confirm the input scope and current Pay Per Event pricing before scheduling ongoing use.

Scope and limitations: Do not use for personal contact harvesting; website visibility and data accuracy vary.

Give it business websites. Get public emails, phone numbers and social profile links with evidence fields and structured output for lead workflows.

Turn public company websites into clean contact-enrichment records without manually opening home, contact, and about pages. The Actor finds publicly displayed business emails, tel: phone links, and major social profiles, then returns one structured dataset item per website with explicit issue flags.

Why use this Actor

Use it when a company website is your starting point and you need a predictable enrichment step for lead research, CRM preparation, supplier research, or market mapping. It keeps the scope deliberately focused on public website data and reports when useful fields are missing instead of silently returning an empty result.

Key features

  • Extracts public emails from visible HTML and mailto: links.
  • Extracts click-to-call phone values from tel: links.
  • Detects LinkedIn, Facebook, Instagram, X/Twitter, YouTube, TikTok, GitHub, and Pinterest profiles.
  • Can follow likely contact/about/support pages on the same website.
  • Returns scanned URLs, page count, HTTP status, and issue flags.
  • Blocks localhost, private IP ranges, and unsafe redirect targets.
  • Produces one structured result per input website for easy automation.

Input

Provide a list of public company website URLs. Optional controls let you limit the number of sites, pages scanned per site, and request timeout.

{
"urls": ["https://www.python.org"],
"max_pages_per_site": 2
}

Output

Each website produces a record containing the normalized/final URL, success status, page title, discovered emails, phone links, grouped social profiles, scanned URLs, number of pages scanned, and explicit issues such as no_public_email_found.

Example

{
"url": "https://www.python.org",
"ok": true,
"emails": [],
"phones": [],
"social_links": {"github": ["https://github.com/python"]},
"pages_scanned": 2,
"issues": ["no_public_email_found", "no_tel_link_found"]
}

Use cases

  • B2B lead enrichment from known company domains
  • CRM and sales-research preparation
  • Supplier and partner research
  • Social-profile discovery for business intelligence
  • Website contact-data QA
  • Structured enrichment pipelines in Apify, Make, n8n, or custom systems

Pricing

Pay per result. The current price is $0.003 per processed website, equivalent to $3 per 1,000 results before any platform-specific charges shown by Apify.

Limitations

  • Only public website content is processed.
  • Phone extraction focuses on explicit tel: links; arbitrary phone-like text is intentionally not guessed.
  • JavaScript-rendered contact information may not be visible to this lightweight fetcher.
  • Anti-bot systems, authentication, CAPTCHAs, or blocked pages can reduce available data.
  • The Actor does not verify ownership, deliverability, or accuracy of discovered contact details.

Responsible use

Use collected data in accordance with applicable law, website terms, and privacy requirements. The Actor does not bypass authentication or access private data.

Buyer-first quick start (November 2026)

This workflow is designed for one practical buyer question, with a small, reproducible first run and auditable Dataset output.

Example input

{
"urls": [
"https://www.python.org"
],
"max_pages_per_site": 2
}

Source and limitations

The first run uses a public-source request or user-provided authorized URLs/documents. Upstream websites can block or throttle requests; not every result is assured to be available. Verify source URLs and timestamps before acting. If the source is inaccessible, a failed or limited result is not evidence of zero market demand.

Repeatable workflow

Use the default test to understand the output, verify record identifiers and field coverage, then schedule a Task with a bounded input. Compare real earlier snapshots only when available. Check the current Apify Store Pay Per Event rate and set Apify run charge limits for recurring use. Source evidence does not establish paying customers, successful outbound sales, or revenue.