# Wix Email Scraper - Domain Filter & Deduplication (`insightflow/wix-email-scraper-powerful-and-intelligent`) Actor

🧩 Wix Email Scraper — turn Wix searches into a clean site owner email list. Filter by keyword, location and domain, merge aliases and decode hidden addresses. 💼 For web agencies, SEO services & SMB lead generation.

- **URL**: https://apify.com/insightflow/wix-email-scraper-powerful-and-intelligent.md
- **Developed by:** [InsightFlow](https://apify.com/insightflow) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.99 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### Wix Email Scraper 🔍

**Wix Email Scraper** helps you find publicly available email addresses from Wix using your chosen keywords and filters. It’s built for marketers, recruiters, sales pros, and researchers who want faster Wix email extraction, easier Wix lead generation, and a practical Wix contact scraper without manual hunting. 🚀

### 🌟 Key Features of Wix Email Scraper

| Feature | Benefit |
|---|---|
| ✅ **Targeted Keyword Search** | Use relevant keywords to surface Wix pages tied to your niche or audience. |
| ✅ **Location Filtering** | Narrow results by location when you want more focused Wix contact extraction. |
| ✅ **Custom Email Domain Filters** | Limit results to domains like `@gmail.com` or `@yahoo.com` for cleaner lead lists. |
| ✅ **Max Emails Control** | Stop the run once your desired number of emails is reached. |
| ✅ **Real-Time Dataset Saving** | Each result is saved as it’s found, which reduces the risk of losing data during longer runs. |
| ✅ **Built for Public Web Data** | Scrapes emails from publicly available sources on Wix for safer, more practical prospecting. |

### 📥 Input — Wix Email Scraper Parameters

```json
{
  "keywords": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20
}
```

| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| `keywords` | Array | ✅ Yes | `["manager","founder"]` | Keywords or queries used to find relevant Wix pages and contacts. |
| `location` | String | No | `""` | Optional location filter to narrow the results. |
| `customDomains` | Array | No | `["@gmail.com","@yahoo.com"]` | Email domains to include when collecting addresses. |
| `maxEmails` | Integer | No | `20` | Maximum number of emails to collect before the actor stops. |

### 📤 Output — What Wix Email Scraper Returns

The actor saves each result as a JSON record in your Apify dataset. 📊

```json
{
  "keyword": "founder",
  "title": "Founder & CEO | Bright Path Studio",
  "description": "Helping small businesses build memorable brands and convert more customers.",
  "url": "https://www.wix.com/profile/bright-path-studio",
  "email": "hello@brightpathstudio.com"
}
```

| Field | Label | Format | Description |
|---|---|---|---|
| `keyword` | Keyword | text | The keyword that matched this result. |
| `title` | Title | text | The page title or lead name shown for the result. |
| `description` | Description | text | The visible page description or summary text. |
| `url` | Url | link | The direct URL to the Wix page. |
| `email` | Email | text | The email address found in publicly available content. |

### 💻 How to Use Wix Email Scraper — Step-by-Step

1. **Open the actor** — Find **Wix Email Scraper** in the Apify Store and open the actor page.
2. **Enter keywords** — Add terms like job titles, roles, or business-related phrases relevant to your Wix lead generation goals.
3. **Set a location** — Use the optional location filter if you want more focused Wix website scraper results.
4. **Choose email domains** — Add domains such as `@gmail.com`, `@yahoo.com`, or company addresses to refine your Wix business email finder results.
5. **Set the max emails limit** — Control how many leads the Wix scraper tool collects in a single run.
6. **Run the actor** — Start the run and monitor progress in the logs.
7. **Export the dataset** — Download your Wix email collection from the dataset tab when the run finishes.

No coding required — just run it and review your results. ✨

### 💡 Best Use Cases for Wix Email Scraper

- 🎯 **B2B Lead Generation** — Build targeted Wix leads scraper lists for outreach campaigns.
- 📣 **Email Marketing** — Collect public contacts for newsletters, nurturing, and follow-ups.
- 🔎 **Research Projects** — Use Wix data extraction to study businesses, creators, or local services.
- 🤝 **Sales Prospecting** — Find relevant contacts faster for outbound prospecting and account research.
- 📊 **CRM Enrichment** — Add new public contact details to existing lead records.

### Disclaimer

This actor only accesses publicly available data on Wix. It does not access private profiles, password-protected pages, or authenticated content. Users are responsible for complying with applicable laws, privacy rules, anti-spam regulations, and Wix’s terms. This tool is intended for legitimate lead generation, research, and marketing use cases only.

For data removal requests, please contact 📧 <insightflowofficial@gmail.com>.

### 🆘 Support & Feedback

Have a question or want help with the Wix Email Scraper? We’re here for you. 💬

- 🐞 **Bug Reports:** Let us know if something isn’t working as expected.
- ✨ **Custom Features:** Share ideas for Wix email harvesting, Wix site crawling, or other improvements.
- 📧 **Email:** <insightflowofficial@gmail.com>

Your feedback helps improve the actor and shape future updates.

### MX Lookup

Every address is checked at the DNS level: the actor resolves the mail domain's
MX records and reports what it found.

| Field | Meaning |
| --- | --- |
| `mxFound` | `true` when the domain publishes at least one mail server |
| `mxHost` | The lowest-preference (primary) mail server |
| `mxRecords` | Every MX record found, in preference order |
| `mxProvider` | Who runs the mail: Google Workspace, Microsoft 365, Zoho, Proton, ... |
| `mxStatus` | `found`, `no_records`, `no_such_domain`, `timeout`, `error`, or `skipped` |

**Inputs**

- **MX Lookup** - turn the check on or off (default: on).
- **Only keep contacts whose domain has an MX record** - drop unreachable domains.
  Only a definite negative (`no_records` / `no_such_domain`) drops a contact; a
  timeout or resolver error is treated as unknown and the lead is kept.
- **MX lookup timeout (seconds)** - per-domain DNS budget, 1-15s.

This is a domain-level check. It confirms the domain can receive mail; it does
not verify that an individual mailbox exists.

# Actor input Schema

## `keywords` (type: `array`):

A list of keywords or queries to search for.

## `location` (type: `string`):

Location to filter search results.

## `customDomains` (type: `array`):

List of custom email domains

## `maxEmails` (type: `integer`):

Maximum number of emails to collect. The scraper will stop once this limit is reached. Setting a higher limit allows for more potential results but doesn't guarantee reaching that number. This helps save costs by controlling scraping time.

## `minLeadScore` (type: `integer`):

Drop any contact whose Lead Score (0-100) falls below this. Leave at 0 for no filter.

## `mxLookup` (type: `boolean`):

Resolve each address's domain to its mail servers. Adds the resolved MX hosts and the mail provider (Google Workspace, Microsoft 365, ...) to every result, and feeds the Lead Score. DNS-level only - it confirms the domain can receive mail, not that the individual mailbox exists.

## `requireMxRecord` (type: `boolean`):

Drop any contact whose domain provably accepts no mail. A lookup that times out or errors is treated as unknown and kept, so a DNS hiccup never silently deletes good leads.

## `mxTimeoutSecs` (type: `integer`):

How long to wait for each DNS answer. Clamped to 1-15 seconds.

## Actor input object example

```json
{
  "keywords": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "minLeadScore": 0,
  "mxLookup": true,
  "requireMxRecord": false,
  "mxTimeoutSecs": 3
}
```

# Actor output Schema

## `dataset` (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 = {
    "keywords": [
        "manager",
        "founder"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("insightflow/wix-email-scraper-powerful-and-intelligent").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 = {
    "keywords": [
        "manager",
        "founder",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("insightflow/wix-email-scraper-powerful-and-intelligent").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 '{
  "keywords": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ]
}' |
apify call insightflow/wix-email-scraper-powerful-and-intelligent --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,insightflow/wix-email-scraper-powerful-and-intelligent"
        }
    }
}

```

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/fNkCnfhcwmyNf22IH/builds/rbrWzM0CNJRoc5ySK/openapi.json