Discord Email Scraper

Discord Email Scraper — public contact emails from Discord server listings

The Discord Email Scraper is an Apify Actor that finds publicly indexed contact emails attached to Discord servers, communities and the people who run them. Keywords in, structured leads out.

Read this first. Discord has no public user profile pages. Results come from server listings and invite pages on discord.com, discord.gg and disboard.org, so volume is limited compared with platforms that index millions of profiles.

That constraint is also the opportunity. The emails the Discord Email Scraper does surface usually belong to server owners, community managers and partnership contacts — exactly the people a discord server owner contact search is looking for.

If you have ever hand-run site:disboard.org "gmail.com" crypto and pasted the hits into a sheet, the Discord Email Scraper is that workflow automated, deduplicated and exported as JSON or CSV.

The Discord Email Scraper never logs into Discord, never uses the Discord API, and never joins a server. Every field comes from publicly available Google search results.

Who it is for

• Web3, gaming and SaaS teams doing community partnership outreach
• Agencies looking for a discord community email finder that returns structured data
• Sponsorship teams contacting server owners about placements
• Recruiters hiring community managers and moderators
• Researchers mapping niche communities and their public contacts

---

Key features

The Discord Email Scraper is a Google SERP crawler with a hardened email parser. Everything in the Discord Email Scraper feature list below is implemented in code — nothing here is aspirational.

Feature	What it does
Multi-domain site: search	Queries discord.com, discord.gg and disboard.org in one run
Query expansion	Base, quoted and intitle: variants plus one query per modifier
Query modifiers	Defaults tuned for Discord: email, contact, business, partnership, sponsor
Domain filtering	Keeps only emails on the mailbox domains you list, e.g. @gmail.com
Global deduplication	One row per unique email across every query and every page
Email normalisation	Understands name [at] domain [dot] com, (at), name @ domain.com, ＠ and zero-width characters
Junk filter	Rejects placeholders such as email@, yourname@, test@, xxx@
Boundary-correct matching	@gmail.com will not match inside @gmail.company or @gmail.com.br
Concurrency	An asyncio worker pool runs several queries in parallel
Retry logic	Up to 3 attempts per page with exponential backoff and a fresh proxy session
Block detection	CAPTCHA, "unusual traffic" and consent pages are detected and retried, not counted as empty
Resumable state	Run state lives in the key-value store and survives migration
Fallback parser	If Google's markup changes, output degrades to emails-without-details, not zero rows
Streaming dataset	Each lead is pushed to the Apify dataset the moment it is found

---

How the Discord Email Scraper works

The Discord Email Scraper uses no browser, no JavaScript rendering, no authentication and no cookies. The pipeline is deliberately simple.

1. Read the input. Keywords, location, email domains and limits are loaded from the Actor input.

2. Build the queries. Each keyword is combined with each email domain and a site: operator per Discord domain, for example:

site:disboard.org community manager "@gmail.com" partnership

3. Expand the query set. With expandQueries on, every keyword × domain pair also runs quoted, as intitle:, and once per modifier. Base queries run first, so the strongest search results land early.

4. Fetch through the proxy. Pages are requested asynchronously with aiohttp through the Apify GOOGLE_SERP proxy, paginating up to maxPagesPerQuery.

5. Parse structurally. The parser locates each <h3> title and walks up to the smallest surrounding block. It does not rely on Google's CSS class names.

6. Extract and clean. A domain-filtered regex pulls emails from the block text. Soft-wrap repair discards a hit that is only the tail of another address in the same block.

7. Deduplicate and push. Emails are deduplicated globally and written straight to the dataset. The run stops once maxEmails unique addresses exist.

Blocked or failed queries are re-queued once at the end of the run, so a temporary block does not quietly cost you leads.

---

What data does the Discord Email Scraper extract?

Every dataset item the Discord Email Scraper produces has the same 14 fields — flat structured data, no nesting, ready for a CRM import or a spreadsheet.

On Discord, accountName is usually the server or listing name rather than a person. fullName is populated when the title parses as a profile-style name and is often empty for server listings.

Because the Discord Email Scraper stores the originating keyword and query on every row, you can see which searches actually produced leads and retire the ones that did not.

---

Input fields

