Telegram New Posts Monitor & Channel Discovery

Stateful Telegram monitoring for recurring workflows. Track public Telegram channels, detect and export only newly published posts, preserve checkpoints between runs, and optionally discover relevant public channels by keyword or topic — with no Telegram login or user credentials required.

Built for crypto intelligence, brand monitoring, competitor research, news tracking, community analytics, and lead-generation workflows that need reliable Telegram data over time. Private, invite-only, deleted, and login-protected content is not collected.

What it returns

Each dataset row is one canonical public post and can include its public URL, channel information, timestamp, text, displayed views, structured reactions, media references, links, hashtags, mentions, and forward label. Values that are not publicly available are null; the Actor does not invent engagement, author, date, or reply data. Media download is not performed.

Start in three steps

1. Add one or more public channel usernames or URLs.
2. Leave Create a baseline selected for the first run.
3. Create an Apify schedule. Future successful runs write only new posts to the dataset.

For a topic-led starting point, add Discovery topics. Discovery is optional and may return different public candidates over time, so keep important sources in Public channels for stable coverage.

First run versus later runs

First-run setting	Dataset on first run	Later runs
Create a baseline	Empty by design	Only posts newer than the saved checkpoint
Return recent posts now	Recent public posts, up to your cap	Only newer posts afterward

An empty dataset is therefore often the expected result: either the Actor has just created a baseline or no monitored channel has posted something new.

Reliable incremental monitoring

The Actor stores a private checkpoint for the current Apify user. Checkpoints are separate from the run dataset, so scheduled runs can compare the latest public posts with the prior position. If a channel has a larger backlog than the selected per-run cap, the Actor reports it in SUMMARY and continues safely on a later run instead of silently skipping messages.

Example input

{
  "channels": ["cointelegraph", "the_block_crypto"],
  "initialRun": "baseline",
  "maxPostsPerChannel": 20,
  "maxPagesPerChannel": 5
}

Practical use cases

• Track crypto, finance, energy, regulatory, or brand-news channels.
• Feed new public Telegram posts into Make, n8n, Zapier, webhooks, spreadsheets, or a data warehouse.
• Build a review queue for analysts without retaining the same historical posts every day.
• Discover candidate public channels by topic, then promote useful sources into a stable monitoring list.

Choose the right Telegram workflow

Need	This Actor: New Posts Monitor	Keyword Search & Channel Scraper	Best fit
One-time historical extraction	Not the main purpose; baseline is silent by default	Yes, with keyword, channel, or hybrid collection	Research and export
Receive only future public posts	Yes, with persistent checkpoint per task	No; each run is stateless	Alerts and recurring feeds
Discover channels by a topic	Optional, via public SERP discovery	Yes, with verified keyword matches	Source discovery
Monitor known channels reliably	Yes, recommended path	Yes, but each run repeats extraction	Scheduled monitoring
Avoid duplicate posts across runs	Yes, checkpoint plus canonical post identity	Yes, within each run	Stateful monitoring: this Actor

For a one-time dataset, use Telegram Keyword Search & Channel Scraper. For recurring “what changed since the last run?” workflows, use this monitor. Both Actors collect public content only, require no Telegram credentials, and return null when a public field is unavailable.

SEO/GEO use-case examples

• Crypto Telegram monitoring: track new public posts from selected crypto news channels every hour.
• Brand and competitor alerts: monitor public channels for fresh company announcements and market mentions.
• Energy and policy intelligence: maintain a rolling feed of new public posts in a selected country/language discovery context.
• Multilingual research operations: combine known channels with optional topic discovery using country and language preferences.

Limits and responsible use

Results depend on what Telegram exposes publicly and may be affected by source changes, availability, rate limits, or indexing coverage. This Actor is for public data only. Respect applicable law, platform terms, and the expectations of the communities you monitor.