# Wellfound Email Scraper - Keyword & Location Targeting (`scrapido/wellfound-email-scraper`) Actor

🚀 Wellfound Email Scraper extracts startup founder and hiring manager emails by keyword and location. 🔓 Domain filters plus decoding and duplicate handling. 📤 Export Wellfound leads to CSV, JSON or Excel for tech recruiting.

- **URL**: https://apify.com/scrapido/wellfound-email-scraper.md
- **Developed by:** [Scrapido](https://apify.com/scrapido) (community)
- **Categories:** Lead generation, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.50 / 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

### Wellfound Email Scraper 🔍

**Wellfound Email Scraper** helps marketers, recruiters, and sales pros find and extract authentic contact emails from Wellfound without manually hunting profile-by-profile. It streamlines **email scraper** workflows and supports **extract emails from Wellfound** using your chosen keywords—so your **Wellfound lead generation** can scale quickly and stay consistent across larger batches.

***

### 🌟 Key Features of Wellfound Email Scraper

| Feature | Benefit |
|---|---|
| ✅ **Targeted Keyword Search** | Reach the exact Wellfound audience you need for email harvesting and outreach |
| ✅ **Location Filtering** | Geo-target contacts by adding a location filter to your Wellfound lead generation runs |
| ✅ **Custom Domain Filter** | Extract only emails matching the domains you specify (for example `@gmail.com` or `@yahoo.com`) |
| ✅ **Bulk Export (Dataset)** | Store scraped results directly in your Apify dataset for easy CRM integration or analysis |
| ✅ **Proxy-Ready Scraping** | Built-in proxy support helps keep web scraping reliable for larger runs |
| ✅ **Real-Time Saving** | Each result is saved incrementally, reducing risk of losing progress on long executions |
| ✅ **Max Emails Control** | Cap results with `maxEmails` to manage cost and runtime while building your email list |

***

### 📥 Input — Wellfound Email Scraper Parameters

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

| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| `keywords` | Array | ✅ Yes | — | A list of keywords to search for in order to find relevant Wellfound profiles for email extraction |
| `location` | String | No | `""` | Optional location filter to narrow results to a specific city, region, or country |
| `customDomains` | Array | No | `["@gmail.com","@yahoo.com"]` | Only collect emails that match these domains (helps you build cleaner, more predictable contact lists) |
| `maxEmails` | Integer | No | `20` | Maximum number of emails to collect per run (higher limits can take longer and don’t guarantee you’ll reach the cap) |

***

### 📤 Output — What Wellfound Email Scraper Returns

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

```json
{
  "keyword": "founder",
  "title": "Ava Johnson",
  "description": "Product builder and startup founder. Previously led growth and partnerships. Currently exploring new B2B launches.",
  "url": "https://wellfound.com/profile/ava-johnson",
  "email": "ava.johnson@gmail.com"
}
```

| Field | Type | Description |
|---|---|---|
| `keyword` | String | The search term used to surface this Wellfound result for contact enrichment |
| `title` | String | The Wellfound profile name or business title associated with the scraped lead |
| `description` | String | Profile bio or summary text captured during scraping (useful for research and segmentation) |
| `url` | link | Direct link to the Wellfound profile for quick verification and CRM syncing |
| `email` | String | The email address extracted from the profile based on your keyword and domain filters |

***

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

1. **Open the Actor** — Launch **Wellfound Email Scraper** in Apify and go to the **Input** panel.
2. **Enter Keywords** — Add job titles, roles, or terms you associate with the Wellfound audience you want to reach.
3. **Set Location** *(optional)* — If you need region-specific outreach, fill in `location`.
4. **Filter by Domain** *(optional)* — Add domains in `customDomains` (for example `@gmail.com` or company domains).
5. **Set Max Emails** — Use `maxEmails` to control runtime while building your email list building pipeline.
6. **Run the Actor** — Start the run and monitor progress in Apify logs.
7. **Export Results** — Use the Apify dataset tab to export for CRM integration or web scraping analysis.

***

### 💡 Best Use Cases for Wellfound Email Scraper

- 🎯 **B2B Lead Generation** — Build a focused Wellfound email list for targeted outreach
- 📣 **Email Marketing** — Power newsletters and sequences with fresh Wellfound contacts
- 🤝 **Recruitment** — Identify Wellfound professionals to contact directly
- 🔬 **Market Research** — Analyze profiles by keyword, role, and region while extracting authentic contact data
- 🧩 **CRM Enrichment** — Add extracted emails to existing CRM records for better coverage

***

### Disclaimer

This actor only accesses publicly available data on Wellfound. It does not scrape private profiles, authenticated content, or password-protected pages. You are responsible for ensuring your use complies with applicable laws and Wellfound’s Terms of Service, including anti-spam requirements and privacy regulations (such as GDPR/CCPA where applicable). For data-removal requests, contact 📧 <scrapidocontact@gmail.com>.

***

### 🆘 Support & Feedback

Have a question or need help with the **Wellfound Email Scraper**? We’re here to support your email harvesting and contact enrichment workflow.

- 🐞 **Bug Reports:** Share details in the repository’s Issues section
- ✨ **Custom Solutions & Feature Requests:** Reach out to our team
- 📧 **Email:** <scrapidocontact@gmail.com>

Your feedback helps improve the Wellfound email scraper experience for web crawler and email list building use cases.

### Multiple Email Types

**Email Types** replaces the old single Audience Type choice: select as many
kinds of mailbox as you want and the run chases all of them together.

| Type | What it matches |
| --- | --- |
| Personal / free webmail | Gmail, Outlook, Yahoo, iCloud, AOL, Proton, ... |
| Business / corporate | Company domains - free webmail and institutions excluded |
| Education (.edu / .ac) | `.edu`, `.ac.uk`, `.edu.au`, `.ac.in` and other academic suffixes |
| Government (.gov / .mil) | `.gov`, `.mil`, `.gov.uk`, `.gc.ca`, ... |
| Non-profit (.org) | `.org`, `.ngo`, `.org.uk`, ... |

Each selected type contributes its own Google dork patterns *and* its own domain
test, so a result is only kept if it genuinely belongs to the type that found
it. Every row carries an `emailType` field recording which one that was.

Suffixes are matched as real domain suffixes, so `cs.mit.edu` counts as
Education while `notedu.com` does not.

Setting **Custom Email Domains** still overrides everything: an explicit domain
list is a manual override and replaces the type-driven patterns. The legacy
`audienceType` value is still accepted, so saved inputs keep working.

# Actor input Schema

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

A list of keywords or queries to search for.

## `audienceType` (type: `string`):

Business Emails runs contextual discovery patterns tuned for company contact pages ("email us at", "contact@", careers, bookings, ...) and filters out consumer webmail domains. Consumer Emails instead searches gmail.com, yahoo.com, outlook.com, hotmail.com and icloud.com directly.

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

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

Optional manual override — provide specific email domains to search for (e.g. @hubspot.com) instead of using Audience Type. Leave empty to use Audience Type.

## `emailTypes` (type: `array`):

Which kinds of mailbox to hunt for. Pick as many as you like - each type contributes its own set of Google search patterns and its own domain filter, and every result records the type it was found as. Personal = free webmail (Gmail, Outlook, Yahoo, iCloud). Business = company domains, excluding free webmail and institutions. Education = .edu / .ac.uk and friends. Government = .gov / .mil. Non-profit = .org.

## Actor input object example

```json
{
  "keywords": [
    "manager",
    "founder"
  ],
  "audienceType": "Consumer Emails",
  "maxEmails": 20,
  "customDomains": [],
  "emailTypes": [
    "Personal",
    "Business"
  ]
}
```

# 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"
    ],
    "customDomains": [],
    "emailTypes": [
        "Personal",
        "Business"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapido/wellfound-email-scraper").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",
    ],
    "customDomains": [],
    "emailTypes": [
        "Personal",
        "Business",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("scrapido/wellfound-email-scraper").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"
  ],
  "customDomains": [],
  "emailTypes": [
    "Personal",
    "Business"
  ]
}' |
apify call scrapido/wellfound-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapido/wellfound-email-scraper"
        }
    }
}

```

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/hi25eneqyuSgyKvie/builds/yIu7JnAfzmeU2uYTK/openapi.json