Bulk Website Contact Extractor & Email Finder avatar

Bulk Website Contact Extractor & Email Finder

Pricing

from $0.90 / 1,000 lead discovereds

Go to Apify Store
Bulk Website Contact Extractor & Email Finder

Bulk Website Contact Extractor & Email Finder

Extract public business website contacts for CRM enrichment. Review HubSpot company CSV updates before import. Export emails, phones, social links and CRM import files. Optional website email MX checks report domain mail routing. Pay per useful website and qualifying optional events.

Pricing

from $0.90 / 1,000 lead discovereds

Rating

0.0

(0)

Developer

harvestlab

harvestlab

Maintained by Community

Actor stats

2

Bookmarked

270

Total users

10

Monthly active users

a day ago

Last modified

Features

Limited permissions

Share

Turn company websites into public emails, phone numbers, social profiles and source-linked contact records. Use the downloadable company and selected-contact files to prepare a CRM import. Basic discovery is priced per useful website; optional enrichment and checks add separate events.

Who it's for

  • Sales and RevOps teams enriching a list of company domains before reviewing an import.
  • Recruiters and market researchers collecting published business contact details.
  • CRM administrators refreshing source URLs and deduplicating company/contact records.

What you get

  • One website record with published contacts, social links and source context.
  • Optional CRM-companies.csv, CRM-contacts.csv and CRM-upserts.json files when exportCrm is enabled; the export does not write to a CRM.
  • Optional email checks, phone formatting and technology signals, each with its own eligibility and cost.

Cost example: 100 useful websites with tech detection, email checks, phone formatting and AI off cost 100 × $0.0012 = $0.12 on Starter/Bronze in basic-discovery events. At the no-discount base the same events total $0.15. The event prices include Apify run usage. This schedule has no separate Actor startup or dataset-item event. Optional Actor events and external services can add cost. Discounts follow your Apify subscription plan, not batch size. Check current pricing.

The Console starter reads one public contact page and saves the CRM import files in the run's key-value store for review. It uses basic discovery pricing, with phone formatting and enrichment switched off. If validatePhones is omitted from an API input, phone formatting remains enabled for compatibility and costs $0.02 per qualifying number at the no-discount base price. Set it to false for raw-phone discovery only. Published contact details are not permission to send unsolicited messages.

Plan discounts: Starter (Bronze), Scale (Silver), and Business (Gold) receive 20%, 30%, and 40% off ordinary events. Basic discovery is $1.50 / $1.20 / $1.05 / $0.90 per 1,000 useful sites at base / Starter / Scale / Business prices. Other single prices and examples below use the no-discount base unless labelled otherwise; see the full event table. Discounts follow your Apify plan, not the number of sites in a run.

Run the ready-made B2B lead task to create company and contact CSV files from one example website. Its starter disables paid phone formatting, verification, tech detection, and AI. Open the configurable Actor for larger batches or optional enrichment.

Already have a list in Apify Storage? Read website URLs from a dataset.

Already have a run ID? Review its CRM files through Apify MCP.

Run the one-site MX example to save CRM files for review. The checked-only export includes a selected contact when the email domain qualifies. This example costs up to $0.016 in Starter/Bronze Actor events, with the full amount applying when one useful site and one qualifying MX check are billed. For a recurring CRM list, prepare a 25-site paid MX pilot from one batch and review two refreshes against the same cohort.

First-run questionAnswer
What should I enter?Start with the prefilled public contact-page URL, then replace it with your own. Clear that URL before entering a domain list, then set Website Limit per Run to the number of distinct websites you intend to process.
What comes back?One website record with public contacts and source context, plus deduplicated company and selected-contact CSV files and JSON merge instructions. Use exportCrm: true to include those files in a custom API input.
What does it cost?At no-discount base prices, this starter uses basic discovery at $0.0015 per useful site with enrichment and phone formatting off. Enabling phone formatting adds $0.02 per qualifying phone. Tech/MX/SMTP enrichment uses a $0.01 website event, with checks charged separately. Eligible Apify plans receive the discounts above.
What if a site is unreachable?The Actor returns a clear no-charge diagnostic instead of billing it as a contact result.

Best first run

Start with a direct page that publishes contact details. A homepage can return useful social links without any email address; an empty email list does not mean that the rest of the site has no contacts.

{
"urls": ["https://www.python.org/about/help/"],
"maxWebsites": 1,
"maxPagesPerSite": 1,
"includeSubpages": false,
"detectTechStack": false,
"validatePhones": false,
"verifyEmails": false,
"deepEmailVerification": false,
"enableAiAnalysis": false,
"exportCrm": true
}

The starter saves CRM-EXPORT, CRM-companies.csv, CRM-contacts.csv and CRM-upserts.json for review. Start with CRM-EXPORT to check whether the files are complete. Published emails remain unverified unless you enable a check. The starter limits the run to one website. For a list, set Website Limit per Run (maxWebsites) to the number of distinct websites you want processed, up to 200. For your own homepages, increase maxPagesPerSite and enable includeSubpages to look for contact and about pages.

What you get back

  • One row per processed site with normalized url, discovered emails, phones_validated, social_profiles, address, contact_page_url, and tech_stack.
  • When detectTechStack is enabled and Shopify is confidently detected, the row can add is_shopify_store, detection confidence and signals, store name, canonical URL, currency, and business country. These fields are omitted for non-Shopify sites and inconclusive detections.
  • result_type shows whether the row contains contact_data, a no-charge partial_result, a no-charge fetch_failed, site_timeout, or site_error diagnostic. fetch_diagnostics lists attempted/reached URLs, timeout details, or sanitized per-site error details for debugging blocked and slow sites.
  • Optional emails_verified and ai_contact_analysis fields appear only when the paid verification or AI toggles are enabled. maxEmailsToVerify limits email verification attempts across the run. A failed or non-qualifying check can use an attempt.
  • After checking the one-page starter, increase page coverage for your own domains. Turn on technology detection or email checks only when those extra fields are useful to your workflow.

Real sample output

This is a field selection from the accepted November 13, 2026 starter. The run returned one website record with two emails, so the example shows one record. Email checks were off; these are published addresses, not verified mailboxes. Your results depend on the target page.

[
{
"url": "https://www.python.org/about/help/",
"domain": "python.org",
"result_type": "contact_data",
"billable_contact_found": true,
"emails": [
"psf@python.org",
"python-announce@python.org"
],
"contact_page_url": "https://www.python.org/about/help/",
"scraped_at": "2026-11-13T13:37:30Z"
}
]

Website Contact Extractor

Give the actor a list of domains or URLs and it crawls each public website for contact details that are visible on the homepage and high-signal subpages such as contact, about, imprint, legal, and team pages. Results are normalized into one row per website, with raw contacts separated from email-check results, formatted phones, social profiles, address data, contact-page URLs, and technology signals.

Contact Details Extractor

