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

🧵 Threads Email Scraper finds creator and brand business emails by keyword and location. 🔓 Custom domain filters, obfuscated-address decoding and duplicate handling. 📤 Export Threads leads to CSV, JSON or Excel for social marketing.

- **URL**: https://apify.com/scrapido/threads-email-scraper.md
- **Developed by:** [Scrapido](https://apify.com/scrapido) (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 $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

### Threads Email Scraper

**Threads Email Scraper** is an Apify actor that automates extraction of public email addresses from Threads—solving the biggest problem teams face: slow, manual inbox data mining. It helps marketers, recruiters, and data teams build outreach lists faster with an email scraper and thread email extraction workflow. Scale contact discovery in minutes and improve ROI with structured results.

### What is Threads Email Scraper? 🔍

Threads Email Scraper is an automated web scraping tool (an Apify actor) designed to extract email addresses from Threads based on the keywords and filters you choose. If you’re doing outreach list building the hard way, this Threads Email Scraper streamlines research into a repeatable email extractor workflow. It also works as a Threads contact scraper by capturing profile context (title and description), plus direct profile links. The actor is built for marketers, recruiters, sales teams, and analysts who need a reliable Threads lead generation tool to turn targeted search terms into thousands of usable contacts at scale.

### What Data Does a Threads Email Scraper Collect? 📊

Threads Email Scraper focuses on contact discovery: it captures public emails from Threads along with the profile context you’ll want for segmentation and outreach personalization. You’ll also see which keyword surfaced each record, and where the profile points.

| Data Category | Fields Extracted | Description |
|---|---|---|
| Contact | `email` | Public email address found on a Threads profile |
| Identity | `title`, `description` | Profile title and summary text that helps you understand who the contact is |
| Context | `description` | Bio/profile summary text used for context during lead evaluation |
| Discovery | `keyword` | The search keyword used to surface this result |
| Navigation | `url` | Direct link to the relevant Threads profile |
| Location | `description` | Location-like info (if present in the profile text) |

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

Each result is a structured JSON record saved to your Apify dataset. Here’s a real example:

```json
{
  "keyword": "founder",
  "title": "Maya Chen",
  "description": "Founder @NorthPeak Studio | Building communities • Product storytelling",
  "url": "https://www.threads.com/@mayacnorthpeak",
  "email": "maya@northpeakstudio.com"
}
```

Each dataset row is ready for export, including JSON as the default and CSV via Apify Console.

#### Core Features: Threads Email Scraper ⚡

| Feature | Benefit |
|---|---|
| ✅ **Keyword-Driven Targeting** | Use your own keywords/queries to focus on the Threads audience you care about |
| ✅ **Location Filter** | Add a `location` string to narrow results to a specific geo context |
| ✅ **Custom Domain Filter** | Use `customDomains` to restrict extracted emails to domains like `@gmail.com` or `@yahoo.com` |
| ✅ **Configurable Result Cap** | Control run size and cost with `maxEmails` (stops once the cap is reached) |
| ✅ **Proxy Support** | Built-in proxy support helps keep large runs more consistent |
| ✅ **Real-Time Data Saving** | As results are found, they are pushed incrementally to the Apify dataset |
| ✅ **Structured Dataset Output** | Clean, labeled fields make email harvesting and data cleaning and deduplication easier downstream |
| ✅ **Works on Public Web Data** | Extracts from publicly available Threads content without requiring logins |
| ✅ **Resumable Progress** | Includes resume state so interrupted runs can continue without starting over |

### Getting Started with Threads Email Scraper 🚀

1. **Open Apify Store** — Go to [apify.com/store](https://apify.com/store) and search Threads Email Scraper
2. **Click Try for Free** — Sign in or create a free Apify account
3. **Open the Input Tab** — Configure your scraping parameters
4. **Add Keywords** — Enter the `keywords` that match your target audience
5. **Set Optional Filters** — Add `location` and/or `customDomains` to narrow extraction
6. **Cap Your Results** — Set `maxEmails` to limit runtime and spending
7. **Click Start** — Launch the run and monitor progress in the logs
8. **Access Your Data** — Open the Dataset tab to preview and export your results

First results are typically available quickly, and the run is designed for scale with outreach list building in mind.

### Ways to Use Threads Email Scraper 💡

- 🎯 **B2B Lead Generation** — Extract email addresses from Threads profiles to power outbound campaigns
- 📣 **Email Marketing** — Build fresh contact lists for newsletters and drip sequences using thread email extraction
- 🤝 **Talent Recruitment** — Reach creators and professionals by building a targeted Threads email finder list
- 🔬 **Market Research** — Learn which niches show up for specific keywords, then enrich with contact info
- 📊 **CRM Enrichment** — Append Threads contact extraction results to existing lead databases
- ⚙️ **Data Pipelines** — Schedule repeat runs and keep your outreach list up to date with email address extraction

#### Input Parameters — Threads Email Scraper

| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| `keywords` | Array | ✅ Yes | — | A list of keywords or queries used to find Threads profiles where emails may appear |
| `location` | String | No | `""` | Location text used to filter results (for example, a city, state, or country name) |
| `customDomains` | Array | No | `["@gmail.com","@yahoo.com"]` | Restrict extracted emails to specific domains only (e.g., `@gmail.com`, `@yahoo.com`) |
| `maxEmails` | Integer | No | `20` | Maximum number of emails to collect. The actor stops once this limit is reached |

#### Input Parameters (example)

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

#### Output Parameters — Threads Email Scraper

```json
{
  "keyword": "founder",
  "title": "Alex Rivera",
  "description": "Creative Director at Studio Co. | Available for freelance",
  "url": "https://www.threads.com/@alexrivera",
  "email": "alex@studioco.com"
}
```

| Field | Label | Format | Description |
|---|---|---|---|
| `keyword` | Keyword | text | The keyword that surfaced this contact during extraction |
| `title` | Title | text | The profile title or name shown in the scraped result |
| `description` | Description | text | Profile bio/summary text used as context |
| `url` | Url | link | Direct link to the Threads profile |
| `email` | Email | text | Extracted public email address |

### Why Choose This Threads Email Scraper? 🏆

Threads Email Scraper is built for speed and usability: it produces structured dataset output that you can export and plug into outreach workflows. With keyword-driven targeting, optional location filtering, and `customDomains` for email harvesting quality control, you spend less time cleaning and more time acting on results. It also supports reliable runs using proxy support for large batches, and it saves results incrementally to the dataset. Cost control is straightforward thanks to pay-per-result style usage on Apify—with a precise cap using `maxEmails`.

### How Many Results Can You Scrape? 📈

Use `maxEmails` to cap results from **1 to 10,000**. Actual volume depends on how many Threads profiles matching your keywords and domain filters contain publicly available emails. Bigger keyword sets and higher caps can take longer. Results are stored in the Apify dataset and can be exported anytime after the run completes.

### Legal Guidelines for Scraping Threads ⚖️

Threads Email Scraper accesses **publicly available data** on Threads. It does not require logins or authenticated access to private profiles. You are responsible for complying with Threads Terms of Service and applicable privacy and anti-spam regulations (including GDPR/CCPA where relevant). Use extracted contact information for legitimate business purposes only. Data removal requests: <scrapidocontact@gmail.com>.

### FAQ — Threads Email Scraper ❓

#### How does the Threads Email Scraper identify data?

Threads Email Scraper uses your provided keywords and optional filters to retrieve Threads profile results, then extracts any publicly listed email addresses and associated profile fields for each matching record. It does not rely on private or authenticated access.

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

You can scrape public Threads accounts where contact information (including emails) is available in publicly visible profile content. If a profile does not expose an email address publicly, you should expect fewer results for that keyword/domain combination.

#### How did the Threads Email Scraper perform in our tests?

Performance depends on your niche and how many matching profiles publish emails that align with your `customDomains` filter. In practice, the actor is designed to return consistent structured records suitable for thread email extraction and outreach list building.

#### Why scrape Threads for contacts?

Threads hosts many professionals and creators who share contact details publicly. Automating contact extraction saves time and helps data teams move faster from discovery to outreach list building.

#### How much does the Threads Email Scraper cost?

Pricing is pay-per-result. You can cap the run with `maxEmails` to control cost precisely. Free monthly credits may be available for new Apify users.

#### How does the Threads Email Scraper help my business?

It turns keyword-driven discovery into an exportable contact dataset containing `email`, plus helpful context like `title`, `description`, and the profile `url`. This makes it easier to enrich CRMs and run outreach automation.

#### What challenges should I expect when using the Threads Email Scraper?

Not every Threads profile includes a public email address. If you see low yield, broaden your keywords, adjust `customDomains`, or add/remove the `location` filter to improve coverage.

#### How do I choose a high-performing Threads email scraper?

Start with targeted keywords that match your audience, then narrow email quality using `customDomains`. Use a reasonable `maxEmails` cap to keep runs efficient. Structured dataset output and incremental saving make it easier to perform data cleaning and deduplication after export.

### Conclusion 🏁

Threads Email Scraper helps you extract emails from Threads at scale using keyword-driven targeting and clean, structured dataset output. Whether you’re building a lead list, enriching a CRM, or powering outreach automation, you can run it quickly on Apify—then export when the dataset is ready.

### 🆘 Support & Feedback

Have a question or feature request for Threads Email Scraper?

- ✨ **Custom Solutions & Feature Requests:** Email <scrapidocontact@gmail.com>
- 📧 **Email:** <scrapidocontact@gmail.com>

### 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/threads-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/threads-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/threads-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapido/threads-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/ByeacashPCK3hRLAB/builds/naovJDYD5BuIXPKJh/openapi.json