Threads Email Scraper

Threads Email Scraper

Threads Email Scraper

The Threads Email Scraper is an Apify Actor that collects publicly indexed contact emails from Meta's Threads. Feed it keywords, get back a structured dataset of creator and founder leads.

Threads is where Instagram's audience went to write. Founders, marketers, journalists and creators post there daily, and many keep a business-inquiry address in their profile bio.

The Threads Email Scraper exists to collect exactly those public addresses, with the account metadata attached.

Because Threads profiles are indexed by Google across both threads.net and threads.com, those addresses are publicly discoverable. The Threads Email Scraper finds them and extracts them at scale.

If you have ever typed site:threads.net "founder" "@gmail.com" into Google by hand, this is that Threads email extractor workflow automated, expanded across dozens of phrasings, deduplicated and exported.

The Threads Email Scraper never logs in, never opens threads.net, and never uses Meta's API. Every lead comes from publicly available Google search results.

---

Key Features of the Threads Email Scraper

Feature	What it means in practice
Dual-domain coverage	Queries target both threads.net and threads.com, so no half of the index is missed
Google-powered data collection	Queries use the site: operator, fetched through the Apify GOOGLE_SERP proxy
Query expansion	Each keyword x email-domain pair is searched as a base query, a quoted phrase, an intitle: query, and one variant per modifier
Domain filtering	Only emails on the domains you list are kept
Global deduplication	One row per unique address across every query and page
Obfuscation handling	Parses name [at] domain [dot] com, name (at) domain, name @ domain.com, zero-width characters and the full-width ＠
Junk filter	Rejects placeholders such as email@, yourname@, test@, xxx@ and single-character locals
Boundary-correct matching	@gmail.com does not match inside @gmail.company or @gmail.com.br
Handle parsing	@username in a Threads result title is turned into a canonical profile URL
Structural parser	Locates each result's <h3> and the smallest surrounding block instead of relying on Google's CSS class names
Fallback parser	A markup change degrades to "emails without account details" rather than zero results
Concurrency control	An asyncio worker pool runs queries in parallel with a shared stop signal
Retry logic	Up to 3 attempts per page, exponential backoff, fresh proxy session per request
Block detection	CAPTCHA, "unusual traffic" and consent pages are detected and retried, not treated as empty
Blocked-query requeue	Failed queries are retried once more at the end of the run
Resumable state	Input-keyed checkpoints in the key-value store, saved on PERSIST_STATE, MIGRATING and ABORTING
Streaming output	Every lead is pushed to the dataset immediately
Run summary	Pages fetched, blocked pages, retries and emails per page are logged

Dual-domain coverage is the detail that matters most here. Threads content lives under two hostnames, and a scraper that only checks one leaves leads on the table.

The rest of the feature set exists because email extraction from search results is messy. The Threads Email Scraper is built to degrade gracefully rather than fail silently.

---

How the Threads Email Scraper Works

The Threads Email Scraper is a search-engine crawler, not a Threads client.

1. Read input. Keywords, location, email domains, caps and concurrency.
2. Build queries. The site: operator is applied to the Threads domains alongside your keyword, the quoted email domain, and any location phrase.
3. Fetch search results. Asynchronous aiohttp requests through the Apify GOOGLE_SERP proxy.
4. Parse structurally. Each result block is located from its <h3> title outward.
5. Extract emails. A domain-filtered regex runs over the block text, with normalisation and the junk filter applied.
6. Deduplicate and push. New addresses go into a global set and straight to the Apify dataset.

Base queries run before expanded variants, so the strongest matches land in the dataset first.

Pagination continues per query until the page cap, the email cap, or a run of pages producing nothing new. That stop rule keeps the Threads Email Scraper from spending compute on exhausted queries.

---

What Data Does It Extract?

Each row the Threads Email Scraper produces is one email address plus the account context Google printed beside it.

For profile results that means a handle, a display name, the https://www.threads.net/@{username} profile URL, and the bio snippet the address came from.