The input schema is small on purpose. These nine fields are the entire configuration surface of the Discord Email Scraper.

Field	Type	Default	Meaning
keywords	array (required)	["founder", "community manager"]	Search terms: niche, role or community topic
location	string	""	Optional location phrase added to every query
customDomains	array	["@gmail.com","@yahoo.com"]	Only emails on these domains are kept; the @ is optional
maxEmails	integer 1–10000	20	Stop after this many unique emails
countryCode	string	""	Two-letter country for the search proxy (US, GB, DE…)
expandQueries	boolean	true	Search each keyword × domain in several phrasings
queryModifiers	array	["email","contact","business","partnership","sponsor"]	Extra words combined with each keyword when expansion is on
maxPagesPerQuery	integer 1–50	30	Pagination cap per query
maxConcurrency	integer 1–20	5	Parallel queries

Because Discord's indexed surface is small, keyword breadth matters more here than on other platforms. Run several topic keywords rather than one.

---

Output fields and dataset structure

The output schema of the Discord Email Scraper is fixed. Every row carries all 14 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 — on Discord usually a server or listing name
fullName	Display name parsed from a profile-style title; often empty for server listings
username	URL-safe handle when one is exposed (an invite code); otherwise null
profileUrl	Canonical invite URL when a handle is known; otherwise empty
url	Direct Discord link when exposed, else the profile URL
description	Listing or bio 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 as JSON, CSV, Excel or XML from the Apify console, or read the dataset through the API.

---

How to use the Discord Email Scraper

Setup takes about a minute.

1. Open the Discord Email Scraper on Apify and click Try for free.
2. Replace the default keywords with your community topic — NFT community, indie game dev, trading server.
3. Set customDomains. @gmail.com alone is the highest-yield single choice for community operators.
4. Optionally set location and countryCode to bias results geographically.
5. Raise maxEmails, then press Start.
6. Watch the log — it reports pages fetched, blocked pages, retries and emails per page.
7. Export the dataset, or schedule the Discord Email Scraper to re-run and append fresh leads.

Tip: because of the limited indexed surface, treat Discord as a supplement. Run it alongside the Telegram Email Scraper and Reddit Email Scraper to cover the same community niches from three angles.

---

Use cases and lead generation workflows

Teams reach for the Discord Email Scraper when contact discovery inside community-led niches is the bottleneck. The Discord Email Scraper works as a one-off list build or as a scheduled data collection job.

Use case	How the Discord Email Scraper helps
Community partnership outreach	Find servers in a niche that publish a partnership or business email
Sponsorship prospecting	Identify server owners advertising sponsor contact details
Web3 and gaming BD	Build a target list of communities around a token, game or genre
Recruiting community managers	Surface people describing themselves as community managers with a public email
Tool and bot vendors	Contact discovery among server operators who might adopt your product
Market research	Collect structured data on how communities in a niche position themselves
CRM enrichment	Attach server names and invite URLs to existing records
Event and AMA booking	Reach community owners for cross-promotion

---

Why choose this Actor

It is honest about its source and its ceiling. Discord has no public profiles; this README says so up front rather than promising millions of leads.

It survives Google layout changes. Structural parsing plus a whole-page fallback means a markup change degrades quality rather than breaking the run.

It covers three domains in one job. The Discord Email Scraper searches discord.com, discord.gg and disboard.org together, which matters a lot when the indexed surface is thin.

It is built for volume without waste. Global deduplication, a shared stop signal on maxEmails and streaming dataset writes mean the Discord Email Scraper collects what you asked for and then stops.

One schema across 40+ platforms. Learn the Discord Email Scraper once and every sibling Actor behaves identically — including the X Email Scraper for the same founders on another network.

---

Limitations

Read this before running the Discord Email Scraper. These are real constraints, not boilerplate.

