# Telegram Channel Scraper & Monitor (`lyklo/telegram-channel-scraper`) Actor

Gets posts from public Telegram channels with views, media and links, plus channel stats. No login or phone number needed. Schedule it to monitor channels: each run returns only the posts that are new since the last run.

- **URL**: https://apify.com/lyklo/telegram-channel-scraper.md
- **Developed by:** [Lyklo](https://apify.com/lyklo) (community)
- **Categories:** Social media, News, Marketing
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.35 / 1,000 posts

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Telegram Channel Scraper & Monitor

Get posts from public Telegram channels: text, date, views, photos and videos, links and forwards, plus each channel's subscribers and posting activity.

Switch **What to return** to *New since the last run* and schedule it, and each run returns only the posts published since the previous run. Post numbers in a Telegram channel only go up, so nothing is returned twice and nothing is skipped, even when a run stops early.

The data comes from the public web preview of each channel (t.me/s/channel). No Telegram account or phone number is needed. This is an independent tool. It is not made, endorsed or sponsored by Telegram.

### Who it's for

- **Brand, PR and market research teams** following competitors', partners' or industry channels, with the new posts delivered to Slack or a spreadsheet every morning or every hour.
- **Crypto and news watchers** who need to react to channel announcements quickly.
- **Agencies and analysts** comparing channels: subscribers, posting frequency and typical views.
- **Developers and AI pipelines** that need a channel's posts as data.

### How to use it

1. Enter the channels, one per line: `t.me/durov`, `@durov` or `durov`.
2. Pick **What to return**:
   - *All posts*: the newest posts, every run.
   - *New since the last run*: the first run returns the newest posts; after that, only posts published since the previous run.
3. Set **Maximum posts per channel** (50 by default).
4. To monitor, save the input as a task and add a schedule in Apify. Connect it to Slack, Google Sheets, a webhook or Zapier/Make with Apify's integrations.

Use a different **Watch name** for each separate list (for example one per client).

### What you get

#### One row per post

| Field | Meaning |
| --- | --- |
| `channel`, `channelTitle` | The channel |
| `postId`, `url` | The post number and its link |
| `date` | When it was posted |
| `text` | The text, with line breaks kept and formatting removed |
| `views` | Views, as Telegram shows them (rounded, for example 5.85M) |
| `mediaType` | `photo`, `video`, `document`, `poll` or `none` |
| `imageUrls` | Photos, and the preview images of videos |
| `links` | Links in the text |
| `isForwarded`, `forwardedFrom` | Whether it is a forward, and the original channel's name when Telegram shows it |
| `change` | `listed` in *All posts* mode, `new` in *New since the last run* mode |

#### One summary row per channel

`subscribers` (and `subscribersChange` since the last run when monitoring), the numbers of `photos`, `videos`, `links` and `files`, `postsLast7Days`, `postsLast28Days`, `avgViewsRecent10` (average views of the newest 10 posts), `topPostsLast7Days` (the 3 most viewed posts of the week), `newSinceLastRun`, the description, the verified badge and the avatar.

#### Output example

A post row and a channel row from a run on `cointelegraph` with 10 posts (shortened):

```json
{
    "type": "post",
    "change": "listed",
    "channel": "cointelegraph",
    "channelTitle": "Cointelegraph",
    "postId": 72853,
    "url": "https://t.me/cointelegraph/72853",
    "date": "2026-10-26T12:07:21.000Z",
    "text": "🔥 JUST IN: Strive acquires 6,182 $BTC, bringing its total holdings to 43,000 Bitcoin.\n\nNews | Markets | YouTube",
    "views": 4750,
    "mediaType": "photo",
    "links": ["http://www.ct.com/", "https://ct.com/category/markets", "https://www.youtube.com/@cointelegraph"],
    "isForwarded": false,
    "forwardedFrom": null
}
```

```json
{
    "type": "channel",
    "channel": "cointelegraph",
    "channelTitle": "Cointelegraph",
    "subscribers": 328000,
    "subscribersText": "328K subscribers",
    "photos": 21000,
    "videos": 1290,
    "links": 58500,
    "postsLast7Days": 12,
    "avgViewsRecent10": 4272,
    "topPostsLast7Days": [
        { "postId": 72847, "views": 6960, "date": "2026-10-26T03:36:38.000Z", "url": "https://t.me/cointelegraph/72847" }
    ],
    "url": "https://t.me/cointelegraph"
}
```

This run read only the newest 12 posts, so `postsLast7Days` is 12 here. A monitoring watch that runs every day, with a maximum above the channel's posts per day, counts the whole week.

Post rows and channel rows share one dataset. Each row has `type` (`post` or `channel`); filter on it when you export the results or connect them to a spreadsheet.

### Pricing

You pay per event. In monitoring mode you pay only for new posts.

| Event | Price |
| --- | --- |
| Run start | $0.003 per run (with the default memory) |
| Post | $0.50 per 1,000 |
| Channel summary row | $0.002 each |

Prices in the table are for the Free plan. On paid Apify plans every event except the run start costs less: 10% off on Starter (Bronze discount), 20% off on Scale (Silver) and 30% off on Business (Gold) and above.

For example, watching 20 channels every day, with about 5 new posts per channel a day, costs about $2.80 a month.

### Good to know

- **Public channels only.** The web preview exists only for public channels. Groups, private channels, people and bots are skipped with a note in the log.
- **Views and subscribers are rounded** the way Telegram shows them (10.2M, 5.85K).
- **Busy channels.** If a channel posted more than your maximum since the last run, the newest posts are returned and the older ones are skipped; `newOverMax` on the channel row tells you about how many.
- **Posts in the last 7 and 28 days** count the posts this run read, plus, when monitoring, the ones seen in earlier runs. For a channel that posts a lot, the first run's numbers can be low until the watch has a few days of history.
- **Personal data.** Posts can mention or forward people. Use the data only when you have a legitimate reason.
- **If Telegram changes its channel pages**, the run stops with an error instead of returning wrong or empty results. Rows returned before that point are charged as usual; nothing after it is returned or charged.

# Actor input Schema

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

One public channel per line: a link (t.me/durov), an @name (@durov) or a name (durov). Only public channels with a web preview work; groups and private channels don't.

## `mode` (type: `string`):

All posts: the newest posts, every run. New since the last run: only posts newer than the ones returned before by a run with the same watch name (the first run returns the newest posts).

## `maxPostsPerChannel` (type: `integer`):

The most posts to return for each channel in one run. In monitoring mode, if a channel posted more than this since the last run, the newest ones are returned and the older ones skipped (counted in newOverMax).

## `watchName` (type: `string`):

New since the last run mode only. Keeps the memory of past runs separate for each watch, for example one per client. Letters, numbers and dashes.

## Actor input object example

```json
{
  "channels": [
    "telegram"
  ],
  "mode": "all",
  "maxPostsPerChannel": 10,
  "watchName": "default"
}
```

# Actor output Schema

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

One dataset with two kinds of rows, told apart by the type field. Rows with type "post" are channel posts: text, date, views, media, links and forwards. Rows with type "channel" are one per channel: subscribers and their change since the last run, posts in the last 7 and 28 days, average views of the newest posts and the most viewed posts of the week.

# 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 = {
    "channels": [
        "telegram"
    ],
    "maxPostsPerChannel": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("lyklo/telegram-channel-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 = {
    "channels": ["telegram"],
    "maxPostsPerChannel": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("lyklo/telegram-channel-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 '{
  "channels": [
    "telegram"
  ],
  "maxPostsPerChannel": 10
}' |
apify call lyklo/telegram-channel-scraper --silent --output-dataset

```

## MCP server setup

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