Telegram Channel Monitor: New Messages, Keywords, Webhooks

Read and monitor public Telegram channels with no API key, no bot token and no phone number. Run it once to pull history, or schedule it in monitor mode to get only the messages posted since your previous run, filtered by keyword or regex, and pushed to your webhook.

Why this one

Most Telegram actors are one-shot scrapers: every run hands you the same messages again, and you deduplicate them yourself. This one is built for scheduled monitoring:

• Monitor mode remembers where it stopped. It stores the last message ID per channel and returns only what is genuinely new. A scheduled run on a quiet channel costs almost nothing because there is nothing to return.
• Filters before you pay attention. Keywords (any or all) plus an optional regex, matched against the message text, the link-preview title and description, and any links in the message.
• Webhook delivery. Matched messages are POSTed as JSON, so a signal channel can drive your own bot, Discord relay or dashboard.
• No credentials, for you or your customers. It reads the same public preview page any visitor sees, so there is nothing to register and nothing to leak.

What you get per message

{
  "channel": "whale_alert",
  "channel_title": "Whale Alert",
  "subscribers": 13600,
  "message_id": 11527,
  "url": "https://t.me/whale_alert/11527",
  "datetime": "2026-07-29T08:19:07+00:00",
  "text": "6,500,000 #USDT (6,529,776 USD) transferred from unknown wallet to #Binance",
  "views": 139000,
  "forwarded_from": null,
  "is_forward": false,
  "is_reply": false,
  "edited": false,
  "has_photo": false,
  "has_video": false,
  "photo_urls": [],
  "poll": null,
  "link_preview": { "url": "https://...", "site": "...", "title": "...", "description": "..." },
  "urls": ["https://..."],
  "is_new": true
}

Channel metadata (title, description, subscriber count, media counters, avatar) is stored in the key-value store under channels.

Typical setups

Signal or news alerting channels: ["mychannel1","mychannel2"], monitorMode: true, keywords: ["BTC","ETH"], plus your webhookUrl. Schedule every 5 or 10 minutes.

Keyword watch across many channels channels: [ ... 20 channels ... ], monitorMode: true, regex: "(listing|airdrop|partnership)".

One-off history pull for analysis channels: ["durov"], maxMessagesPerChannel: 1000, minDate: "2026-01-01", monitorMode: false.

Input

Field	Default	Meaning
channels	["durov"]	usernames, @usernames or t.me links
maxMessagesPerChannel	50	how far back to page per channel
monitorMode	false	return only messages new since the last run
keywords	none	case-insensitive terms to match
requireAllKeywords	false	on: all keywords must appear
regex	none	advanced pattern filter
minDate	none	stop paging past this date (YYYY-MM-DD)
includeHtml	false	also return original message HTML
webhookUrl	none	POST matched messages as JSON
concurrency	3	channels read in parallel

Honest limitations

• Only public channels with the web preview enabled are readable. Private channels, groups and channels that disabled the preview cannot be read by anyone without credentials, including this actor. Unreadable channels are reported in the log rather than failing the run.
• View counts and subscriber numbers are the rounded values Telegram itself displays (for example 3.49M), not exact integers.
• Photo URLs are the preview images from the public page; large media files and documents are reported as flags rather than downloaded.
• Deleted or edited messages reflect the current state of the page, not a history of edits.

Keywords

telegram scraper, telegram channel scraper, telegram monitor, telegram messages api, telegram channel messages, telegram keyword alerts, telegram webhook, monitor telegram channel, telegram signals, telegram news monitoring, no api key telegram