Extract public contact details from company websites in a format your CRM can use immediately: email addresses, phone numbers, social links, physical addresses, contact-page URLs, and technology signals. Use it for contact discovery, enrichment, deduplication, and fresh lead records before outreach.

Email Finder from Website

Use it as an email finder from website and domain lists when you need fresh outreach data before a campaign. The actor finds public role, team, and company addresses, adds optional deliverability checks, keeps contact-page context, and returns each website as a structured row that can move directly into a CRM, spreadsheet, or enrichment pipeline.

Shopify Store Contact Enrichment

Enable detectTechStack for Shopify store URLs already in your domain list. When strong public evidence identifies a Shopify storefront, the contact row can add the positive detection flag, confidence and evidence signals, public store name, canonical URL, currency, and business country when exposed in top-level Store or Organization metadata. Inconclusive and non-Shopify sites receive no Shopify fields. The Actor reuses the page fetched for contact extraction; it does not discover stores, request a product catalog, or access private Shopify APIs.

B2B Lead Extractor

Extract published emails, phone numbers, social profiles and addresses from accessible public websites. Add optional email checks, formatted phones and tech-stack signals, then export company and selected-contact files for CRM import. Built for SDRs, RevOps teams, recruiters, ABM marketers and M&A researchers working from domain or URL lists; coverage depends on what each website exposes.

For each domain you provide, the actor checks the homepage and high-signal subpages such as /contact, /about, and /imprint; extracts public emails and business contact data; formats phone numbers when enabled; identifies social profiles; parses physical addresses; and can add tech-stack signals, email checks and AI role classification. The dataset is structured JSON. Enable exportCrm for company and selected-contact CSV files plus JSON merge instructions; import them using your destination's field mapping and authorized credentials. The export does not write to a CRM.

Features

  • Public contact discovery: URLs or domains, contact-page crawling, social profiles and available addresses.
  • Optional enrichment: technology and Shopify context, email-domain checks, mailbox signals and phone formatting. Check results retain their limitations; none guarantees delivery or reachability.
  • CRM preparation: deduplicated company and selected-contact exports, source timestamps and merge instructions that preserve existing values when incoming fields are empty.
  • Controlled batches: website and page caps, separate per-site diagnostics, and opt-in AI role classification.

Choose a First-Run Cost

At no-discount base prices, basic discovery costs $0.0015 per useful website with enrichment switched off. The enriched base is $0.01 per useful website when tech detection, email checks or deep verification is enabled. Phone formatting, qualifying email checks, SMTP checks and AI have separate additive events; the enriched base does not include all of them. Review the Pricing section and maximum Actor charge before enabling optional features.

The B2B starter below disables those optional charges and produces downloadable CRM files. Published emails remain unverified unless a check was actually performed; no mode guarantees mailbox availability or delivery of a message.

Use Cases

SDR / AE Outbound Prospecting

Enrich company lists with published emails and their actual check status. Upload target company domains to extract public contacts and optional enrichment, then review the CRM import files and map them to your destination. Configure any downstream integration separately with authorized credentials; extraction does not enroll contacts in outreach. Optional AI role classification helps distinguish shared inboxes such as info@, support@, and noreply@.

Account-Based Marketing (ABM) Lists - match-rate by domain, not name + company guess

Build enriched ABM target lists from a domain seed (e.g. "all SaaS companies running Segment + Marketo on Shopify"). Tech stack detection (175+ signals) lets you filter by CMS, analytics, CRM, chat widget, payment processor, CDN, search platform. Combine with enableAiAnalysis for primary-contact selection per account.

Lead-Gen Agencies & RevOps - pay-per-event beats per-seat

Run hundreds of client enrichment jobs without buying seats per analyst. Pay only for sites that returned data: failed fetches and DNS errors are free. Keep source URLs and contact-page context for QA and client delivery.

Recruiter Sourcing & Talent Intel - find decision-makers via tech-stack match

Identify hiring managers at companies running specific stacks, such as SaaS teams using modern frontend frameworks or developer tools. Tech-stack detection reveals what languages and platforms a company appears to use today, which can be more current than profile skill tags. Pair with social profile capture to surface candidate-targeting signals.

M&A Due Diligence & Investor Research - rapid target screening

Run a watchlist of acquisition targets through the Actor every quarter. Where published, output includes company description, address, contact emails, phones, social profiles and optional tech signals. Split lists larger than 200 websites into separate capped runs; runtime and completeness depend on target responsiveness and pages crawled. Use the evidence to screen technology adoption and public company context, not as a guarantee of complete coverage.

Download CRM Import Files

Set exportCrm: true to get files directly in the run's CRM Import Files output. No script download or CRM credentials are needed. The existing B2B lead task enables this export with paid enrichment and phone formatting switched off. This sample reads a published contact page and exports a selected unverified email when one is available; a homepage-only crawl may find no contact email.

{
"urls": ["https://www.python.org/about/help/"],
"maxWebsites": 1,
"maxPagesPerSite": 1,
"includeSubpages": false,
"detectTechStack": false,
"validatePhones": false,
"verifyEmails": false,
"deepEmailVerification": false,
"enableAiAnalysis": false,
"exportCrm": true,
"crmRequireMx": false,
"proxyConfiguration": {"useApifyProxy": true}
}

The files contain:

FileContents and import key
CRM-companies.csvOne company per normalized company_key domain; website, name, LinkedIn, available formatted phone and technology signals.
CRM-contacts.csvAt most one selected eligible published email per website observation, deduplicated by contact_key email; source URL, check status and observation time. A shared email across companies has a blank company association for review.
CRM-upserts.jsonThe same records with merge instructions that preserve existing values when incoming fields are empty.
CRM-EXPORTCompletion status, counts and file names. Import only after status is complete. Compare the exported coverage with your planned website list.

The run log reports when the website limit excludes sites. CRM-EXPORT.requested_sites counts the sites selected within the limit. Import companies first, then contacts using the keys above. Review blank company associations before linking contacts. The complete original email lists remain in the dataset. The export adds no Actor event. Reads or writes to output storage after the run may incur separate Apify usage charges. Basic extraction remains $0.0015 per useful website when enrichment and phone formatting are off.

Unchecked emails are labelled published_unverified. Existing failed, LOW/UNKNOWN, disposable and typo checks are excluded. For checked-only contacts, enable verifyEmails deliberately and set crmRequireMx: true. The filter itself does not turn on verification or its charges. MX checks concern the email domain, not mailbox existence; formatted phones are not reachability checks. Zero eligible emails produces an empty contacts file, not an invented person.

For repeat refreshes, save your own task with the same company list and choose a schedule appropriate to your business need. Import completed runs by key, preserve existing fields on empty values, and never delete a contact because it is absent from a later crawl. These files do not perform CRM writes or retain a cross-run baseline. If the export fails or a source is unavailable, keep your last accepted CRM data and inspect the dataset diagnostics.

