# Threads Email Scraper (`socialdataapi/threads-email-scraper`) Actor

Threads Email Scraper searches public Threads profile pages for your keywords and returns pages that show an email: profile title, snippet, link and email. Filter by location and email domain. No Threads account or login. Export as JSON, CSV or Excel, or use the API.

- **URL**: https://apify.com/socialdataapi/threads-email-scraper.md
- **Developed by:** [Social Data API](https://apify.com/socialdataapi) (community)
- **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.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

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

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### Threads Email Scraper — Public Profile Emails by Keyword

Threads Email Scraper searches public Threads profile pages for your keywords and returns every page that shows an email address, with the profile title, a short text snippet and the direct link. **Each keyword runs as its own search**, so a list of niches becomes one combined lead list. Every response is structured JSON, ready for an LLM, a CRM or an outreach pipeline. No Threads account, login or cookies are needed. Start with a couple of keywords, then scale up once you see the leads each one returns.

***

### What data can I extract with Threads Email Scraper?

Using this Threads Email API, you will be able to extract the following Threads profile data:

| 📧 Email | 🔗 Page URL | 🏷️ Title | 🔎 Keyword |
| --- | --- | --- | --- |
| 📝 Description (snippet) | 🌐 Network (always threads.net) | | |

***

### How to use Threads Email Scraper

Anyone building a lead list from Threads — growth marketers, recruiters, sales teams — gets a combined list of public profile pages that mention an email address, from a single run with as many keywords as they need.

**Copy to your AI assistant:**

```text
Threads Email Scraper is an Apify Actor that returns public Threads profile pages matching a list of keywords as structured JSON: the keyword that matched, the page title, a text snippet, the page URL and the email address shown on it. Use it whenever someone needs leads from public Threads profiles without a login, a browser, or hand-checking search results - building an outreach list by niche, finding contributors in a city, or monitoring which profiles in a space publish contact details. Inputs: keywords (array of strings, required, one search per keyword), location (string, optional city or region filter), emailDomains (array of strings, optional, e.g. "@gmail.com" - keeps only matching domains and sharpens the search), maxEmails (integer 1-100000, default 10, maximum emails to return per keyword), proxyConfiguration (object, default automatic - optional custom proxy settings). Free-plan accounts are limited to 20 emails per keyword per run and 200 per month; paid plans have no limit. Each new email returned is billed as one "row_result" event.
```

#### Step by step

1. [Create a free Apify account](https://console.apify.com/sign-up).
2. Open [Threads Email Scraper](https://apify.com/socialdataapi/threads-email-scraper) in the Apify Store.
3. Enter one or more keywords (e.g. "fitness coach", "photographer").
4. Click **Start**.
5. Download or stream your results in JSON, CSV or Excel.

#### How to scale Threads Email Scraper to bulk

Scrape threads profile emails in bulk by adding as many keywords as you need to the `keywords` list in a single run — up to three keywords are searched at the same time, and each one keeps its own result limit and de-duplication, so a 50-keyword run returns one combined, duplicate-free list without any extra setup. For recurring lead lists, schedule the same input on a daily or weekly Apify schedule instead of running it by hand.

***

### ✨ Features

Threads Email Scraper fetches clean, structured email leads from public Threads profile pages ⚡. As a threads lead generation tool, you can find emails on threads by keyword, location and domain in a single run. It's ideal for outreach list building, community research and market research by niche.

It extracts, per result:

- **Email** – the public email address found on the page, lower-cased
- **URL** – direct link to the public Threads profile page, so you can verify the source
- **Title** – the profile's display name and handle
- **Keyword** – which of your input keywords found this result
- **Description** – the public text snippet shown with the result (bio or post text, up to 500 characters)
- **Network** – always `threads.net` for this actor

⚡ No Threads account, login or cookies needed — every row is read from a page anyone can already see.

***

### Use cases 💡

Use it as a threads contact email extractor for outreach, recruiting or market research.

- **Growth marketer** — build outreach lists of profiles by niche keyword and city.
- **Recruiter** — find coaches, artists and photographers who publish a public contact address.
- **Sales rep** — use it as a threads app email scraper to spot small businesses and creators active on Threads in a target market.
- **Community researcher** — run it as a threads public profile email scraper to see which profiles in a niche share contact details.
- **AI agent builder** — feed matched emails straight into a lead-enrichment or outreach pipeline.

Building an AI agent? Connect Threads Email Scraper to your own automation and let it run on a schedule.

***

### Why choose this actor?

As a threads.net email finder, it keeps going past the first page of results instead of stopping early.

1. **Keeps searching after the first page runs dry.** Up to 15 search series run per keyword — the direct search plus individual-post-page, date-restricted, region-restricted and outreach-term variants — continuing until the keyword's limit is reached or there is nothing left to show.
2. **Real extraction, not a guess.** This threads bio email finder checks each candidate address against the page's own markup to repair addresses split across inline formatting tags, and rejects it if it matches one of 36 known placeholder patterns ("username@...", "johndoe@...") or trails off after an ellipsis.
3. **Built to keep running through blocks.** A four-tier proxy fallback (your own proxy URLs → your Apify proxy settings → the default search proxy group → a direct connection) and up to 3 retries per page keep a keyword moving instead of failing on the first blocked page.

***

### ⬇️ Input

Threads Email Scraper accepts a list of keywords; every other field is optional. `keywords` is the only required field.

| Parameter | Required | Type | Description | Example value |
| --- | --- | --- | --- | --- |
| keywords | ✅ Yes | array | One or more keywords. Each keyword is searched separately; more specific keywords give more targeted leads. | `["fitness coach", "makeup artist"]` |
| location | No | string | Optional city or region. Only pages that mention this place are kept. Default: empty (worldwide). | `"London"` |
| emailDomains | No | array | Keep only emails of these domains (the `@` is optional). Default: empty (any domain). | `["@gmail.com", "@outlook.com"]` |
| maxEmails | No | integer | Maximum emails to return per keyword, 1-100,000. Default: `10`. Free plan: 20/keyword/run, 200/month. | `100` |
| engine | No | string | Processing engine; only `"legacy"` is available. Default: `"legacy"`. | `"legacy"` |
| proxyConfiguration | No | object | Connection settings. Default: automatic proxy selection. | `{"useApifyProxy": false}` |

***

### Free plan limits

Users on the Apify free plan can fetch up to 20 items per run (all keywords together) and 200 items per month. When the limit is reached, the run finishes successfully with a status message explaining the limit. Upgrade to any paid Apify plan to remove these limits.

***

#### Example input

```json
{
  "keywords": ["fitness coach", "makeup artist"],
  "location": "London",
  "emailDomains": ["@gmail.com", "@outlook.com"],
  "maxEmails": 100,
  "engine": "legacy",
  "proxyConfiguration": { "useApifyProxy": false }
}
```

***

### ⬆️ Output

Every result is one typed, normalized JSON item with the same six fields on every run, pairing a public email address with the Threads profile page that published it. Export as JSON, CSV or Excel directly from the dataset.

#### Example output

```json
[
  {
    "network": "threads.net",
    "keyword": "artist",
    "title": "Jay Frostt ❄️ (@jayfrosttx)",
    "description": "946 Followers • 224 Threads • New Orleans @hiddendimensionstudio 6723 Saint Claude Ave Booking: JayFrosttHD@ gmail.com #SnowflakeGang Studio Artist",
    "url": "https://www.threads.com/@jayfrosttx",
    "email": "jayfrostthd@gmail.com"
  }
]
```

***

### How does it work?

Threads Email Scraper searches Google for public Threads profile pages that match your keywords and pulls the contact details shown in them. Requests go through rotating proxies, and a blocked or failed page is retried automatically with a fresh connection. The actor never logs in to Threads and only reads what any visitor to a public profile page already sees — no account, cookies or private data are involved. The output schema is fixed (network, keyword, title, description, url, email) and stays the same from run to run, so downstream code never has to adapt when Threads changes its page layout. Scrapier maintains the actor and ships fixes as Threads's public pages change.

***

### How do you integrate Threads Email Scraper into your stack?

Threads Email Scraper works with what you already use: a REST API from any language, and no-code tools for teams that don't write scrapers by hand.

#### No-code tools (n8n, Make, LangChain)

In n8n, use the Apify node's "Run an Actor" action, or the HTTP Request node pointed at the Actor's run-sync endpoint with your Apify token. In Make, use the Apify app's "Run an Actor" module followed by "Get Dataset Items" to pull the results into your scenario. In LangChain, install `langchain-apify` and call `ApifyActorsTool()` to let an agent run the actor and read its dataset directly.

***

### Is it legal to scrape Threads data?

Scraping publicly available data is generally permissible, but how you use what you collect is your responsibility. Threads Email Scraper only returns information shown on public pages — the same text any visitor sees without logging in. Under GDPR and similar laws, scraping public data is generally allowed, but storing and using it must comply with local data-protection law, and sending unsolicited bulk email to addresses collected this way can fall under anti-spam laws like CAN-SPAM. Consult legal counsel if your use case involves bulk storage of personal data.

***

### Frequently asked questions

#### What fields does Threads Email Scraper return?

Every result includes the email address, the profile title, the page URL, the keyword that matched and a text snippet. Use it to find threads business email leads together with the page that published them. See [the data fields section](#what-data-can-i-extract-with-threads-email-scraper).

#### Does Threads Email Scraper require a Threads account or login?

No. Only public page data is extracted. No credentials are needed, and the actor never logs in to Threads.

#### What happens if no public page shows an email for my keyword?

That keyword simply returns no rows instead of a guess — nothing is invented. Try a broader keyword, remove the location filter or add more email domains to widen the search.

#### Can I scrape multiple Threads profile emails at once?

Yes. Pass a list to `keywords`; up to three keywords are searched at the same time, and results stay grouped by the keyword that found them.

#### Does Threads Email Scraper return data in a format LLMs can use directly?

Yes. Every result is typed, normalized JSON with consistent field names — no HTML parsing or selectors. Pass it straight to an LLM, index it into a vector store, or feed it to an agent tool with no transformation step.

#### Can I use Threads Email Scraper without managing proxies or browser infrastructure?

Yes. Proxy rotation and retrying blocked pages run on the actor's side. You send one request and get structured JSON back — no proxy accounts or headless browser setup to maintain.

#### What happens when Threads changes its layout?

Scrapier maintains the actor. When Threads changes its public pages, Scrapier updates the actor — your calls keep returning the same JSON schema with no changes on your end.

#### Which fields work best for AI training data and RAG indexing?

For RAG: the description and title fields carry the free text worth indexing. For structured filtering: keyword, network and url are stable, typed strings with no normalization needed.

***

### Your feedback

Found a bug or missing a field? Open a ticket in this actor's Issues tab and describe what you saw. The Scrapier team reads every report and ships fixes into the actor over time.

# Actor input Schema

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

One or more keywords (e.g. marketing, coach, photographer, fitness). Each keyword is searched separately on public Threads pages and every email found is returned with the keyword that found it. More specific keywords give more targeted leads.

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

Optional city or region (e.g. London, New York, Dubai). Only pages that mention this place are kept. Leave empty to search worldwide.

## `emailDomains` (type: `array`):

Keep only emails of these domains, e.g. @gmail.com, @outlook.com, @hotmail.com, @yahoo.com, @icloud.com or a business domain like @yourcompany.com (the @ is optional). The domains also sharpen the search. Leave empty to collect emails of any domain.

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

How many emails to collect per keyword (1 - 100,000). A keyword stops earlier when no more public results with an email are available. Free plan users are limited to 20 items per run in total (across all keywords) and 200 items per month; paid plans have no limit.

## `engine` (type: `string`):

Processing engine. Only 'legacy' is available.

## `proxyConfiguration` (type: `object`):

How the actor connects. Leave it as it is and a suitable Apify proxy is selected automatically. When a page is blocked the actor retries with a fresh proxy session (up to 3 attempts per page). You can also choose your own Apify proxy groups or custom proxy URLs.

## Actor input object example

```json
{
  "keywords": [
    "marketing"
  ],
  "location": "",
  "emailDomains": [
    "@gmail.com"
  ],
  "maxEmails": 10,
  "engine": "legacy",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `results` (type: `string`):

Dataset rows: network, keyword, title, description, url, email.

# 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": [
        "marketing"
    ],
    "emailDomains": [
        "@gmail.com"
    ],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("socialdataapi/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": ["marketing"],
    "emailDomains": ["@gmail.com"],
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("socialdataapi/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": [
    "marketing"
  ],
  "emailDomains": [
    "@gmail.com"
  ],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call socialdataapi/threads-email-scraper --silent --output-dataset

```

## MCP server setup

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