Website Email & Contact Finder — Phone, WhatsApp & Socials

Bulk website email finder and contact scraper for public phones, WhatsApp links, contact pages, forms, and social profiles — optimized for Brazilian B2B lead enrichment.

Turn a list of company websites into structured contact profiles for prospecting, CRM enrichment, local SEO audits, and agency workflows.

Verified in production

• 10 Brazilian websites processed in one real remote batch.
• 10 useful Dataset rows and 0 item errors.
• Approximately $0.000130 platform cost per useful website in HTTP mode without proxy.
• Emails, phones, WhatsApp links, forms, contact pages, and social profiles supported.
• Real regression fixed: truncated email suffixes are removed while the complete address is preserved.

Cost evidence applies to HTTP mode without proxy. Browser rendering and proxies can materially increase cost.

At a glance

Capability	Output
Emails	emails[], hasEmail
Phones	phones[], normalized digits, source
WhatsApp	whatsAppLinks[], number, source, pre-filled message
Contact pages	/contato, support/help/contact URLs
Forms	form action, method, field names
Social profiles	Instagram, LinkedIn, Facebook, YouTube, TikTok, X
Lead quality	contactScore 0-100 + contactCompleteness

Best for

• Brazilian B2B sales agencies
• SDR and outbound prospecting teams
• Local marketing and SEO agencies
• CRM enrichment builders
• SaaS founders selling to SMBs
• Automation builders using Make, n8n, Zapier

What this Actor does

1. Accepts public website URLs.
2. Fetches pages with cheap HTTP-first defaults.
3. Extracts public contact channels.
4. Filters common false positives like Sentry/error-reporting emails and noisy numeric IDs.
5. Scores contact completeness from NONE to HIGH.
6. Writes clean JSON rows to an Apify Dataset.

Example input

{
  "startUrls": [
    { "url": "https://www.rdstation.com" },
    { "url": "https://portaldascorridas.com.br" }
  ],
  "maxItems": 10,
  "useBrowser": false
}

Example output

{
  "url": "https://portaldascorridas.com.br",
  "emails": ["contato@portaldascorridas.com.br"],
  "phones": [],
  "whatsAppLinks": [
    {
      "number": "5535987127477",
      "source": "wa.me",
      "url": "https://wa.me/5535987127477",
      "confidence": "HIGH"
    }
  ],
  "socialProfiles": [
    { "platform": "instagram", "url": "https://www.instagram.com/portaldascorridas" }
  ],
  "hasEmail": true,
  "hasPhone": false,
  "hasWhatsApp": true,
  "contactScore": 60,
  "contactCompleteness": "MEDIUM"
}

Buyer workflows

Website list → Website Contact Finder → Dataset/CSV → CRM
CNPJ/domain list → Website Contact Finder → n8n or Make → sales pipeline
Agency audit → contact completeness score → outreach prioritization

A successful row means the website was processed without a request error. usefulProfiles in the run summary is narrower: it counts successful rows with at least one actionable contact signal (contactScore > 0). Empty contact fields are not automatically request failures; inspect error, successful, and the HTTP result.

The OUTPUT run summary includes:

{
  "processed": 10,
  "successful": 9,
  "usefulProfiles": 7,
  "emailsFound": 8,
  "phonesFound": 6,
  "whatsAppLinksFound": 3,
  "contactPagesFound": 5,
  "formsFound": 4,
  "socialProfilesFound": 12,
  "failed": 1
}

Channel counters report total occurrences across successful profiles, not only the number of websites containing each channel.

Optional contact-page discovery

Enable followContactPages to fetch same-origin contact/support links discovered on each primary page. maxSecondaryPages is a strict per-domain budget from 0 to 5 (default 2). Contacts are merged into the primary Dataset row and deduplicated; secondary-page failures are reported without failing an otherwise valid primary profile.

The feature is disabled by default because every secondary page adds crawling cost. Inspect secondaryPagesScanned, secondaryPageErrors, and secondaryPageUrls to measure the gain.

Use cases

• Enrich CRM leads from website URLs.
• Audit whether local business websites expose contact channels.
• Build prospecting lists with emails, WhatsApp, forms, and social profiles.
• Score company websites by contact completeness.
• Feed clean contact data into Sheets, Make, n8n, Zapier, CRMs, or BI tools.

Safety and limitations

• Uses public website data only.
• Does not log in, bypass protections, send WhatsApp messages, or scrape private conversations.
• Phone extraction is conservative to reduce false positives.
• JavaScript-heavy contact widgets may require useBrowser: true, which costs more.

API usage

Run through Apify API, CLI, Tasks, Schedules, webhooks, Make, n8n, Zapier, or your own backend.

Support and feedback

Run 5–20 websites first. If a public contact channel is missing or incorrectly extracted, send the run ID and target URL through the Apify support tab so the parser can be improved. Do not include private credentials, cookies, or personal data in support requests.