Size larger MX batches from the trial. The verification limit defaults to 50 attempts per run, shared across all submitted sites. For a batch of 200 distinct sites, that permits at most 50 sites with an MX-qualified CRM contact, or 25%. A 70% coverage target needs at least 140 qualifying checks even in the best case. One site can use several attempts. Compare the distinct contact-bearing sites exported in your trial with the sites submitted before increasing the batch size. On Starter/Bronze, 200 useful sites and 50 qualifying MX checks would total $2.00 in Actor events. This example includes Apify run usage and has SMTP, phone formatting, AI and connectors off. Enabling those options can add charges.

Try two weekly checks on 25 websites. After a useful small trial, plan one batch of 25 authorized websites in the offline reviewer below and download the paid MX pilot input. Use the same file for both runs, seven UTC days apart. It enables checked-only CRM export and caps MX verification at 25 attempts. At Starter/Bronze the downloaded settings have an Actor event ceiling of $0.40 for each original run, or $0.80 for the two planned runs before retries. The event prices include Apify run usage. Check each separate dated coverage summary for at least 18 distinct sites with an eligible contact before expanding.

To keep the charge cap with one private pilot task, expand Prepare a private pilot task with a charge cap, choose your tier and MX mode, and download the ZIP. Preview the included task saver before explicitly saving your private task. Start each run in Apify when ready.

Download the 60-second Contact CRM review demo (MP4) to see how to save a 25-site input and manifest, attach completed-run files and review coverage before accepting a baseline. The walkthrough uses synthetic records.

The current offline reviewer writes a version-2 coverage summary with separate selectedContactSites and mxQualifiedContactSites counts. Use mxQualifiedContactSites for the 18-site check. It counts distinct planned companies with unambiguous selected MX evidence, excluding SMTP-only and unchecked statuses. If an older download has only eligibleContactSites, re-review the original files to obtain the MX count. Confirm exact run inputs, export provenance and paid use separately in Apify.

Request a 25-site pilot review. If you can use the same 25 authorized websites for two weekly refreshes, open a Contact issue. Use the title 25-site Contact MX pilot and a short note such as “I would like to try the pilot.” The issue and replies are public. You can include your approximate site count, refresh cadence, and CRM platform. Keep company lists, contact data, credentials, billing details, files, and run IDs or links out of the public text. If you later choose to share a completed run, check the access shown in Apify's run-sharing control and attach that exact run. The attachment gives HarvestLab access to its input, logs, and default storages.

If you already refresh roughly 1,250 or more authorized company websites per week, you can include that volume to help us assess whether the pilot fits your larger workflow.

Reserve MX checks for later websites. For checked-only CRM exports with MX checks enabled and deep SMTP off, set crmMxReservePerSite: true to keep one attempt available per remaining website when the shared cap allows it. When the cap would omit addresses, a disposable address, a likely typo or a domain with a cached negative MX result can give way to an alternative within the same attempt budget. The hard attempt cap stays the same. An additional qualifying address can trigger the existing MX event. Sites with several addresses may receive fewer checks. Without this setting, checks continue in website order until the run's budget is used. Use the same tested build and settings for both weekly pilot runs. For an absent-site retry, the v16 reviewer keeps supported checked-only MX settings from the original input for any matched batch. The retry contains only the selected absent sites, with at most the smaller of the original MX cap and the number of selected sites. The reviewer shows the Starter/Bronze Actor event ceiling before downloading. Apify run usage is included. Use the Actor input editor directly for other input settings.

Review a completed one-site CRM export. In the offline reviewer, under Review Contact batches together, open Review a completed basic one-site run without a manifest. Choose the saved INPUT, CRM-EXPORT, and one CRM-upserts.json from the same completed run. Enter the UTC refresh dates to prepare a candidate baseline. Save the accepted baseline to compare a later refresh from the same site. Use the planner for a larger website list or a checked-only batch.

Plan and review multiple batches from one refresh. Download the offline Contact CRM batch reviewer and open the HTML file in your browser. Paste your company websites or choose a UTF-8 CSV with a header row and select the Website column. Before generating inputs, review any URLs with queries or fragments. Approve removal of recognized marketing queries or explicitly omit held rows. The planner creates capped Actor inputs and a batch manifest. Run the batches in Apify with CRM export enabled. Confirm that each run's CRM-EXPORT status is complete, then load the manifest and matching CRM-upserts.json files from the same refresh. From a larger CRM list, select a batch of 25 and choose Prepare pilot from selected batch. Choose Copy paid MX pilot JSON or download the same paid input. If you use per-site reservation, choose the matching copy or download. Save the matching manifest via Download pilot manifest for a selected batch or Download manifest for a 25-site plan. Use that manifest for both pilot refreshes so coverage is measured against the selected 25 sites.

Start from a saved website dataset. Download the offline Contact CRM reviewer with JSON intake. In Prepare Contact CRM batches, open Review websites from a JSON dataset. Choose a raw JSON array with a top-level website field in each usable row. Preview the proposed URLs and review missing, duplicate and held rows. Allow removal of recognized tracking tags only if those tags can be discarded. Resolve held rows or explicitly leave them out before accepting the list. Save the matching manifest. Choose Download Actor input for basic CRM discovery or use the paid MX controls for checked-only CRM. The file stays in your browser. Set the run timeout and maximum charge in Apify before starting.

For a review that combines checked-only exports from several runs, open Run evidence for export beside each file. Add CRM-EXPORT JSON and Complete default dataset JSON from the same completed run as that export. Export all items from the run's default dataset as JSON without a view, filters, or field selection. The Overview view omits emails_verified. Until the files reconcile, MX coverage is provisional and the reviewer holds unverified MX and SMTP contact changes. It can still prepare eligible company changes. With the source files, the reviewer holds an address found at another company even when only one company selected it. The MX-qualified count excludes SMTP-deliverable contacts. For basic exports, check the original dataset for unselected candidates before importing. Confirm run identity and billing separately in Apify. The files stay in your browser.

Prepare a paid MX original for this batch. After a useful small pilot, expand this option for the selected batch in a larger plan. Choose the MX attempt budget and optional per-site reservation, then download the checked-only input. The displayed Starter/Bronze Actor-event ceiling is conditional on useful sites and qualifying checks. Review the run timeout and set a maximum Actor charge in Apify before starting. Use the same batch settings on each refresh and compare companies reviewed with sites that returned a selected MX contact.

Prepare 200 sites for a weekly MX refresh. For 200 distinct authorized websites, Download the offline eight-batch MX planner. Paste the list or import a CSV, plan eight batches of 25, and select Download eight paid MX inputs and manifest (ZIP). The ZIP contains eight checked-only JSON inputs and one shared manifest. Import each JSON into Apify and choose a per-run cap using current pricing. With 25 billable sites and 25 qualifying MX checks, each original can cost $0.40 at Starter/Bronze or $0.50 at base rates. Eight originals can total $3.20 or $4.00 respectively before retries. Separate post-run storage usage can apply. Repeat with the same files seven UTC days later. Review all eight completed exports against the shared manifest and save each week's coverage separately.

