Telegram Info Scraper

🔎 Telegram Info Scraper for public profiles

Telegram Info Scraper gets public profile data from Telegram usernames, @handles, and t.me links. Paste users, bots, channels, groups, or supergroups, then export Telegram IDs, usernames, titles, bios, member counts, online counts, profile photos, verification flags, preview post dates, bot active-user counts, and source URLs.

Use this telegram info scraper when you need to check a list of Telegram entities before outreach, research, monitoring, moderation, brand protection, or CRM enrichment. You do not need a Telegram login, cookies, a phone number, or an API key. The Actor saves one clean dataset row for each public target Telegram exposes.

For a small first run, keep the prefilled targets. They cover a public channel, user, bot, and Telegram URL formats, so you can inspect the output before adding a larger list.

✅ What this Actor does

• Looks up public Telegram usernames, @handles, t.me URLs, and telegram.me URLs.
• Supports public users, bots, channels, groups, and supergroups when Telegram shows a public preview page.
• Saves one dataset row per successfully found public Telegram entity.
• Extracts source-native identity fields such as Telegram ID, primary username, public usernames, entity kind, title, first name, last name, and source URL when visible.
• Extracts public profile text, profile photo URL, member or subscriber count, online count, latest visible preview post date, preview post count, and visible metric text.
• Adds Telegram trust and type flags such as verified, scam, fake, restricted, bot, forum, slow mode, join request, join-to-send, participants hidden, and forwarding restriction fields when visible.
• Includes bot-specific fields such as visible active-user count and bot capability fields when Telegram exposes them.
• Skips invalid, private, missing, unavailable, or temporarily unreachable targets instead of saving placeholder failure rows.

📦 Data you can export

Each output item represents one public Telegram entity. Fields include:

• input, telegramId, username, usernames, entityKind, and sourceUrl
• title, firstName, lastName, bio, and profilePhotoUrl
• memberCount, onlineCount, adminCount, bannedCount, and kickedCount
• isVerified, isScam, isFake, isRestricted, isBot, and isForum
• hasLocation, location, hasSlowMode, slowModeSeconds, hasPaidMedia, and scheduled-message or forwarding fields
• isJoinRequestRequired, isJoinToSend, isParticipantsHidden, canViewMembers, and canViewStats
• linkedChatId, linkedMonoforumId, latestPostDate, previewPostCount, previewUrl, and visibleMetricText
• botActiveUsers, hasBotMainApp, hasBotAttachMenu, isBotBusiness, and botInlinePlaceholder

Fields can be null when Telegram does not show that value on the public profile or preview page.

🎯 Common use cases

• Check whether Telegram usernames, channels, groups, or bots exist.
• Build a clean Telegram channel metadata list for research or monitoring.
• Compare public member, subscriber, online, or bot active-user counts across communities.
• Flag verified, scam, fake, or restricted Telegram entities when those labels are visible.
• Enrich a CRM, lead list, influencer list, community list, or monitoring sheet with public Telegram profile data.
• Export public Telegram entity data to JSON, CSV, Excel, the Apify API, schedules, webhooks, or integrations.

🚀 How to run it

1. Open the Input tab.
2. Add one Telegram target per line in Telegram targets.
3. Use bare usernames, @handles, t.me URLs, or telegram.me URLs.
4. Start the Actor and open the dataset when the run finishes.

Input example:

{
	"targets": [
		"@telegram",
		"https://t.me/durov",
		"@BotFather",
		"telegram",
		"https://telegram.me/telegram"
	]
}

Private /c/ links and invite-only chats are not supported because they do not have a public Telegram preview page.

🧾 Output example

{
	"input": "@telegram",
	"telegramId": "1005640892",
	"username": "telegram",
	"usernames": ["telegram"],
	"entityKind": "channel",
	"title": "Telegram News",
	"firstName": null,
	"lastName": null,
	"bio": "The official Telegram on Telegram. Much recursion. Very Telegram. Wow.",
	"memberCount": 10323873,
	"onlineCount": null,
	"adminCount": null,
	"bannedCount": null,
	"kickedCount": null,
	"profilePhotoUrl": "https://cdn1.telesco.pe/file/example.jpg",
	"sourceUrl": "https://t.me/telegram",
	"isVerified": true,
	"isScam": false,
	"isFake": false,
	"isRestricted": false,
	"isBot": false,
	"isForum": null,
	"hasLocation": null,
	"hasScheduledMessages": null,
	"hasSlowMode": null,
	"slowModeSeconds": null,
	"hasPaidMedia": null,
	"isNoForwards": null,
	"isJoinRequestRequired": null,
	"isJoinToSend": null,
	"isParticipantsHidden": null,
	"canViewMembers": null,
	"canViewStats": null,
	"linkedChatId": null,
	"linkedMonoforumId": null,
	"location": null,
	"latestPostDate": "2026-03-02T17:33:34+00:00",
	"previewPostCount": 20,
	"previewUrl": "https://t.me/s/telegram",
	"visibleMetricText": "10.3M subscribers",
	"botActiveUsers": null,
	"hasBotMainApp": null,
	"hasBotAttachMenu": null,
	"isBotBusiness": null,
	"botInlinePlaceholder": null
}

Counts, flags, preview dates, and bot fields depend on what Telegram shows publicly at run time.

💳 Pricing

This Actor uses pay-per-event pricing. You are charged for each public Telegram entity that is successfully found and saved to the dataset. Invalid, private, missing, unavailable, or skipped targets are not saved as output rows.

⚠️ Limits and caveats

• The Actor extracts public data shown by Telegram profile and preview pages.
• It does not log in to Telegram or scrape private chats.
• It does not join groups, send messages, or collect private member lists.
• It does not find phone numbers, emails, or contacts from other websites.
• Some public profiles expose fewer fields than others, so fields can be null.
• Public Telegram pages can change what they show over time, so schedule important monitoring jobs with enough room for review.

❓ FAQ

🔐 Does Telegram Info Scraper need a Telegram account?

No. The Actor uses public Telegram pages. You do not need to provide a Telegram login, cookies, a phone number, or an API key.

👥 Can it scrape Telegram channel members?

No. This Actor gets public entity profile data, not private member lists. It can return a public member or subscriber count when Telegram displays one.

🚫 What happens when a username does not exist?

Missing, private, invalid, or unavailable targets are skipped and mentioned in the run logs. The dataset contains only found public Telegram entities.

🔎 Can I use this as a Telegram username scraper?

Yes, for public profile lookup. Add Telegram usernames or links and the Actor returns normalized usernames, entity type, titles, bios, counts, flags, photos, preview context, bot metrics, and source URLs when visible.

🕒 Can I schedule this Actor?

Yes. You can schedule runs on Apify and compare exported rows over time in your own sheet, warehouse, dashboard, or workflow.

📝 Changelog

• 1.0: Initial release.

🆘 Support

For issues, questions, or feature requests, file a ticket and I'll fix or implement it in less than 24h 🫡

🔗 Other actors

• Social Media Stats Checker ↗ - Check public profile stats across major social platforms in one dataset.
• Instagram Profile Stats Scraper ↗ - Export detailed public Instagram profile metrics for known profiles.
• Influencer Scraper ↗ - Find and compare public creator profiles on TikTok, Instagram, and YouTube.
• Twitter Scraper ↗ - Search public X/Twitter posts, profiles, and trending topics.
• Website Emails Scraper ↗ - Find public contact emails from websites you already care about.

Made with ❤️ by Maxime Dupré