• No public user profiles. Discord does not publish user profile pages. The Discord Email Scraper works from server listings and invite pages, so expect noticeably lower volume than platforms with indexed profiles.
• Public index only. Only emails visible in Google's index can be found. Anything shared inside a server is invisible to this Actor.
• ~300 results per query. Google caps a single query at roughly 300 results, which is precisely why expandQueries exists — leave it on.
• Truncated emails. possiblyTruncated: true means Google's snippet ellipsis touched the address. Verify those rows before sending.
• Handle availability. username and profileUrl are only populated when a handle appears in the result. Where Google shows only a display or server name, you still get accountName but an empty handle. This is a Google limitation, not a bug.
• Proxy requirement. The Actor requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials.
• Free-plan cap. Free Apify plans are capped at 100 emails per run. Paid plans are uncapped.
• No volume guarantee. Results from the Discord Email Scraper vary with keywords, domains and location.

Use the output responsibly and in line with GDPR, CAN-SPAM and your local rules on unsolicited email.

---

Related Actors

The Discord Email Scraper shares its crawler, parser and output schema with every Actor below. Swap the platform, keep the workflow.

Actor	What it collects
Discord Email and Phone Number Scraper	Emails and phone numbers from Discord
Discord Phone Number Scraper	Public phone numbers from Discord
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
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
Threads Email Scraper	Public contact emails from Threads
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

Example: JSON input and dataset output

A realistic Discord Email Scraper input targeting indie game communities:

{
  "keywords": ["indie game community", "community manager"],
  "location": "",
  "customDomains": ["@gmail.com", "@protonmail.com"],
  "maxEmails": 150,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "business", "partnership", "sponsor"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}

And a single dataset item the Discord Email Scraper returns:

{
  "network": "Discord",
  "keyword": "indie game community",
  "query": "site:disboard.org indie game community \"@gmail.com\" partnership",
  "title": "Pixel Forge Devs - Discord Server",
  "accountName": "Pixel Forge Devs",
  "fullName": "",
  "username": "pixelforgedevs",
  "profileUrl": "https://discord.gg/pixelforgedevs",
  "url": "https://discord.gg/pixelforgedevs",
  "description": "Indie game dev community, 12k members. Partnerships and sponsor enquiries: pixelforge.partners@gmail.com",
  "email": "pixelforge.partners@gmail.com",
  "emailDomain": "@gmail.com",
  "possiblyTruncated": false,
  "foundAt": "2026-08-31T10:02:47Z"
}

---

FAQ about the Discord Email Scraper

Does the Discord Email Scraper log into Discord or join servers?

No. It never logs in, never uses the Discord API and never joins a server. All data comes from publicly indexed Google search results.

Why does Discord return fewer results than other platforms?

Because Discord has no public user profile pages. The Discord Email Scraper works from server listings and invite pages only, so the indexed surface is much smaller.

Where exactly do the emails come from?

From titles, snippets and site labels Google prints for discord.com, discord.gg and disboard.org pages — typically server descriptions listing a partnership or business contact.

Can it read messages inside a server?

No. Nothing posted inside a Discord server is visible to this Actor. If it is not in Google's public index, the Discord Email Scraper cannot see it.

Why do some rows have an empty username and profileUrl?

Because Google showed only a display or server name for that result. You still get accountName and the email. It is a Google limitation, not a bug.

What does possiblyTruncated: true mean?

Google's snippet ellipsis touched the email, so it may be cut off. Verify those addresses before sending.

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

Yes. The Discord Email Scraper requires the Apify GOOGLE_SERP proxy and cannot run without Apify proxy credentials.

Is the output ready for a CRM?

Yes. The Discord Email Scraper writes flat structured data with 14 fixed fields, exportable as JSON, CSV, Excel or XML.

How many emails can I get on a free plan?

Free Apify plans are capped at 100 emails per run. Paid plans are uncapped.

Should I leave expandQueries on?

Yes. Google caps a single query at roughly 300 results, and expansion spreads the Discord Email Scraper across base, quoted, intitle: and modifier variants.

How do I improve yield on a discord server owner contact search?

Use several topic keywords, add more mailbox domains, raise maxPagesPerQuery, and combine the run with a Telegram or Reddit job covering the same niche.

Can I schedule the Discord Email Scraper?

Yes. Schedule it on Apify and it appends new leads on each run. Run state is resumable and survives platform migrations.

Is this affiliated with Discord?

No. The Discord Email Scraper is independent and is not affiliated with, endorsed by or officially supported by Discord.

---

Leave a review

If the Discord 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 Discord Email Scraper? Email neurodata.apify@gmail.com.