# ✈️ Telegram Channel Messages & Incremental Monitor (`snuggly_beanie_970/telegram-public-channel-monitor`) Actor

✈️ Scrape public Telegram channel profiles and messages without an account. 📊 Export views, reactions, forwards, media flags, links, mentions and hashtags. ✅ Message-ID checkpoints prevent rebilling old posts.

- **URL**: https://apify.com/snuggly\_beanie\_970/telegram-public-channel-monitor.md
- **Developed by:** [Ilia](https://apify.com/snuggly_beanie_970) (community)
- **Categories:** Social media, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 telegram messages

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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 Channels, Posts, Media & Reactions

Extract public Telegram channel profiles and messages from Telegram's web preview. No Telegram account, phone number, bot token or cookies required.

### Designed for recurring monitoring

Each message has a stable `channelUsername/messageId` identity. Pass the previous highest ID through `afterMessageIds` and the Actor stops at that checkpoint instead of charging for old rows again. Overlapping preview pages are deduplicated before billing. `maxMessagesPerChannel` is a hard paid-row cap.

### 📤 What you get

- channel title, description, avatar, verification, subscribers, and public photo/video/link counters;
- stable message IDs, canonical URLs, ISO timestamps, edited state, author signature, text, and original HTML;
- parsed and raw view counts plus individual reactions and total reaction count;
- forwarded-message source and context;
- direct public photo and video CDN URLs, combined media list, media flags, and video duration label;
- structured link previews with destination, site, title, description, and image;
- extracted links, mentions, and hashtags;
- date and keyword filters, per-channel result caps, deduplication, and reusable incremental checkpoints.

### 🚀 Popular use cases

- news and announcement monitoring;
- competitor and campaign watchlists;
- view/reaction trend snapshots;
- media archiving, link-preview, mention and hashtag extraction;
- scheduled ingestion into Slack, Sheets, databases and AI pipelines.

### ⚙️ Example input

```json
{"channels":["durov","telegram"],"maxMessagesPerChannel":100,"includeChannelInfo":true,"afterMessageIds":{},"keyword":""}
```

### 📥 Complete input reference

| Field | Type | Default | Purpose |
|---|---|---:|---|
| `channels` | array | `["telegram"]` | Usernames, @handles, or public t.me channel URLs. Private invite links are rejected. |
| `maxMessagesPerChannel` | integer | `100` | Hard per-channel cap on paid message rows. |
| `afterMessageIds` | object | `{}` | Optional channel-to-message-ID map. Only messages newer than each checkpoint are emitted. |
| `dateFrom` | string | — | Optional inclusive YYYY-MM-DD date filter. |
| `dateTo` | string | — | Optional inclusive YYYY-MM-DD date filter. |
| `keyword` | string | `""` | Optional case-insensitive text filter applied after retrieval. |
| `includeChannelInfo` | boolean | `true` | Emit one channel profile row for every accessible channel. |
| `requestDelayMs` | integer | `350` | Polite delay between Telegram page requests. |

### 📤 Complete output reference

The default dataset is exportable as JSON, CSV, Excel, XML or RSS. Fields remain stable for scheduled runs and API integrations.

| Field | Type |
|---|---|
| `recordType` | string |
| `channelUsername` | string |
| `channelTitle` | string / null |
| `channelUrl` | string |
| `subscriberCount` | integer / null |
| `subscriberCountRaw` | string / null |
| `channelDescription` | string / null |
| `channelAvatarUrl` | string / null |
| `photoCount` | integer / null |
| `videoCount` | integer / null |
| `linkCount` | integer / null |
| `verified` | boolean |
| `messageId` | integer / null |
| `messageUrl` | string / null |
| `postedAt` | string / null |
| `edited` | boolean |
| `text` | string / null |
| `textHtml` | string / null |
| `views` | integer / null |
| `viewsRaw` | string / null |
| `reactions` | array |
| `reactionCount` | integer |
| `isForwarded` | boolean |
| `forwardedFrom` | string / null |
| `hasPhoto` | boolean |
| `hasVideo` | boolean |
| `hasDocument` | boolean |
| `authorSignature` | string / null |
| `photoUrls` | array |
| `videoUrls` | array |
| `mediaUrls` | array |
| `videoDurationText` | string / null |
| `linkPreview` | object / null |
| `links` | array |
| `mentions` | array |
| `hashtags` | array |
| `scrapedAt` | string |

### 🔌 API & integrations

Run this Actor from the Apify Console, API, CLI, MCP, Make, Zapier or n8n. Replace the Actor identifier and token in this template:

```bash
curl -X POST "https://api.apify.com/v2/acts/telegram-public-channel-monitor/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'
```

Results are stored in the run's default dataset and can be forwarded with Apify webhooks or scheduled Tasks.

### 🔎 Search keywords

Telegram Channels, Posts, Media & Reactions — No Login, telegram, channels, posts, media, reactions, login, public, channel, monitor, Apify Actor, scraper API, structured data, scheduled monitor, automation.

### 💰 Pricing

Billing is tied to successfully delivered result events. Empty, filtered, duplicate or failed records are not charged as results. Open the **Pricing** tab for the current per-event rate before starting a run, and use Apify's maximum-charge control to enforce a hard budget.

# Actor input Schema

## `channels` (type: `array`):

Usernames, @handles, or public t.me channel URLs. Private invite links are rejected.

## `maxMessagesPerChannel` (type: `integer`):

Hard per-channel cap on paid message rows.

## `afterMessageIds` (type: `object`):

Optional channel-to-message-ID map. Only messages newer than each checkpoint are emitted.

## `dateFrom` (type: `string`):

Optional inclusive YYYY-MM-DD date filter.

## `dateTo` (type: `string`):

Optional inclusive YYYY-MM-DD date filter.

## `keyword` (type: `string`):

Optional case-insensitive text filter applied after retrieval.

## `includeChannelInfo` (type: `boolean`):

Emit one channel profile row for every accessible channel.

## `requestDelayMs` (type: `integer`):

Polite delay between Telegram page requests.

## Actor input object example

```json
{
  "channels": [
    "telegram"
  ],
  "maxMessagesPerChannel": 100,
  "afterMessageIds": {},
  "keyword": "",
  "includeChannelInfo": true,
  "requestDelayMs": 350
}
```

# Actor output Schema

## `results` (type: `string`):

Default dataset containing channel and message records.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("snuggly_beanie_970/telegram-public-channel-monitor").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("snuggly_beanie_970/telegram-public-channel-monitor").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 '{}' |
apify call snuggly_beanie_970/telegram-public-channel-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,snuggly_beanie_970/telegram-public-channel-monitor"
        }
    }
}

```

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/vJGqpDtZ5oVWeifrh/builds/5EgPsVpAac50Hwdpx/openapi.json