If a 25-site checked-only pilot returns zero qualifying companies, open Review transient failures after an empty MX pilot in the offline reviewer. Load your planner manifest. Use the saved input, both CRM files and complete default dataset from the same succeeded Apify run. Choose up to five original URLs with recorded timeouts or deadline skips. Before starting the retry in Apify, review a 300-second timeout and $0.10 Actor charge cap. The original coverage stays at zero.

After reviewing exports for a dated refresh, open Prepare a private refresh receipt to save coverage and observation times. The receipt fingerprints the batch manifest and each export so you can verify the cohort and tell similarly named exports apart. Add the run IDs and roles you verified in Apify, then use those IDs to check charges for the original and any retries. Keep the receipt private.

Keep the tab open to add CRM-upserts.json files from completed retries. Choose the retry exports in the same review and select Review exports again. Remove an incorrect file or clear the selection when moving to another refresh. Review coverage and withheld records before downloading the company and contact observation CSVs. Set an optional UTC date range for one refresh and its retries to hold files with observations outside that range. Save a coverage summary with counts only when comparing successive refreshes. Enter the dates for one refresh to prepare a baseline. For later refreshes on the same cohort, add your last accepted baseline and review the proposed changes and candidate before using them. For HubSpot company updates, add a current Companies CSV to check proposed name and phone changes against existing Record IDs and current values. Verify all company and contact changes before accepting the full candidate. If the reviewed HubSpot company values are already current, use Verify current HubSpot companies and a fresh Companies CSV before accepting those rows. If only some HubSpot company updates landed, keep the original Companies CSV and check a fresh export from the same account under Verify a partial HubSpot import. Use the verified company baseline for the next dated refresh. Keep the previous baseline and original files to finish reviewing this refresh. Contact changes stay in the separate review. Files stay in your browser. The reviewer needs no API token and starts no Actor.

Review CRM changes in n8n

Use the Contact n8n template with an existing succeeded run that used exportCrm: true. It prepares changed company and selected-contact records for review and retains previously accepted records. It does not start a new scrape or write to your CRM. Follow the setup guide for private credentials, replay handling and destination acceptance.

In a new private n8n workflow, copy the Contact n8n template link address and choose Import from URL from the workflow menu. You can also download the same JSON and choose Import from File. Before adding your Apify credential or CRM records, open Settings. Set Save manual executions, Save execution progress, Save successful production executions, and Save failed production executions to Do not save. Enable Timeout Workflow and set it to 5 minutes. The n8n editor can keep the new workflow’s settings when it imports the nodes.

For a repeat batch, set contactReviewMode to fixed_cohort and copy the basic or MX-only input from the batch planner into expectedContactInput. Use one URL per company in the same order and set maxWebsites to the list length. Apply private HTTP Header Auth to Read saved Contact input as well as the other GET nodes. A changed company list, path, or crawl and MX setting stops the review before it reads CRM files. Keep the accepted snapshot's contact_scope for the next refresh. Check fixed_cohort_coverage for planned, observed and absent companies. For an ad hoc review, keep single_run.

For an eligible 25-site checked-only MX refresh with one completed retry, use the original run ID and add retryRunId in the same workflow. Set contactRefreshWindow to the UTC start and end dates of the refresh. The retry must use the original crawl and MX policy and target only sites absent from the original export. Apply private HTTP Header Auth to the retry and dataset GET nodes. Inspect Review original plus retry for observed companies and current MX-qualified sites. The workflow checks both complete datasets and keeps shared contact associations on hold. Verify buyer charges and settlement separately in Apify.

For an existing Amazon Product Scraper run, see the Amazon price-review instructions. Templates were tested on n8n 2.44.7; verify your own source and destination before enabling a downstream integration.

CRM Data Hygiene & Re-enrichment

Upload domains for any CRM segment with empty phone, email, linkedin_url, or tech_stack fields and bulk-update with fresh data from the source website. The dual phones + phones_validated shape lets you pick raw-extract vs format-valid per workflow. AI dedup groups info@ / hello@ / contact@ into a single primary contact per account.

Competitive Intelligence & Tech-Stack Tracking

Schedule regular scans on competitor domains. Detect when a target migrates CMS, swaps analytics, adds a CDP, or rolls out a new payment processor. The tech_stack array surfaces 175+ technologies, including CDPs (Segment, Pendo, PostHog), analytics, search platforms (Algolia, Typesense), build tools (Vite, Webpack), and feature-flag systems (LaunchDarkly).

Market Research & Industry Datasets

Build structured datasets of companies in a niche by feeding a domain list and exporting JSON / CSV / Excel. Combine tech stack adoption with contact data to segment markets by technology profile, company digital maturity, and likely deal size - perfect for analyst reports, investor decks, and trend studies.

Input

