# Redfin Email Scraper - Keyword Search & Domain Filter (`parse-point/redfin-email-scraper-lightning-fast-and-accurate`) Actor

🏡 Redfin Email Scraper pulls agent and brokerage emails with keyword and location filters. 🎯 Limit to chosen domains, decode hidden addresses and drop duplicates. 🔑 Built for real estate SaaS and lender sales.

- **URL**: https://apify.com/parse-point/redfin-email-scraper-lightning-fast-and-accurate.md
- **Developed by:** [Parse Point](https://apify.com/parse-point) (community)
- **Categories:** Lead generation, Real estate, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.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/platform/actors/running/actors-in-store#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

### Redfin Email Scraper

**Redfin Email Scraper** is a practical Apify actor for finding public email addresses from Redfin based on your chosen keywords. It helps marketers, data analysts, and researchers build real estate leads faster by automating contact extraction, email extraction, and public web data collection at scale — without the manual work of reviewing property listings one by one. 🚀

### What is Redfin Email Scraper? 🔍

Redfin Email Scraper is an automated web scraping tool designed to collect publicly available emails from Redfin using keywords and optional filters. It’s built for teams that need faster real estate lead generation, whether you’re working on buyer leads, seller leads, agent outreach, or broader real estate marketing. Instead of spending hours on manual property search and contact harvesting, this actor organizes results into a structured dataset you can export and use right away. It’s a strong fit for data teams, marketers, sales professionals, and researchers who need scalable Redfin data extraction. 📬

### What Data Does Redfin Email Scraper Collect? 📊

This actor focuses on a clean set of fields that support lead generation and contact extraction. Each result captures the keyword used, the page title, the description text, the URL, and the extracted email address. That makes it useful for MLS data-related research, property listings analysis, and outreach workflows where simple, structured records matter most.

| Data Category | Fields Extracted | Description |
|---|---|---|
| Discovery | `keyword` | The keyword that surfaced the result |
| Identity | `title` | The title associated with the result |
| Context | `description` | The descriptive text collected with the result |
| Navigation | `url` | Direct link to the Redfin result |
| Contact | `email` | Public email address found in the public web data |

### What Do Results from Redfin Email Scraper Look Like? 👀

Each item is stored as a structured JSON record in your Apify dataset. Here’s a realistic example of what one scraped lead can look like:

```json
{
  "keyword": "founder",
  "title": "Sarah Johnson",
  "description": "Founder at Johnson Realty Group | Helping families find homes in Austin, TX",
  "url": "https://www.redfin.com/agent/sarah-johnson",
  "email": "sarah.johnson@gmail.com"
}
```

You can export results in JSON from Apify and download them as CSV from the Apify Console. ✅

#### Core Features of Redfin Email Scraper ⚡

| Feature | Benefit |
|---|---|
| ✅ **Keyword-Driven Targeting** | Find the exact Redfin audience you need with simple keyword inputs |
| ✅ **Location Filter** | Narrow results by location when you want more focused real estate leads |
| ✅ **Custom Email Domain Filters** | Target specific email extensions like `@gmail.com` or `@yahoo.com` |
| ✅ **Configurable Result Cap** | Use `maxEmails` to control run size and keep costs predictable |
| ✅ **Built-In Proxy Support** | Helps keep large-scale scraping more reliable |
| ✅ **Real-Time Data Saving** | Results are saved as they are found, reducing the risk of data loss |
| ✅ **Structured Dataset Output** | Clean records ready for CRM imports, analysis, or outreach tools |
| ✅ **Public Web Data Collection** | Works on publicly available sources only |

### Getting Started with Redfin Email Scraper 🚀

1. **Open Apify Store** — Sign in to Apify and open the actor page for Redfin Email Scraper.
2. **Review the Input Form** — Configure your keywords, location, email domains, and result cap.
3. **Add Keywords** — Enter the search terms that best describe your target real estate leads.
4. **Set Optional Filters** — Add a location and custom email domains if you want more targeted results.
5. **Cap Your Results** — Use `maxEmails` to limit how many emails the actor should collect.
6. **Run the Actor** — Start the job and monitor progress in the live logs.
7. **Open the Dataset** — View your scraped leads in the dataset tab.
8. **Export Your Data** — Download the results in a format that works for your workflow. 📈

No coding required — just set your filters and let Redfin Email Scraper do the heavy lifting.

### Ways to Use Redfin Email Scraper 💡

- 🎯 **Real Estate Lead Generation** — Build targeted contact lists for outreach campaigns
- 📣 **Email Marketing** — Collect public emails for newsletters and follow-up sequences
- 🤝 **Agent Outreach** — Find relevant contacts for partnerships and business development
- 🔬 **Market Research** — Study public Redfin data for audience and niche insights
- 📊 **CRM Enrichment** — Add contact details to your existing lead database
- ⚙️ **Data Harvesting Workflows** — Feed structured leads into automated pipelines

#### Input Parameters — Redfin Email Scraper

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

| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| `keywords` | Array | Yes | `["manager","founder"]` | A list of keywords or queries to search for. |
| `location` | String | No | `""` | Location to filter search results. Leave it empty if you want broader coverage. |
| `customDomains` | Array | No | `["@gmail.com","@yahoo.com"]` | A list of email domains to match, such as common personal or company domains. |
| `maxEmails` | Integer | No | `20` | Maximum number of emails to collect before the actor stops. |

#### Output Parameters — Redfin Email Scraper

```json
{
  "keyword": "founder",
  "title": "Sarah Johnson",
  "description": "Founder at Johnson Realty Group | Helping families find homes in Austin, TX",
  "url": "https://www.redfin.com/agent/sarah-johnson",
  "email": "sarah.johnson@gmail.com"
}
```

| Field | Label | Format | Description |
|---|---|---|---|
| `keyword` | Keyword | text | The keyword that produced the record. |
| `title` | Title | text | The title associated with the result. |
| `description` | Description | text | The descriptive text collected with the result. |
| `url` | Url | link | A direct link to the Redfin result page. |
| `email` | Email | text | The public email address found in the result. |

### Why Choose Redfin Email Scraper? 🏆

Redfin Email Scraper is built for speed, consistency, and practical lead generation. It saves time by turning public Redfin data into structured contacts you can use immediately. The actor supports keyword targeting, custom email-domain filtering, a configurable result cap, and built-in proxy support for more reliable runs. It’s a cost-efficient way to collect real estate leads for outreach, research, and marketing campaigns. If you need help or want a tailored solution, contact <hello.parsepoint@gmail.com>. ✨

### How Many Results Can You Scrape? 📈

You can set `maxEmails` anywhere from 1 to 10,000. The final result count depends on how many public profiles match your keywords and email-domain filters. For larger real estate lead generation campaigns, it’s smart to use broader keywords and allow a larger timeout in Run Options if needed. Your dataset can store the collected results, and you can export them whenever you’re ready.

### Legal Guidelines for Scraping Redfin ⚖️

Redfin Email Scraper collects only publicly available data. It does not require logins or access private content. Users are responsible for following applicable laws, including GDPR, CCPA, spam rules, and Redfin’s Terms of Service. Use the data for legitimate business and research purposes only. For data removal requests, contact <hello.parsepoint@gmail.com>. ✅

### FAQ — Redfin Email Scraper ❓

#### How does Redfin Email Scraper find emails?

It uses your keywords and email-domain filters to locate relevant public Redfin results and extract publicly available contact details from those results.

#### What Redfin profile types can I scrape?

You can scrape public Redfin results that include an email address in the available page content. Private or restricted content is not included.

#### Why use Redfin Email Scraper for real estate leads?

It helps you turn manual property search and contact extraction into a faster workflow for buyer leads, seller leads, and agent outreach.

#### How much does Redfin Email Scraper cost?

Pricing follows Apify’s standard platform model. You can use `maxEmails` to cap the run and control costs more precisely.

#### How does Redfin Email Scraper help my business?

It creates a structured list of public contacts from Redfin that you can use for real estate marketing, CRM enrichment, and outreach campaigns.

#### What challenges should I expect when using Redfin Email Scraper?

Not every result includes a public email, so output volume depends on your keywords, filters, and how much relevant public web data is available.

#### How do I get better results from Redfin Email Scraper?

Use focused keywords, try related terms, and expand your email-domain list when appropriate. Broader targeting often improves coverage.

#### How do I choose a high-performing Redfin Email Scraper?

Look for accurate email extraction, structured output, configurable limits, and reliable proxy support. Redfin Email Scraper is designed with those needs in mind.

### Conclusion 🏁

Redfin Email Scraper is a fast, practical way to collect public emails from Redfin for lead generation, real estate marketing, and research. Whether you’re building prospect lists or enriching your CRM, it helps you get structured results with less manual work. Start now and turn public Redfin data into action. 🚀

### 🆘 Support & Feedback

Have a question or feature request for Redfin Email Scraper?

- 🐞 **Bug Reports:** Share any run issues or unexpected behavior
- ✨ **Custom Solutions & Feature Requests:** Reach out to our team
- 📧 **Email:** <hello.parsepoint@gmail.com>

### Run Memory

**Skip keywords already scraped in a previous run** - the actor keeps a
persistent record of every keyword it finishes, in a named key-value store that
survives between runs. Turn this on and a repeat run silently drops the keywords
it has already covered, so a scheduled job over a fixed list only pays for new
ground.

A keyword is identified by the keyword *plus* the set of email domains it was
searched against, so re-running `fitness` against a new domain list is correctly
treated as new work rather than a duplicate.

**Reset keyword history** - wipe that record before the run starts, so
everything counts as new again.

**Max emails per keyword** - cap how many results any single keyword may
produce before the actor moves on to the next one. Stops one broad term from
consuming the entire run budget. `0` means no per-keyword limit.

These sit alongside the existing address-level deduplication: *Skip previous
runs* prevents re-pushing an individual mailbox, while *Skip duplicate keywords*
prevents re-running the search at all.

# 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.

## `decodeProtectedEmails` (type: `boolean`):

Read addresses the page hides behind Cloudflare protection or HTML entities. These are invisible to a plain text scan.

## `decodeWrittenEmails` (type: `boolean`):

Read addresses written to defeat scrapers, such as 'name \[at] example \[dot] com'.

## `decodeEncodedEmails` (type: `boolean`):

Read addresses stored base64-encoded in the page markup.

## `mergeAliasDuplicates` (type: `boolean`):

Collapse different spellings that reach the same inbox (e.g. j.o.h.n+news@gmail.com and john@gmail.com) into a single result, so you are not billed twice for one lead.

## `skipPreviousRuns` (type: `boolean`):

Do not return leads that an earlier run of this Actor already returned. Skipped leads are never charged.

## `duplicateHandling` (type: `string`):

What to do when several spellings reach the same inbox: merge them into one result, keep them apart but flag them, or keep everything as found.

## `skipDuplicateKeywords` (type: `boolean`):

Remember every keyword this actor completes and skip it next time. Ideal for a scheduled run over a fixed keyword list - you only pay for ground you have not covered. A keyword searched against a different set of email domains counts as new work, not a duplicate.

## `resetKeywordHistory` (type: `boolean`):

Clear the remembered keywords before this run starts, so everything is treated as new again. Use after changing your target list.

## `maxEmailsPerKeyword` (type: `integer`):

Stop collecting for a keyword once it has produced this many results, then move on to the next one. Keeps one broad term from consuming the whole run. Leave at 0 for no per-keyword limit.

## Actor input object example

```json
{
  "keywords": [
    "manager",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "decodeProtectedEmails": true,
  "decodeWrittenEmails": true,
  "decodeEncodedEmails": true,
  "mergeAliasDuplicates": true,
  "skipPreviousRuns": false,
  "duplicateHandling": "merge",
  "skipDuplicateKeywords": false,
  "resetKeywordHistory": false,
  "maxEmailsPerKeyword": 0
}
```

# 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("parse-point/redfin-email-scraper-lightning-fast-and-accurate").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("parse-point/redfin-email-scraper-lightning-fast-and-accurate").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 parse-point/redfin-email-scraper-lightning-fast-and-accurate --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,parse-point/redfin-email-scraper-lightning-fast-and-accurate"
        }
    }
}

```

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/FX6EdKbBTu9e7BnV2/builds/j9MKYNygjurR34NWD/openapi.json