Telegram Email Scraper

Telegram Email Scraper

Telegram Email Scraper

The Telegram Email Scraper is an Apify Actor that collects publicly indexed contact emails from Telegram channels, groups and public accounts. Give it keywords, get back a structured dataset of leads.

Telegram is where crypto projects, trading communities, SaaS founders, news channels and regional business groups publish. Admins routinely put a partnership or advertising address in the channel description.

Those t.me and telegram.me preview pages are indexed by Google, which is exactly where the Telegram Email Scraper looks. It never logs in, never joins a channel, and never uses Telegram's API or MTProto.

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

There is no message reading, no member list access and no private group data involved. The Telegram Email Scraper works only from publicly available search results.

Think of it as a focused crawler for contact discovery and lead generation, not a general-purpose Telegram scraper.

---

Key Features of the Telegram Email Scraper

Feature	What it means in practice
Dual-domain coverage	Queries target both t.me and telegram.me, 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
Telegram-tuned modifiers	Defaults are email, contact, admin, business, partnership — the words channel owners actually write
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	A Telegram handle resolves to its canonical https://t.me/{username} 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 targeting is the detail that matters here. Older Telegram links use telegram.me, and ignoring them would silently shrink your coverage of the index.

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

---

How the Telegram Email Scraper Works

The Telegram Email Scraper is a search-engine crawler. It never behaves like a Telegram client.

1. Read input. Keywords, location, email domains, caps and concurrency.
2. Build queries. The site: operator is applied to the Telegram 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 Telegram Email Scraper from burning compute on exhausted queries.

---

What Data Does It Extract?

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

That typically means the channel or account handle, a display name where the title is name-shaped, the https://t.me/{username} link, and the channel description snippet the address came from.

Where the title is a message preview rather than a name, fullName is left empty while accountName and the snippet still carry useful context.

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

This structured-data design is what separates the Telegram Email Scraper from a raw email list: you always know where a lead came from.

---

Input Fields

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

Field	Type	Default	Description
keywords	array (required)	["founder", "crypto"]	Search terms describing the Telegram 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", "admin", "business", "partnership"]	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 modifiers shipped with the Telegram Email Scraper matter more here than elsewhere. admin and partnership are the exact words channel owners use when they publish a business address.

---

Output Schema

Every dataset item from the Telegram 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 (channel handle or display name)
fullName	Display name parsed from a profile-style title; empty for message previews
username	URL-safe handle when Telegram exposes one; otherwise null
profileUrl	Canonical https://t.me/{username} URL when a handle is known; otherwise empty
url	Direct Telegram link when exposed, else the profile URL
description	Channel description or message snippet, cleaned of labels and 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 Telegram Email Scraper dataset as JSON, CSV, Excel, XML or HTML, or read it over the Apify API.

The output schema is identical on every run, so downstream CRM ingestion stays predictable.

---

Example Input and Output

A realistic Telegram Email Scraper configuration for crypto and fintech partnership outreach.

Input

{
  "keywords": ["crypto signals", "defi project", "trading community"],
  "location": "",
  "customDomains": ["@gmail.com", "@proton.me"],
  "maxEmails": 300,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "admin", "business", "partnership"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 6
}

Output

{
  "network": "Telegram",
  "keyword": "defi project",
  "query": "site:t.me defi project \"@gmail.com\" partnership",
  "title": "AlphaChain Research - Telegram",
  "accountName": "alphachain_research",
  "fullName": "AlphaChain Research",
  "username": "alphachain_research",
  "profileUrl": "https://t.me/alphachain_research",
  "url": "https://t.me/alphachain_research",
  "description": "DeFi research and on-chain analytics. Daily reports. Partnerships and ads: alphachain.partners@gmail.com",
  "email": "alphachain.partners@gmail.com",
  "emailDomain": "@gmail.com",
  "possiblyTruncated": false,
  "foundAt": "2026-08-31T14:12:33Z"
}

---

How to Use the Telegram Email Scraper

1. Open the Telegram Email Scraper on Apify and click Try for free.
2. Replace the default keywords with your target vertical, for example NFT community, forex signals, travel deals, job board.
3. Keep or edit queryModifiers. admin and partnership are the highest-yield phrases on Telegram.
4. Set customDomains to the providers your audience actually uses.
5. Set maxEmails for the list size you need, and countryCode if you want a regional bias.
6. Run it and export the dataset as CSV, or read it via the Apify API.

Tip: channel descriptions are short and repetitive. Vertical keywords like airdrop, signals or deals outperform abstract business terms.

Tip: for non-English regions, set countryCode and use local-language keywords when running the Telegram Email Scraper. Telegram's channel ecosystem is heavily regional.

Tip: if blocked pages appear in the Telegram Email Scraper run log, lower maxConcurrency and re-run. Blocked queries are requeued once automatically.

---

Use Cases

Use case	How the Telegram Email Scraper helps
Channel advertising sales	Find admins who publish an ads or partnership address
Crypto and Web3 partnerships	Reach project channels, research desks and trading communities
Influencer and KOL outreach	Contact Telegram-native voices in finance, gaming and news
Community-tool lead generation	Prospect admins to pitch moderation, analytics or bot products
Media buying	Build a list of channels available for sponsored placements
Regional market entry	Use location and countryCode to map a market's channel landscape
Recruiting	Reach job-board and hiring channel operators
PR distribution	Contact news and aggregator channels in your topic
CRM enrichment	Attach a contact channel to Telegram handles you already track
Competitive research	Map which channels dominate a vertical, with metadata for segmentation

Agencies often run the Telegram Email Scraper once per vertical and per region, keeping each dataset separate for clean reporting.

---

Why Use This Telegram Email Scraper

Telegram has no public directory of channels with contact details, and in-app search returns names, not emails. Manual prospecting stalls quickly.

Google caps a single query at roughly 300 results. The Telegram Email Scraper answers that with query expansion across base, quoted, intitle: and modifier variants for every keyword and domain pair.

Dual-domain coverage of t.me and telegram.me widens the crawl further, picking up older links that a single-domain scraper would never see.

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

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

Telegram communities overlap heavily with Discord and Reddit. Run this alongside the Discord Email Scraper and the Reddit Email Scraper for full community coverage.

For the crypto and founder audience specifically, the X Email Scraper and the Substack Email Scraper reach the same people in a different format.

In Asian markets, the LINE Email Scraper and the KakaoTalk Email Scraper cover the equivalent messaging ecosystems.

---

Limitations

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

• Publicly indexed emails only. If an address is not visible in Google's index, the Telegram Email Scraper cannot find it. There is no login, no API, no message access and no private group data.
• Google's result cap. A single query returns roughly 300 results maximum. Query expansion mitigates 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 Telegram Email Scraper 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 Telegram Email Scraper ships for every major network.

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

FAQ

What is the Telegram Email Scraper?

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

Does the Telegram Email Scraper read Telegram messages or member lists?

No. It has no access to messages, members or private groups. There is no login, no bot token, no MTProto and no Telegram API use.

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

From indexed titles, snippets and site labels on public t.me and telegram.me pages, usually channel descriptions where an admin published an address.

Does the Telegram Email Scraper cover both t.me and telegram.me?

Yes. Both domains are targeted, so older links are not missed.

Do I need a proxy to run the Telegram 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 Telegram 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 Telegram Email Scraper extracts addresses exactly as published. Verify deliverability yourself before a send.

Which query modifiers work best on Telegram?

admin and partnership typically outperform generic terms, because those are the words channel owners write next to a business address.

Can I resume an interrupted Telegram 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 Telegram 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 Telegram Email Scraper? Email neurodata.apify@gmail.com.