For post results the title is a caption rather than a name, so fullName is left empty while accountName and the snippet still carry useful context. The Threads Email Scraper never guesses a name it cannot parse.

Every row also records the keyword that produced it and the exact Google query used, which makes campaign attribution and segmentation straightforward.

---

Input Fields

All input to the Threads Email Scraper is set in the Apify Console form or passed as JSON via the API.

Field	Type	Default	Description
keywords	array (required)	["founder", "creator"]	Search terms describing the Threads accounts you want
location	string	""	Optional location phrase added to every query
customDomains	array	["@gmail.com", "@yahoo.com"]	Only emails on these domains are kept; leading @ optional
maxEmails	integer (1-10000)	20	Stop once this many unique emails are collected
countryCode	string	""	Two-letter country code for the search proxy (US, GB, DE...)
expandQueries	boolean	true	Search each keyword x domain pair in several phrasings
queryModifiers	array	["email", "contact", "business inquiries", "collab", "booking", "dm"]	Extra words combined with each keyword when expansion is on
maxPagesPerQuery	integer (1-50)	30	Page cap per query
maxConcurrency	integer (1-20)	5	How many queries run in parallel

The default modifiers shipped with the Threads Email Scraper are tuned for Threads bios, where creators write "collab", "business inquiries" or "DM" beside their address.

---

Output Schema

Every dataset item from the Threads Email Scraper contains all fourteen fields below.

Field	Meaning
network	Platform name
keyword	The keyword that produced the lead
query	The exact Google query used
title	Raw result title
accountName	Account label Google prints (handle or display name)
fullName	Display name parsed from a profile-style title; empty for post captions
username	URL-safe handle when Threads exposes one; otherwise null
profileUrl	Canonical https://www.threads.net/@{username} URL when a handle is known; otherwise empty
url	Direct Threads link when exposed, else the profile URL
description	Bio or caption snippet, cleaned of labels and engagement counters
email	Lower-cased email address
emailDomain	The matched domain, e.g. @gmail.com
possiblyTruncated	true when Google's snippet ellipsis touched the email
foundAt	ISO 8601 UTC timestamp

Export the Threads Email Scraper dataset as JSON, CSV, Excel, XML or HTML, or read it over the Apify API.

The output schema is stable across runs, so you can build a repeatable ingestion pipeline on top of it.

---

Example Input and Output

A realistic Threads Email Scraper configuration for B2B and creator outreach.

Input

{
  "keywords": ["startup founder", "growth marketer", "newsletter writer"],
  "location": "Berlin",
  "customDomains": ["@gmail.com", "@proton.me"],
  "maxEmails": 200,
  "countryCode": "DE",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "business inquiries", "collab", "dm"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}

Output

{
  "network": "Threads",
  "keyword": "growth marketer",
  "query": "site:threads.net growth marketer \"@gmail.com\" \"Berlin\"",
  "title": "Jonas Weber (@jonasgrowth) on Threads",
  "accountName": "jonasgrowth",
  "fullName": "Jonas Weber",
  "username": "jonasgrowth",
  "profileUrl": "https://www.threads.net/@jonasgrowth",
  "url": "https://www.threads.net/@jonasgrowth",
  "description": "Growth marketing for B2B SaaS in Berlin. Threads every day. Business inquiries: jonas.weber.growth@gmail.com",
  "email": "jonas.weber.growth@gmail.com",
  "emailDomain": "@gmail.com",
  "possiblyTruncated": false,
  "foundAt": "2026-08-31T12:41:09Z"
}

---

How to Use the Threads Email Scraper

1. Open the Threads Email Scraper on Apify and click Try for free.
2. Replace the default keywords with your target niche, for example indie hacker, book author, fitness coach.
3. Set customDomains to the providers your audience actually uses.
4. Set maxEmails for the list size you need.
5. Optionally set location and countryCode to focus one market at a time.
6. Run it and export the dataset as CSV, or pull it via the Apify API.

