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

🏗️ Porch Email Scraper pulls home-service pro emails with keyword and location filters. 🎯 Limit to specific domains, decode hidden addresses and drop duplicates. 🧰 Built for building supplier and franchise sales.

- **URL**: https://apify.com/parse-point/porch-email-scraper-lightning-fast-and-accurate.md
- **Developed by:** [Parse Point](https://apify.com/parse-point) (community)
- **Categories:** Lead generation, Automation, Developer tools
- **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

### Porch Email Scraper 🔍

**Porch Email Scraper** helps marketers, recruiters, and sales pros extract emails from Porch faster than manual email hunting ever could. It streamlines porch email scraper workflows, supports email extraction for lead generation, and makes contact harvesting from public web data much more efficient. ⚡

### 🌟 Key Features of Porch Email Scraper

| Feature | Benefit |
|---|---|
| ✅ **Targeted Keyword Search** | Use your keywords to focus on the most relevant public business directory scraper results and improve lead generation quality. |
| ✅ **Location Filtering** | Narrow results by location to support local business leads and more precise prospect data extraction. |
| ✅ **Custom Domain Filter** | Filter by email domains like `@gmail.com` or `@yahoo.com` to refine email finder results. |
| ✅ **Bulk Export Ready** | Results are saved in a structured dataset, making sales outreach and CRM imports easier. |
| ✅ **Built-In Retry Logic** | Includes retries and fallbacks for resilience when scraping public contact information. |
| ✅ **Incremental Saving** | Each result is stored as soon as it is found, reducing the risk of data loss on longer runs. |

### 📥 Input — Porch 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"]` | A list of keywords or queries to search for. Use this to guide your email extraction and find relevant Porch profiles. |
| `location` | String | No | `""` | Location to filter search results. Helpful when you want local business leads or regional prospect data extraction. |
| `customDomains` | Array | No | `["@gmail.com","@yahoo.com"]` | List of custom email domains to include in the search, such as personal or company email domains. |
| `maxEmails` | Integer | No | `20` | Maximum number of emails to collect. The scraper stops when this limit is reached to help control cost and run time. |

### 📤 Output — What Porch Email Scraper Returns

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

```json
{
  "keyword": "founder",
  "title": "Sarah Mitchell",
  "description": "Founder at BrightSide Marketing. Contact for partnerships and consulting opportunities.",
  "url": "https://www.porch.com/profile/sarah-mitchell",
  "email": "sarah.mitchell@gmail.com"
}
```

| Field | Label | Format | Description |
|---|---|---|---|
| `keyword` | Keyword | text | The keyword that produced the result. Useful for organizing lead generation campaigns and reviewing prospect data extraction performance. |
| `title` | Title | text | The title or profile name returned from Porch. |
| `description` | Description | text | The public description or summary associated with the result. |
| `url` | Url | link | The direct URL to the Porch profile or public page. |
| `email` | Email | text | The email address found in publicly available contact information. |

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

1. **Open the Actor** — Find **Porch Email Scraper** in the Apify Store and open the actor page.
2. **Enter Keywords** — Add job titles, roles, or other terms you want to use for web scraping and lead generation.
3. **Set Location** — Optionally narrow your search to a city or region for more local business leads.
4. **Add Email Domains** — Include one or more domains to refine your email finder results.
5. **Set Max Emails** — Choose how many emails you want the run to collect before stopping.
6. **Run the Actor** — Start the actor and monitor progress in the logs.
7. **Export Results** — Download the dataset and use it in your sales outreach or customer acquisition workflow.

No coding required — results are ready in minutes. 🚀

### 💡 Best Use Cases for Porch Email Scraper

- 🎯 **B2B Lead Generation** — Build targeted contact lists for outreach and sales prospecting.
- 📣 **Email Marketing** — Collect public contact information for newsletters and nurture campaigns.
- 🔬 **Market Research** — Study public business directory scraper results and identify relevant professionals.
- 🤝 **Sales Outreach** — Find decision-makers and contacts faster for direct outreach.
- 📊 **CRM Enrichment** — Add fresh email extraction results to your existing databases.

### Disclaimer

This actor only accesses publicly available data on Porch. It does not scrape private profiles, authenticated content, or password-protected pages. Users are responsible for complying with applicable laws, platform terms, and anti-spam regulations when using the data. This tool is intended for legitimate lead generation, research, and customer acquisition purposes only. For data-removal requests, contact 📧 <hello.parsepoint@gmail.com>.

### 🆘 Support & Feedback

Have a question or need help with the **Porch Email Scraper**?

- 🐞 **Bug Reports:** Tell us what happened so we can investigate.
- ✨ **Custom Solutions & Feature Requests:** Share your ideas for new lead generation and contact harvesting workflows.
- 📧 **Email:** <hello.parsepoint@gmail.com>

Your feedback helps improve the actor for researchers, marketers, and data analysts.

### 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/porch-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/porch-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/porch-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/porch-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/LQTZjRaZAvbqO8hqf/builds/ahqDLdfQB3urhTLIO/openapi.json