ParameterTypeDefaultDescription
urlsarray[]List of full website URLs (e.g., https://example.com).
startUrls / url / websitearray/string-API/CLI aliases for URL inputs. startUrls is merged with urls; singular aliases are accepted for one-off calls.
domainsarray[]List of bare domains (e.g., example.com, stripe.com). HTTPS is added automatically.
sourceWebsiteDatasetstring-Optional read-only Apify dataset ID. Uses its website column in place of all direct website and domain inputs.
maxPagesPerSiteinteger5Number of pages to crawl per site (1-20). More pages means more contact data found but longer runtime.
includeSubpagesbooleantrueAutomatically crawl /contact, /about, /imprint, and similar pages. Highly recommended - many sites only list contact info on subpages.
detectTechStackbooleanfalseDetect CMS, frameworks, analytics, and 175+ other technologies. Confidently detected Shopify stores can also return public store name, canonical URL, currency, and business country when available. Uses enriched-mode pricing: $0.01 per useful website instead of $0.0015 basic discovery.
validatePhonesbooleantrueFormat valid phones as E.164, with country and line type, for $0.02 per qualifying number in addition to the base event. Set false to return raw phones only. Not a carrier or reachability check.
verifyEmailsbooleanfalseCheck extracted email domains for MX records, typos and disposable/free-inbox signals, returning HIGH / MEDIUM / LOW / UNKNOWN in emails_verified. The $0.01 event requires boolean mx_valid: true, HIGH/MEDIUM and no typo/disposable flag. LOW/UNKNOWN is free even when MX resolves; domain checks do not prove mailbox existence.
deepEmailVerificationbooleanfalseOpt-in mailbox-level verification for every MX-cleared email. Classifies each as deliverable / undeliverable / catchall / greylisted / port_blocked / rate_limited. Rate-limited per mail host. Charges $0.02 per definitive verdict only. Requires verifyEmails: true.
enableAiAnalysisbooleanfalseEnable AI-powered contact enrichment - email role classification, team-address deduplication, primary-contact selection, and deliverability flags. Requires an API key for your chosen AI provider.
llmProviderstringopenrouterAI provider when enrichment is enabled: openrouter, anthropic, google, openai, or ollama.
openrouterApiKey / anthropicApiKey / googleApiKey / openaiApiKeystring-API key for the chosen provider. Ollama (self-hosted) uses ollamaBaseUrl instead.
outputConnectorsarray-Optional MCP connectors for per-website contact summaries. Sends counts plus extracted public emails, phones, social profiles, and contact metadata to authorized Slack, Notion, GitHub, Sheets, CRM, or other connector tools.
connectorAlertTargetstring-Optional connector destination, such as a Slack channel, Notion database ID, sheet name, table, or CRM list.
proxyConfigurationobject{"useApifyProxy": true}Uses automatic Apify Proxy selection by default. Choose a residential group for websites that block datacenter traffic.

You can provide input via urls, startUrls, url, website, domains, or any combination of them. Duplicates across inputs are removed automatically.

Read website URLs from a dataset

  1. Use a completed dataset in Apify Storage with a website string on each row you want to use, for example {"website":"https://www.python.org/about/help/"}. Use authorized website URLs without credentials, query strings or fragments, up to 2,048 characters each.
  2. In Input, clear Company website or contact-page URLs, including the example, and Company website domains. Under Existing website dataset, choose the dataset in Source dataset of websites (read only). For an API run, set sourceWebsiteDataset to the dataset ID and omit all direct URL and domain inputs or leave their lists empty.
  3. For a basic trial, select a dataset with one known contact page. Set Website Limit per Run and Max Pages Per Site to 1 and turn Include Subpages off. Turn off tech detection, email checks, phone formatting, AI and connectors. Enable the CRM export and leave Export Only MX-Qualified Emails off to include eligible unchecked contacts. Review CRM-EXPORT before using the downloaded company and contact files.

The Actor reads only website and keeps the first URL for each domain. Missing or empty values are skipped. Use at most 1,000 source rows and up to your Website Limit per Run (maximum 200 distinct sites). An unreadable or incomplete source, an invalid populated value, or a cohort beyond either limit returns a diagnostic before crawling or charging an Actor event. The source stays unchanged.

For repeated reviews, save the exact website list before each refresh. Keep it with the exports so you can check whether the source cohort changed between dates.

Basic discovery costs $0.0012 per useful site on Starter/Bronze or $0.0015 at the base rate, including Apify run usage. Dataset selection and CRM export add no Actor event. Standard storage charges can still apply. Optional checks and enrichment follow the rates below. Check current pricing.

Pricing

This Actor uses pay-per-event (PPE) pricing. Ordinary runs use the per-site and optional events below, which include Apify run usage. Prices are USD per event; base means Free/no-discount pricing. Starter (Bronze), Scale (Silver), and Business (Gold) receive 20%, 30%, and 40% discounts respectively. Platinum and Diamond match Gold. These are Apify subscription-plan discounts, not quantity breakpoints. The legacy $5 bundle stays flat. Check the live Pricing tab for your plan.

EventBaseStarter / BronzeScale / SilverBusiness / GoldWhen charged
lead-discovered$0.0015$0.0012$0.00105$0.0009Per persisted useful website in basic mode (detectTechStack: false, verifyEmails: false, deepEmailVerification: false). Diagnostic-only rows do not request this event.
contact-extracted$0.01$0.008$0.007$0.006Per useful website when tech detection, MX checks, or SMTP checks are enabled. Phone formatting and AI alone do not select this base tier; their qualifying events are additive.
verified-phone-extracted$0.02$0.016$0.014$0.012Per number that passes phone-format validation (E.164 + country + line-type). This is not a carrier or reachability check.
verified-email-checked$0.01$0.008$0.007$0.006Per email with boolean mx_valid: true, HIGH/MEDIUM deliverability and no typo/disposable flag. LOW/UNKNOWN is free, even when MX resolves. Only when verifyEmails is on.
verified-email-deep-checked$0.02$0.016$0.014$0.012Per definitive SMTP verdict (deliverable or undeliverable). catchall, greylisted, rate_limited, port_blocked, and error are free. Only when deepEmailVerification is on.
ai-analysis-completed$0.05$0.04$0.035$0.03Per completed structured analysis persisted in a useful contact row. Empty, invalid, provider-error, or unpersisted AI results are not charged.
connector-alert-dispatched$0.002$0.0016$0.0014$0.0012Per successful per-website summary delivery through an MCP output connector. Failed attempts are not charged.
skyfire-bundle-1000-leads$5.00$5.00$5.00$5.00Listed legacy bundle; ordinary runs do not request this event. A prepaid 1,000-lead route has not been verified.

Failed requests (unreachable sites, DNS errors) are not charged.

Actor-event subtotals for 100 useful websites:

ScenarioBaseStarter / BronzeScale / SilverBusiness / Gold
Raw discovery; tech/MX/SMTP/AI off, validatePhones: false$0.15$0.12$0.105$0.09
Same discovery plus one qualifying phone per site; validatePhones: true$2.15$1.72$1.505$1.29
Tech-enriched discovery, phone/MX/SMTP/AI off$1.00$0.80$0.70$0.60
Tech-enriched discovery plus one qualifying phone per site$3.00$2.40$2.10$1.80
Tech-enriched discovery plus one qualifying MX email per site, phones off$2.00$1.60$1.40$1.20

The basic and enriched website events are mutually exclusive. Phone, MX, SMTP, AI, and successful connector events are additive. Examples are Actor-event subtotals, not quotes for external AI or downstream services. maxWebsites defaults to 50 and has a hard cap of 200 per run; split larger lists into batches. These examples assume the specified useful results are found, not that every submitted website succeeds. Set a maximum charge in the Apify run options as an additional spending limit.

vs. commercial alternatives: this actor is a pay-per-event alternative to subscription lead tools and seat-based enrichers. You only pay for successful events.

Skyfire bulk bundle

The Pricing list contains a skyfire-bundle-1000-leads event at $5.00, but ordinary runs do not request it. A separate prepaid 1,000-lead payment route has not been verified. Use the documented per-site and optional-event prices when estimating a normal run; the listed bundle does not guarantee 1,000 results or replace those charges.

Automated Contact Enrichment Workflows

Contact-extractor returns structured records (emails, phones_validated, tech_stack, social_profiles, and optional verification fields). Optional role labels and contact selection live under ai_contact_analysis.email_roles and ai_contact_analysis.primary_contact, not at the row's top level. Use the mapping below in your own authorized integration; no private repository access is needed.

Company and contact mapping

Source fieldDestination and rule
domainStable company key; upsert rather than create a company every refresh.
company_name, url, social_profiles.linkedinCompany name, website, LinkedIn URL; preserve populated fields when source values are empty.
emails[]Contact email key; choose a published address, not an AI-invented contact.
emails_verified[]Reject available LOW/UNKNOWN, failed MX, disposable/typo flags and smtp_probe.result: undeliverable. HIGH/MEDIUM MX still means mailbox unknown. Unchecked published email is unverified.
ai_contact_analysis.primary_contact.emailOptional preferred email, only if it belongs to the eligible extracted list.
ai_contact_analysis.email_roles[]Optional role matched by email; not a numerical contact score.
phones_validated[].e164Optional format-valid phone, not a reachability check; raw phones[] is not validated.
scraped_at, urlObservation timestamp and public provenance.

Fetch the exact succeeded run's dataset; discard diagnostic and partial-only rows, deduplicate companies by domain and contacts by email, then upsert companies before contacts. Company-only records can enrich accounts without creating people. If one email appears under several domains, review the association rather than guessing. Replayed completions use the same keys. Failed/empty exports preserve prior good CRM data. Test mapping and unique keys in your authorized destination account before production writes. The Actor does not send email, enroll sequences or provide CRM credentials.

Common automation patterns:

  • Enrich a target-account CSV before an SDR sequence and keep only domains with verified company emails.
  • Add phone, social, address, and tech-stack fields to incomplete CRM accounts.
  • Re-run priority accounts quarterly to catch changed contact pages, new social profiles, or technology changes.
  • Review proposed HubSpot company changes and import the approved CSV. Use a compatible Apify integration or a webhook to send completed exports to other tools.

MCP Quickstart - call this actor from Claude / Cursor / ChatGPT

Review an existing CRM export. Connect your MCP client with Apify access to the run and select these tools:

https://mcp.apify.com?tools=get-actor-run,get-key-value-store-record
  1. Call get-actor-run with your runId. Confirm the response has the same runId, actorId set to bHzVpEmytvDNJk48m, and status set to SUCCEEDED.
  2. Pass storages.keyValueStores.default.id as keyValueStoreId to get-key-value-store-record with recordKey set to CRM-EXPORT. Check for status: complete, review the requested and exported counts, and inspect any post_crawl_interruption before using the files.
  3. Call the same tool and store again with recordKey set to CRM-upserts.json for the company and selected-contact records. The run's CRM Import Files view lists CRM-companies.csv and CRM-contacts.csv.

Try one new page. Configure https://mcp.apify.com?tools=call-actor,get-actor-run,get-key-value-store-record and pass these arguments to call-actor. The Actor input enables CRM export and switches off paid enrichment and phone formatting explicitly.

{
"actor": "harvestlab/contact-extractor",
"input": {
"urls": ["https://www.python.org/about/help/"],
"maxWebsites": 1,
"maxPagesPerSite": 1,
"includeSubpages": false,
"detectTechStack": false,
"validatePhones": false,
"verifyEmails": false,
"deepEmailVerification": false,
"enableAiAnalysis": false,
"exportCrm": true
},
"callOptions": {"memory": 256, "timeout": 300, "maxTotalChargeUsd": 0.10},
"waitSecs": 10
}

If the run is still active, check the returned run ID until it finishes, then use the same export review above. A useful site in this example costs $0.0012 on Starter/Bronze in basic-discovery events, including Apify run usage. The $0.10 is the Actor-charge cap. Post-run storage access can incur separate usage. Selected emails have published_unverified status in this trial. Apify MCP tools and run options

For a new run, compatible clients can use Apify's experimental prepaid token in their private Authorization header. The minimum purchase is $1, the balance caps spending, and unused funds expire after 14 days without a refund. Apify prepaid terms

Output

Each website produces a structured JSON object:

{
"url": "https://example.com",
"domain": "example.com",
"company_name": "Example Inc",
"company_description": "Example Inc is a technology company that helps businesses build better software solutions and streamline their operations.",
"emails": ["info@example.com", "sales@example.com"],
"emails_verified": [
{
"email": "info@example.com",
"domain": "example.com",
"mx_valid": true,
"mx_hosts": ["aspmx.l.google.com", "alt1.aspmx.l.google.com"],
"catchall": false,
"disposable": false,
"free_inbox": false,
"role_based": true,
"typo_suggestion": null,
"deliverability": "MEDIUM",
"deep_probe": true,
"probe_result": "deliverable",
"smtp_probe": {
"result": "deliverable",
"response_code": 250,
"response_text": "2.1.5 OK",
"mx_host": "aspmx.l.google.com",
"probed_at": "2026-04-23T03:15:22+00:00",
"is_catchall": false
}
},
{
"email": "sales@example.com",
"domain": "example.com",
"mx_valid": true,
"mx_hosts": ["aspmx.l.google.com", "alt1.aspmx.l.google.com"],
"catchall": null,
"disposable": false,
"free_inbox": false,
"role_based": true,
"typo_suggestion": null,
"deliverability": "MEDIUM",
"deep_probe": true,
"probe_result": "rate_limited",
"smtp_probe": {
"result": "rate_limited",
"response_code": null,
"response_text": "daily_cap_reached:10/10",
"mx_host": "aspmx.l.google.com",
"probed_at": "2026-04-23T03:15:22+00:00",
"is_catchall": null
}
}
],
"phones": ["+1 888 926 2289", "555-1234"],
"phones_validated": [
{
"raw": "+1 888 926 2289",
"e164": "+18889262289",
"country": "US",
"type": "TOLL_FREE",
"valid": true,
"possible": true
}
],
"phones_uncertain": ["555-1234"],
"social_profiles": {
"linkedin": "https://linkedin.com/company/example",
"twitter": "https://twitter.com/example",
"facebook": null,
"instagram": null,
"youtube": null,
"github": "https://github.com/example",
"tiktok": "https://tiktok.com/@example",
"pinterest": null,
"telegram": "https://t.me/examplecompany",
"discord": null,
"threads": "https://threads.net/@example"
},
"address": "123 Main St, City, State, 12345",
"contact_page_url": "https://example.com/contact",
"tech_stack": ["Shopify", "Cloudflare", "Google Analytics"],
"is_shopify_store": true,
"shopify_detection_confidence": "high",
"shopify_detection_signals": ["response-header", "shopify-store-identity", "shopify-asset-host"],
"shopify_store_name": "Example Store",
"shopify_canonical_url": "https://example.com/",
"shopify_currency": "USD",
"shopify_country": "US",
"pages_crawled": 3,
"scraped_at": "2026-04-10T12:00:00Z"
}

Which phone field should you use? For format-valid dialing, cold-call campaigns, or CRM import, use phones_validated - every entry carries a canonical E.164 string, ISO-3166-1 country code, and line-type so your dialer knows whether it's mobile, toll-free, or a PBX fixed line. The legacy phones list (all raw extracts) and phones_uncertain (parsed but not format-validated) are kept for backward compatibility and triage workflows.

The shopify_* fields and is_shopify_store are positive-only: they appear only when detectTechStack is enabled and public evidence confidently identifies Shopify. They are omitted for non-Shopify sites and inconclusive detections. This enrichment uses pages already fetched for contact extraction and does not request a product catalog or private Shopify API.

Null values indicate that the Actor searched for the data but did not find it on the crawled pages. Output is available as JSON, CSV, or Excel. For HubSpot, use the Companies CSV review. The native Apify HubSpot card uses a different Actor.

When enableAiAnalysis is true, each output item additionally includes:

  • ai_contact_analysis.email_roles - per-email classification (sales, support, hr, legal, executive, general, personal)
  • ai_contact_analysis.primary_contact - selected email and reasoning; this is not a numerical contact score
  • ai_contact_analysis.primary_phone - selected format-valid phone, when available
  • ai_contact_analysis.dedup_groups - near-duplicate team addresses grouped together
  • ai_contact_analysis.deliverability_flags - warnings for no-reply and non-monitored addresses

Technologies Detected

The Actor recognizes 175+ technologies across these categories:

  • CMS and Platforms - WordPress, Shopify, Wix, Squarespace, Drupal, Joomla, Ghost, Webflow, HubSpot
  • JavaScript Frameworks - React, Next.js, Vue.js, Nuxt.js, Angular, Svelte, jQuery
  • CSS Frameworks - Bootstrap, Tailwind CSS, Foundation, Bulma, Materialize
  • Analytics and Marketing - Google Analytics, Google Tag Manager, Facebook Pixel, Hotjar, Mixpanel, Segment, Plausible, Matomo, Microsoft Clarity, Amplitude, LinkedIn Insight Tag
  • Product Analytics - FullStory, LogRocket, PostHog, Pendo, Datadog RUM, Sentry, LaunchDarkly
  • Email Marketing - Mailchimp, SendGrid, Klaviyo, ActiveCampaign, Marketo, Pardot, ConvertKit
  • CRM and Sales - Salesforce, HubSpot, Pipedrive
  • Chat and Support - Intercom, Drift, Zendesk, Crisp, LiveChat, Tawk.to, Freshdesk
  • Authentication - Auth0, Okta, Firebase, Supabase
  • Search - Algolia, Elasticsearch, Typesense
  • Infrastructure - Cloudflare, Fastly, CloudFront, Vercel, Netlify, nginx, Apache, Akamai
  • E-commerce - WooCommerce, Magento, PrestaShop, BigCommerce, Stripe, PayPal
  • Video and Media - YouTube Embed, Vimeo, Wistia, Loom
  • Scheduling - Calendly, Acuity Scheduling
  • Social Proof - Trustpilot Widget, G2, Yotpo
  • Build Tools - Webpack, Vite, GraphQL, WebSocket

Quick Start

The simplest possible input - a list of domains:

{
"domains": ["stripe.com", "shopify.com", "hubspot.com"]
}

Or full URLs with custom crawl depth:

{
"urls": ["https://example.com", "https://anothersite.org"],
"maxPagesPerSite": 10,
"includeSubpages": true,
"detectTechStack": true
}

Enable email-domain and SMTP acceptance checks before reviewing CRM import eligibility:

{
"domains": ["stripe.com", "shopify.com"],
"verifyEmails": true,
"deepEmailVerification": true
}

Enable AI role classification and primary-contact selection:

{
"domains": ["stripe.com", "shopify.com"],
"verifyEmails": true,
"enableAiAnalysis": true,
"llmProvider": "openrouter",
"openrouterApiKey": "your-key-here"
}

Troubleshooting

A target is rejected as invalid input Use a bare domain or an HTTP(S) website URL. URLs with embedded usernames or passwords, malformed hosts or invalid ports are rejected before crawling. Rejected values are omitted from warnings and dataset diagnostics; the diagnostic retains invalid_input_count and redacted invalid_inputs placeholders. Mixed batches continue with valid targets. Rejected targets request no Actor business events. This does not rewrite Apify's original INPUT record: never paste credentials into website inputs. It is not a login workflow or a general redirect/network-access security guarantee.

SMTP verification returns "greylisted" for most emails Greylisting temporarily defers an SMTP request. A greylisted result is inconclusive: it does not establish whether that mailbox exists or will accept a message. The Actor requests no deep-verification event for this result. Keep the status when exporting and do not relabel it as a verified mailbox; any later check remains subject to the mail host's rate limits and may still be inconclusive.

Many emails flagged as "catchall" or "undeliverable" Catchall domains accept addresses regardless of whether a mailbox exists. Treat them as "valid domain, unknown mailbox." Filter the exported emails_verified[].smtp_probe.result field in your downstream workflow, retaining only deliverable when definitive mailbox evidence is required. MX HIGH/MEDIUM alone does not prove mailbox existence.

No tech stack signals returned Tech detection depends on what the target website publishes publicly. Pages behind login walls, very dynamic apps, or sites that block automated access may return fewer tech signals. The actor detects 175+ technologies from publicly visible website assets only. Shopify context is likewise omitted unless the public evidence is strong enough for a positive detection.

AI role classification returns wrong roles The AI role classifier uses the email prefix and page context to infer roles (sales/marketing/engineering/executive/support). It cannot access LinkedIn or internal org data. For ambiguous prefixes (info@, hello@, contact@), it classifies as "unknown" - these are typically shared inboxes.

Rate limited or IP blocked mid-crawl The actor implements reputation-safe probe rate limits (max 10 SMTP probes per domain per UTC day, 10s cooldown). If a domain blocks the probe IP, the actor logs smtp_blocked: true and falls back to MX-only verification. HTTP proxy settings do not route SMTP probes, and the actor never charges for blocked or inconclusive probes.

No emails found for a domain The site may not publish contact emails publicly. The actor still checks canonical host variants, sitemap-discovered contact URLs, and common paths such as /contact, /about, /impressum, and /legal. If no billable contact data is found, the row is marked as partial_result, fetch_failed, site_timeout, or site_error and includes fetch_diagnostics. The actor only extracts contacts that are publicly visible - it does not guess or generate addresses.

How many pages should I crawl per website? The default of 5 pages works well for most sites. The Actor prioritizes /contact, /about, and /imprint pages. Set maxPagesPerSite to 1 if you only need tech stack data and want the fastest possible run. Increase to 10-20 for large corporate sites where contact details may be spread across many sections.

Can I input just domain names without https://? Yes. Use the domains field with bare domain names like "stripe.com" or "hubspot.com". The Actor adds HTTPS automatically. You can also mix urls (full URLs) and domains (bare domains) in the same run.

How does email deliverability verification work? When you set verifyEmails: true, every extracted email runs through a four-step pipeline:

  1. Typo check - Common mail-domain misspellings such as gmial.com, outllok.com, hotmial.com, and iclould.com are flagged with a typo_suggestion and tagged LOW deliverability.
  2. Disposable / burner check - Known disposable hosts (Mailinator, 10MinuteMail, GuerrillaMail, YOPmail) are hard-flagged LOW regardless of MX state.
  3. Real MX lookup - The Actor runs an actual DNS MX query against the domain. Domains that have no MX record cannot receive mail and are tagged LOW.
  4. Tiering - Emails at free inboxes (Gmail / Yahoo / Outlook / iCloud / ProtonMail) OR with role prefixes (info@, hello@, support@, sales@) land in MEDIUM. Named addresses at non-free company domains with resolved MX land in HIGH.

How does the deep SMTP probe work? When verifyEmails and deepEmailVerification are both on, every MX-cleared email receives a mailbox-level acceptance check. No email content is delivered. Results are classified as deliverable, undeliverable, catchall, greylisted, port_blocked, rate_limited, or error, and the checks are capped per mail host to avoid aggressive probing.

How does phone validation work? Every phone candidate is normalized and checked against regional phone-number rules. Numbers that pass validation land in phones_validated with E.164, country code, and line type. Numbers that parse but fail strict validation land in phones_uncertain. This gives you a cleaner phone field without paying for a separate cleanup service.

What if a website blocks the scraper? Some sites block datacenter IP addresses. The default preset lets Apify select a compatible proxy automatically. Choose a residential group for harder sites. If proxy setup fails, the actor retries once and returns a no-charge diagnostic instead of terminating the run. Sites behind login walls or aggressive bot protection may still remain inaccessible. Failed requests are not charged.

Frequently Asked Questions

Can I extract contacts from a website URL? Yes. Provide full URLs in urls or bare domains in domains. The actor normalizes each target, crawls the homepage plus contact-oriented subpages, and returns emails, phones, socials, addresses, contact-page URLs, and technology signals when they are publicly visible.

Is this a contact details extractor or an email finder? Both. The core workflow extracts public contact details from a website, including emails, phones, social profiles, addresses, and contact-page URLs. Email verification and AI role labeling are optional paid enrichments for teams that need cleaner outreach records.

What is the best first run for a domain list? Start with maxPagesPerSite: 3, detectTechStack: false, and verifyEmails: false on one or two domains. If the output looks useful, run the larger list with tech-stack detection enabled, then re-run only promising domains with email verification.

Can I use this as a B2B lead extractor? Yes. Start with a list of company domains, then export the resulting contact rows to your CRM or outreach tool. The actor is strongest for company-level B2B enrichment, ABM lists, recruiting research, market maps, and CRM cleanup.

Does it verify email addresses? Yes, when verifyEmails: true is enabled. The actor checks email domains with MX lookup and deliverability signals. For deeper mailbox checks, enable deepEmailVerification: true; definitive deliverable or undeliverable SMTP verdicts are charged only when produced.

Does it find personal emails for every company? No. It extracts contact details that the website makes publicly visible. Many companies publish shared inboxes like info@, sales@, or contact forms rather than personal decision-maker emails. AI role classification can help prioritize the best available inbox.

Can it extract phone numbers and social profiles too? Yes. The output includes raw phones, validated phones in E.164 format when possible, LinkedIn and other social profiles, addresses, and a canonical contact-page URL.

Workflow: provide a list of public company domains or website URLs, then run contact-extractor to return CRM-ready contact records and enrichment signals.


Scheduling and webhooks

Save your tested input as a task and add a weekly Apify schedule. Configure an Apify run-succeeded webhook or integration to fetch that exact run's default dataset. Use the company/contact mapping above with your own authorized destination credentials. Reject diagnostics and failed checks, deduplicate keys, preserve non-empty values, and retry by upsert instead of repeated contact creation. Do not trigger outreach or sequence enrollment as an extraction side effect.


This actor scrapes publicly available data. By using this actor, you agree to the following:

  • Your responsibility: You are solely responsible for ensuring your use complies with all applicable laws, regulations, and the target website's terms of service. This includes but is not limited to GDPR (EU), CCPA / CPRA (California), CAN-SPAM Act (US), CASL (Canada), PECR (UK), LGPD (Brazil), and other data protection / anti-spam laws in your jurisdiction.
  • No legal advice: This actor does not constitute legal advice. Consult a qualified attorney if you have questions about the legality of your specific use case.
  • Intended use: This actor is designed for legitimate business purposes such as market research, competitive analysis, and B2B lead generation using publicly accessible data.
  • Data handling: You are responsible for how you store, process, and share any data collected. Ensure you have a lawful basis (e.g. legitimate interest under GDPR Art. 6(1)(f), or pre-existing business relationship under CASL) for processing any personal data under applicable privacy laws.
  • CAN-SPAM compliance (US): Any commercial email you send using contacts from this actor must include a clear, conspicuous opt-out mechanism, a valid physical postal address, accurate "From" / "Reply-To" headers, non-deceptive subject lines, and you must honor unsubscribe requests within 10 business days. Penalties are up to $53,088 per violation under the FTC's enforcement schedule.
  • GDPR compliance (EU/UK): Even publicly available personal data is subject to GDPR. You must have a lawful basis (typically legitimate interest with documented LIA), respect Art. 14 transparency requirements (notify the data subject within 30 days when collecting from a third-party source), honor erasure / objection requests promptly, maintain records of processing under Art. 30, and not transfer EU data outside the EU/EEA without an SCC, adequacy decision, or other approved mechanism.
  • Anti-spam / outreach: Do NOT use this tool for unsolicited bulk messaging, spam, scraped-list email blasts, or list-building for resale. Use for permission-tested, targeted, B2B-relevant outreach only.
  • Rate limiting: This actor implements polite crawling practices including request delays and retry backoff to minimize impact on target servers.
  • No warranty: This actor is provided "as is" without warranty. Data accuracy depends on the target website's content and structure.
  • Personal data minimization: Implement data retention policies (typically 6-12 months for cold outreach contacts), encrypt PII at rest and in transit, restrict internal access on a need-to-know basis, and honor opt-out / Do-Not-Contact requests across your entire system, not just the channel that received the request.
  • Mailbox verification: Deep email verification uses rate-limited mailbox checks and never delivers email content. Some mail server operators may still log or flag verification attempts, so use this option responsibly and only on domains you have explicitly listed in urls or domains.
  • Indeed Scraper - Pipe Indeed job listings into a recruiter sourcing pipeline: identify hiring companies, then run Contact Extractor on company websites you supply to collect available published business contact details. Specific hiring-manager identities and contacts are not guaranteed.

Share feedback from your run

If you have used the output, an honest Store review can help other users decide whether this Actor fits their workflow. Describe what worked and what did not. For an issue, describe the expected output without sharing private data in the public text. Use Apify's run-sharing control for any relevant run you choose to attach.