Tip: Threads bios are short. Keywords describing a job title or niche outperform keywords describing content topics.

Tip: many Threads users mirror their Instagram bio verbatim. Running the Threads Email Scraper and the Instagram Email Scraper on the same keywords catches accounts that only one platform indexed.

Tip: lower maxConcurrency if blocked pages start appearing in the Threads Email Scraper run log; raise it when the log is clean.

---

Use Cases

Use case	How the Threads Email Scraper helps
Creator partnerships	Build a contact list of Threads creators before pitching a collab
B2B founder outreach	Reach startup founders who post about building in public
Newsletter cross-promotion	Find writers with an audience and a public contact address
PR and media outreach	Contact journalists and commentators active on Threads
Podcast guest sourcing	Identify subject-matter voices worth booking
SaaS lead generation	Prospect marketers, operators and agency owners by niche
Community building	Invite active posters in your topic into a private group
Recruiting	Reach specialists who describe their role in their Threads bio
CRM enrichment	Attach a contact channel to Threads handles you already track
Competitive research	Map which voices dominate a niche, with metadata for segmentation

Agencies commonly run the Threads Email Scraper once per client vertical and per city, keeping each dataset separate for clean reporting.

---

Why Use This Threads Email Scraper

Threads has no public contact directory and no way to filter people by "has an email in bio". Manual search stops working almost immediately.

Google caps a single query at roughly 300 results. Query expansion is the fix, and the Threads Email Scraper applies it methodically across base, quoted, intitle: and modifier variants.

Dual-domain targeting also matters. Covering only threads.net and ignoring threads.com would silently halve your coverage of the index.

The parser inside the Threads Email Scraper is stricter than a naive regex: obfuscated addresses are normalised, placeholders are rejected, and soft-wrapped fragments are collapsed rather than emitted as fake leads.

Leads stream to the dataset as they are found, so an aborted or migrated run still leaves usable data, and resumable state means a restart continues where it stopped.

Because Threads sits inside Meta's ecosystem, it pairs naturally with the Facebook Email Scraper and the Instagram Email Scraper.

For the same text-first audience elsewhere, try the X Email Scraper, the Bluesky Email Scraper and the Mastodon Email Scraper.

---

Limitations

Read these before your first Threads Email Scraper run. They are honest and structural.

• Publicly indexed emails only. If an address is not visible in Google's index, the Threads Email Scraper cannot find it. There is no login, no API and no private data.
• Google's result cap. A single query returns roughly 300 results maximum. Query expansion works around this but does not remove it.
• possiblyTruncated. true means Google's snippet ellipsis touched the address. Verify those rows before sending.
• Apify GOOGLE_SERP proxy required. The Actor cannot run without Apify proxy credentials.
• Free-plan cap. Free Apify plans are limited to 100 emails per run. Paid plans are uncapped.
• Handle availability. username and profileUrl populate only when Google exposes a handle. Some rows carry accountName and fullName with an empty username/profileUrl. That is a Google limitation, not a bug.
• Variable yield. Results depend on keywords, domains and location. No volume is guaranteed.

---

Related Actors

The same engine behind the Threads Email Scraper ships for every major network.

