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

✈️ Telegram Email Scraper extracts public channel and group owner emails by keyword and location. 🔓 Domain filtering, hidden-address decoding and dedup. 📤 Export Telegram leads to CSV, JSON or Excel for community growth.

- **URL**: https://apify.com/scrapido/telegram-email-scraper.md
- **Developed by:** [Scrapido](https://apify.com/scrapido) (community)
- **Categories:** Lead generation, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 0.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

### Telegram Email Scraper 🔍

**Telegram Email Scraper** helps you automatically extract emails from Telegram using keywords you choose—solving the time-consuming problem of manual email hunting for marketers, recruiters, and sales pros. It’s also a practical **telegram email extractor** for faster **extract emails from telegram** and scalable **telegram lead generation** when you need results quickly.

***

### 🌟 Key Features of Telegram Email Scraper

| Feature | Benefit |
|---|---|
| ✅ **Targeted Keyword Search** | Reach the exact Telegram audience you need with keyword-driven discovery |
| ✅ **Location Filtering** | Add `location` to focus results on a specific city, region, or country |
| ✅ **Custom Domain Filter** | Extract only `@gmail.com`-style (or any domains you provide) email addresses |
| ✅ **Max Emails Control** | Set `maxEmails` to cap the total emails collected per run |
| ✅ **Bulk Export Ready** | Results land in your Apify dataset for easy JSON/CSV export workflows |
| ✅ **Real-Time Saving** | Each discovered result is pushed and saved incrementally as the run progresses |
| ✅ **Deduplication of Emails** | Avoid repeated emails by tracking `seen_emails` during the run |

Related SEO angles you’ll see in marketing teams include telegram user email scraper and OSINT email extraction—this actor is built for that kind of practical workflow.

***

### 📥 Input — Telegram Email Scraper Parameters

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

| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| `keywords` | Array | ✅ Yes | — | Search terms to find relevant Telegram profiles and contact mentions for email harvesting from telegram |
| `location` | String | No | `""` | Location to filter search results (useful for telegram channel email scraping with a regional focus) |
| `customDomains` | Array | No | `[]` | List of custom email domains to filter extracted emails (e.g., `@gmail.com`, `@yahoo.com`) |
| `maxEmails` | Integer | No | `20` | Cap on total emails to collect per run (helps control scraping time while you do bulk email scraping) |

Pro tip: for best results with a telegram email extractor, use focused keywords plus the email domains you actually want.

***

### 📤 Output — What Telegram Email Scraper Returns

The actor saves each result as a JSON record in your Apify dataset.

```json
{
  "keyword": "founder",
  "title": "Founder @GrowthOps — Telegram community",
  "description": "We connect teams with operators. Contact us for collaborations. hello@growthops.tools",
  "url": "https://t.me/growthops",
  "email": "hello@growthops.tools"
}
```

| Field | Type | Description |
|---|---|---|
| `keyword` | String | The search term that surfaced this result (helps track your telegram email finder queries) |
| `title` | String | Telegram profile name or business title shown for the lead |
| `description` | String | Bio or profile summary content where the email was found |
| `url` | String | Direct link to the Telegram profile/channel for this lead |
| `email` | String | Email address extracted from the Telegram content for your outreach list |

This dataset is tailored for telegram bot for email collection workflows, where you want clean, structured telegram contacts ready for analysis.

***

### 💻 How to Use Telegram Email Scraper — Step-by-Step

1. **Open the Actor** — Find Telegram Email Scraper in the Apify Store: https://apify.com/store
2. **Enter Keywords** — Add job titles, roles, or themes you want to extract emails from telegram for
3. **Set Location (optional)** — Use `location` to narrow where leads are likely to be found
4. **Filter by Domain (optional)** — Provide `customDomains` like `@gmail.com` or `@yahoo.com` to focus harvesting
5. **Set Max Emails** — Use `maxEmails` to cap results and control run duration
6. **Run the Actor** — Start the run and monitor logs as it collects leads
7. **Export Results** — Download from your Apify dataset and import into your CRM or outreach tooling

*No coding required. Results ready in minutes.*

***

### 💡 Best Use Cases for Telegram Email Scraper

- 🎯 **Lead Generation** — Build a telegram lead generation list for outreach and partnerships
- 📣 **Email Marketing** — Enrich campaigns with telegram channel email scraping contacts
- 🤝 **Recruitment** — Find professionals using data mining telegram contacts workflows
- 🔬 **Market Research** — Identify industry voices and community operators via telegram user email scraper outputs
- 📊 **CRM Enrichment** — Improve records with extracted email validation and deduplication-ready fields

If you’re doing OSINT email extraction or regex email detection-based pipelines, this actor’s structured output fits neatly into your process.

***

### Disclaimer

Telegram Email Scraper only accesses publicly available data. It does not retrieve private profiles, authenticated content, or password-protected pages. You are responsible for ensuring your use complies with applicable laws and platform policies, including anti-spam rules and privacy regulations such as GDPR and CCPA. This tool is intended for legitimate purposes like lead generation and research, and for automated compliance checks in your own workflows. For data-removal requests, contact 📧 <scrapidocontact@gmail.com>.

***

### 🆘 Support & Feedback

Have a question or found an issue with the Telegram Email Scraper? We're here to help.

- 🐞 **Bug Reports:** Open a ticket in the repository's Issues section
- ✨ **Custom Solutions & Feature Requests:** Reach out to our team
- 📧 **Email:** <scrapidocontact@gmail.com>

Your feedback shapes the roadmap — we read every message.

### 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": [
    "channel admin",
    "crypto"
  ],
  "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": [
        "channel admin",
        "crypto"
    ],
    "customDomains": [],
    "emailTypes": [
        "Personal",
        "Business"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapido/telegram-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": [
        "channel admin",
        "crypto",
    ],
    "customDomains": [],
    "emailTypes": [
        "Personal",
        "Business",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("scrapido/telegram-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": [
    "channel admin",
    "crypto"
  ],
  "customDomains": [],
  "emailTypes": [
    "Personal",
    "Business"
  ]
}' |
apify call scrapido/telegram-email-scraper --silent --output-dataset

```

## MCP server setup

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