Actor	What it collects
Threads Email and Phone Number Scraper	Emails and phone numbers from Threads
Threads Phone Number Scraper	Public phone numbers from Threads
Behance Email Scraper	Public contact emails from Behance
Bigo Live Email Scraper	Public contact emails from Bigo Live
Bluesky Email Scraper	Public contact emails from Bluesky
Bumble Email Scraper	Public contact emails from Bumble
Clubhouse Email Scraper	Public contact emails from Clubhouse
Dailymotion Email Scraper	Public contact emails from Dailymotion
DeviantArt Email Scraper	Public contact emails from DeviantArt
Discord Email Scraper	Public contact emails from Discord
Dribbble Email Scraper	Public contact emails from Dribbble
Facebook Email Scraper	Public contact emails from Facebook
Goodreads Email Scraper	Public contact emails from Goodreads
Hinge Email Scraper	Public contact emails from Hinge
Instagram Email Scraper	Public contact emails from Instagram
KakaoTalk Email Scraper	Public contact emails from KakaoTalk
Kick Email Scraper	Public contact emails from Kick
Lemon8 Email Scraper	Public contact emails from Lemon8
Likee Email Scraper	Public contact emails from Likee
LINE Email Scraper	Public contact emails from LINE
LinkedIn Email Scraper	Public contact emails from LinkedIn
Mastodon Email Scraper	Public contact emails from Mastodon
Medium Email Scraper	Public contact emails from Medium
Mixcloud Email Scraper	Public contact emails from Mixcloud
Patreon Email Scraper	Public contact emails from Patreon
Pinterest Email Scraper	Public contact emails from Pinterest
Quora Email Scraper	Public contact emails from Quora
Reddit Email Scraper	Public contact emails from Reddit
Rumble Email Scraper	Public contact emails from Rumble
Snapchat Email Scraper	Public contact emails from Snapchat
SoundCloud Email Scraper	Public contact emails from SoundCloud
Substack Email Scraper	Public contact emails from Substack
Telegram Email Scraper	Public contact emails from Telegram
TikTok Email Scraper	Public contact emails from TikTok
Tinder Email Scraper	Public contact emails from Tinder
Tumblr Email Scraper	Public contact emails from Tumblr
Twitch Email Scraper	Public contact emails from Twitch
Vimeo Email Scraper	Public contact emails from Vimeo
VK Email Scraper	Public contact emails from VK
WeChat Email Scraper	Public contact emails from WeChat
Weibo Email Scraper	Public contact emails from Weibo
X Email Scraper	Public contact emails from X

FAQ

What is the Threads Email Scraper?

An Apify Actor that collects publicly indexed contact emails from Threads-related Google search results and returns them as structured data.

Does the Threads Email Scraper log into Threads or use Meta's API?

No. No login, no cookies, no browser, no API. Everything comes from public Google search results.

Where do the emails the Threads Email Scraper returns come from?

From indexed titles, snippets and site labels, usually Threads bios and post captions where the account published an address itself.

Does it cover both threads.net and threads.com?

Yes. Both domains are targeted, so the Threads Email Scraper does not miss half of Google's index.

Do I need a proxy to run the Threads Email Scraper?

Yes. It requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials.

Can I filter by email domain?

Yes, via customDomains. Matching is boundary-correct, so @gmail.com never matches @gmail.company.

How many emails can one Threads Email Scraper run return?

Free Apify plans are capped at 100 emails per run. Paid plans are uncapped, bounded by maxEmails and by how much Google has indexed.

Why is username sometimes null?

Google does not always print a handle. When it does not, you still get accountName, fullName and the snippet, but username and profileUrl stay empty.

What does possiblyTruncated: true mean?

Google's snippet ellipsis touched the address, so it may be cut off. Verify those rows before adding them to a campaign.

Are the emails verified or deliverable?

No. The Threads Email Scraper extracts addresses exactly as published. Verify deliverability yourself before a send.

Should I leave query expansion on?

Yes. Google caps a single query at roughly 300 results, and expansion is how the Actor reaches past that ceiling.

Can I resume an interrupted Threads Email Scraper run?

Yes. Progress is checkpointed in the key-value store, keyed by an input hash, and restored on restart or migration.

---

Leave a review

If the Threads Email Scraper saved you time, please leave a star rating and a short review on the Actor page.

Reviews are how other buyers judge whether a tool works, and they tell us which features to build next.

If something did not work, email neurodata.apify@gmail.com instead - bugs get fixed faster than they get complained about.

Support

Questions, a bug, or need a custom build of the Threads Email Scraper? Email neurodata.apify@gmail.com.