Telegram Channel Scraper (Apify)

Export the public message history of Telegram channels: text, date, views, reactions and media links, filtered by date or keyword. JSON, CSV or Excel, no login.

Hosted MCP Server

npx add-mcp 'https://mcp.apify.com/?tools=monkey.d.scraping/telegram-channel-scraper'

Installs into Claude Code, Codex, Cursor and more

Documentation

Telegram Channel Scraper — History & CSV Export (monkey.d.scraping/telegram-channel-scraper) Actor

Telegram channel scraper for public messages and posts: export accessible history to CSV, Excel, JSON or Markdown. Filter by date or keyword; collect text, views, reactions and media URLs. No Telegram login. $0.20/1K posts plus the scheduled start fee.

Pricing

$0.20 / 1,000 telegram post returneds

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?

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 section below.

Each client library has reference documentation the quickstart does not restate: JavaScript/TypeScript (npm install apify-client) and Python (pip install apify-client).

README

Telegram Channel Scraper — History & CSV Export

Export the available history of public Telegram channels. Start with a channel link, select a date range and export post text, dates, available views and reactions, and original post links. Use CSV or Excel for analysis, JSON for integrations, or a Markdown document field in each JSON record for indexing.

Export public Telegram channel history with date filters and spreadsheet or Markdown output

Snapshot exports: each run is independent. For incremental exports, your workflow passes fromMessageId for each channel; for automatic task checkpoints, use the separate Telegram New Posts Monitor.

No Telegram account, phone number, bot token or Telegram API key required.

$0.20 per 1,000 returned posts. No per-channel fee. Platform usage included. See Pricing for the scheduled native start fee.

中文用户 / 中文用戶: 简体中文说明 · 繁體中文說明(Telegram频道采集、电报频道爬虫、Telegram频道导出CSV/Excel)

What can you use this Telegram channel scraper for?

  • News and crypto research: export posts from known public channels into a dated spreadsheet, with source links for verification.
  • Brand and competitor research: filter posts inside your selected channels by date or phrase, then compare the returned text, views and reactions.
  • AI knowledge bases: select Markdown documents to export post text with canonical source links for your indexing pipeline. No AI model is called.

Start with the small example below. Works with public Telegram channels; each run exports a snapshot.

Is this the right Telegram scraper?

Use this Actor when you already know the public channels or post URLs you want to export. Choose Spreadsheet columns for CSV/Excel, or Markdown documents for a text-indexing workflow with links back to the posts.

  • Known channels → export: stay here; begin with one channel and 10 posts ($0.002 post charge; see Pricing for the scheduled start fee).
  • A keyword, but no channel list → discover: use Telegram Keyword Search. Discovery has its own pricing.
  • Only new posts across repeated runs → monitor: use Telegram New Posts Monitor. Reuse the same task/checkpoint according to its instructions.

Each scheduled run exports a fresh snapshot of the same input.

Using keyword filters? Add a start date for a bounded first test. The post limit counts returned matches, not posts examined; SUMMARY.messagesExamined and filteredOut show how much history was scanned.

Ready-to-run Telegram export examples

Open an example below and save your own task in Console. Adjust the visible inputs, check the active Pricing tab and maximum cost per run, then run your copy. Export the dataset as JSON, CSV or Excel after checking the run summary. These examples are snapshot exports.

Public taskSaved collection limitsOutput and exportPost charge at saved limits
Telegram Channel Scraper — 10-post CSV starterCointelegraph; one channel, up to 10 posts totalcompact: one flat row per post with text, dates, views, reaction totals and source URLs. Export CSV, Excel or JSON.Up to $0.002 for 10 posts
Telegram posts to Markdown for AI datasetsdurov; up to 10 posts totalllm: one row per post with a document containing Markdown and a messageUrl source link. Export JSON for your knowledge base or RAG pipeline.Up to $0.002 for 10 posts
Export Telegram Channel Posts by Date Rangetelegram; posts from 1 January to 31 October 2026, up to 50 posts totalcompact: one row per post in the date window with text, dates, views and link. Export CSV or Excel.Up to $0.010 for 50 posts

Browse all ready-to-run examples → — English, 中文 and Русский.

Примеры на русском: Экспорт постов Telegram-канала в CSV: Хабр

Each saved post costs $0.0002, with platform usage included. The examples above show post charges; add the native start fee from 19 November 2026 (see Pricing). Fewer available posts produce fewer rows and a lower post charge. Keep both post limits when copying the task; changing them can change the charge. Check the active Pricing tab and Maximum cost per run before starting your copy.

For the CSV starter, open the Posts dataset view and choose CSV or Excel from Export. For the Markdown example, use Markdown documents to inspect the text, or export JSON and read each row's document field. Markdown is formatted from the collected public post; no AI model is called. SUMMARY.quality and CHANNEL_REPORT summarize what each run collected.

Export Telegram posts in three steps

  1. Add Channels to scrape and set Maximum posts per channel. The Console example uses 10.
  2. Choose Spreadsheet columns for CSV/Excel, Full records for structured JSON, or Markdown documents for indexing.
  3. Set Maximum cost per run, run the Actor, and open Output → Export.

The run output also exposes Download CSV and Download Excel links for seven common columns: channel, post ID, publication date, text, views, reaction total and source URL. These exports use the posts already collected, with no additional scraping or post charge. Full records and Markdown remain available through the dataset export. Dataset access permissions still apply.

The Console example:

{
  "channels": ["cointelegraph"],
  "maxMessagesPerChannel": 10,
  "outputPreset": "compact"
}

Ten returned posts have a $0.002 post charge; from 19 November 2026, the total at default memory is $0.00205, including the native start event. Set Maximum cost per run in Run options for an additional spending limit. An empty result has no post charge.

Channel names, @usernames and public URLs such as https://t.me/cointelegraph are accepted.

Choose the export for your workflow

GoalSuggested inputOutput
Open posts in Excel or Google SheetsA small message limit for the first testcompact: flat columns
Analyze announcements, mentions or engagementDate window and optional keyword filtersfull: structured fields
Build a searchable knowledge baseSelected channels and a date windowllm: one Markdown document per post
Refresh your own databaseOne channel and its saved fromMessageIdNewer posts, with checkpoint managed by your workflow
Archive accessible channel historyRemove both message limits and date/ID filtersAccessible public history, with a per-channel coverage report

Scrape Telegram posts by date

{
  "channels": ["cointelegraph", "@durov"],
  "afterDate": "7 days",
  "maxMessages": 1000,
  "maxMessagesPerChannel": 500,
  "outputPreset": "full",
  "includeChannelInfo": true,
  "downloadMedia": false
}

The message limits in this example keep the run small. Remove them to export the entire date window, with a matching run budget and timeout. afterDate and beforeDate accept ISO dates or relative expressions such as 7 days. The filters include posts on the specified boundaries.

Use includeKeywords, excludeKeywords or regexFilters to narrow posts by text. Use postUrls to request specific posts; leave channels empty when you only want those URLs.

From a Telegram history export to a recurring feed

Channel Scraper exports a snapshot; Monitor keeps its own checkpoint.

  1. Choose the same public channels in both tools. For a handoff with overlap, first save a new Monitor starter task, use initialRun: "baseline", keep resetState: false, and run it. Confirm the channels were checked without errors.
  2. Export the required history with Channel Scraper. SUMMARY and CHANNEL_REPORT show the covered ranges.
  3. Run that same Monitor task again, then schedule it at a frequency suited to your channels. Run it one run at a time and review each run summary.
  4. Merge both datasets using channelUsername + messageId as the unique key. The overlap is intentional. Confirm your destination saved each dataset independently.

Create the Monitor baseline before your export so the two datasets overlap. The new-post feed adds new posts; exported posts keep the text, views and reactions recorded at export time.

Fetch new posts on subsequent runs

fromMessageId is an exclusive lower bound: 72469 means return IDs greater than 72469. The number below is an example checkpoint, not a current channel position.

{
  "channels": ["cointelegraph"],
  "fromMessageId": 72469,
  "outputPreset": "full",
  "downloadMedia": false
}
  1. Save the posts in your own database, deduplicating by channelUsername + messageId.
  2. Inspect SUMMARY and CHANNEL_REPORT in the run’s key-value store.
  3. Advance the channel’s checkpoint to the highest stored ID only after the requested range was fully collected and your destination successfully saved the results.
  4. Pass that checkpoint in the next run’s input.

Before advancing, read the channel’s stoppedBecause value in CHANNEL_REPORT. range_complete or channel_start, with no unreadable ranges or run errors, indicates the requested walk finished. Otherwise keep the old checkpoint, run again with larger limits, and deduplicate the repeated posts.

Message IDs belong to individual channels. Keep a separate checkpoint and input per channel; a single fromMessageId applies to every channel in the input.

Your external workflow reads the results and supplies the next ID for each scheduled run. For a ready-made stateful workflow, see Telegram New Posts Monitor & Channel Discovery below. Incremental collection returns newer IDs; posts you already stored keep their recorded values.

Telegram channel data you can export

Covers public Telegram channels, with values as publicly shown at collection time. Depending on what Telegram exposes publicly, records can include:

  • Text, Markdown and rich-text entities.
  • Publication time, message ID and source URL.
  • Public view counts and reactions.
  • Media URLs and available metadata for photos, videos, audio, documents and stickers.
  • Albums, polls, link previews, replies and forwarded-post references.
  • Channel name, description, subscriber count and verification when available.

Enable downloadMedia to also attempt saving available media files in the run’s key-value store. Every media item keeps its source URL; Telegram media URLs can expire, so enable downloads for files you need to keep. Leave it off when your workflow only needs text and links.

Every field in the export

FieldWhat it holds
channelUsername, channelName, channelUrlWhich channel the post came from
messageId, messageUrlCanonical identity of the post; also used to deduplicate
publishedAtPublication time in ISO 8601 UTC
text, textLength, textMarkdown, entitiesMessage text as plain, Markdown, and typed offsets
views, viewsTextView count as an integer, plus the abbreviation as shown
reactions, reactionsTotalOne object per emoji with its count, plus the sum
mediaTyped array: photo, video, roundVideo, document, voice, audio, sticker — with URL, thumbnail, file name, size and duration
isAlbumWhether the row carries a multi-photo album
pollQuestion, quiz type, options and percentages
linkPreviewSite name, title, description and image of the linked page
forwardedFrom, replyToSource channel, message id and quoted preview
author, isEdited, isServiceMessagePost signature and status flags
links, hashtags, mentions, cashtagsEverything extracted from the text
channelSubscribers, verification, description, avatar and channel counters
scrapedAtWhen the row was collected

Fields are null or empty when Telegram does not publish a value. Counts converted from abbreviations such as 26.2K keep the precision of the public display.

Output formats and a sample record

  • Full (full): nested structured data for APIs and databases.
  • Compact (compact): flat columns for CSV and spreadsheets.
  • LLM (llm): Markdown documents for indexing and AI pipelines.

The dataset field schema describes all three presets. Preset-specific fields may be absent: hashtags is an array in full records and a space-separated string or null in compact records; document appears only in Markdown records. Posts with no visible text keep text: null. The common identity, date, text, engagement and extraction-time fields are always present, with null values where the source provides no value.

Illustrative excerpt from a full record; values are examples, not live channel metrics:

{
  "channelUsername": "examplechannel",
  "messageId": 123,
  "messageUrl": "https://t.me/examplechannel/123",
  "publishedAt": "2026-10-04T08:00:00.000Z",
  "text": "A new product announcement",
  "textMarkdown": "A new **product announcement**",
  "views": 1200,
  "reactions": [{ "emoji": "🔥", "count": 5, "countText": "5" }],
  "reactionsTotal": 5,
  "media": [],
  "poll": null,
  "replyTo": null
}

sortOrder: "oldestFirst" reverses returned posts within each channel. With a message limit, the Actor still selects from the newest matching posts; this option does not request the oldest posts in the channel or globally merge several channels by date.

Export accessible Telegram channel history

To request accessible history, clear both maxMessages and maxMessagesPerChannel (use explicit null values in JSON to override Console defaults), and remove date and fromMessageId filters. There is no fixed input post cap; set Maximum collection steps, the run budget and the timeout to match the history size.

Each run writes SUMMARY and CHANNEL_REPORT to its key-value store. The channel report includes the covered message-ID ranges, reachedChannelStart, stoppedBecause and unreadableRanges, so you can confirm which ranges were collected.

Runtime depends on history size, filters and media downloads.

Pricing

EventPrice
Returned post$0.0002
1,000 returned posts$0.20
10,000 returned posts$2.00
Native Actor startFree until 19 November 2026, 10:14:58 UTC; then $0.00005 per memory unit
Channel detailsNo additional charge

The native apify-actor-start event is charged automatically: one unit up to and including 1 GB RAM, then one additional unit for each extra GB. At the default 256–512 MB, 10 posts cost $0.00205 and 40 posts cost $0.00805 after the change. Empty runs also incur the start fee. The Pricing tab shows the current and upcoming tariffs.

Platform usage is included. Set Maximum cost per run in Run options to cap total event charges. The Actor stops collecting when that allowance is exhausted.

Telegram scraper API, n8n, Make and Zapier

Export the dataset as JSON, CSV or Excel, or read it through the Apify API from your HTTP client, n8n, Make or another automation workflow. A schedule can start repeated runs; a finished-run webhook can trigger processing in your destination. Your integration manages result persistence, deduplication and any incremental checkpoint.

More tools by the same author

Chinese Simplified

中文说明:Telegram频道采集工具(Telegram Channel Scraper 爬虫 / API)

Telegram Channel Scraper 将公开Telegram频道(电报频道)的帖子批量导出为 CSV、Excel 或 JSON:帖子正文、发布时间、浏览量、表情回应总数和原帖链接,完整记录中还包含可用的媒体链接。输入频道名即可开始,可以先采集10条帖子测试,也可以按日期范围或单条帖子链接导出,还能导出频道公开可见的历史帖子。每1,000条帖子仅0.20美元,不按频道收费,平台用量已包含。无需Telegram账号、手机号、Bot Token 或 Telegram API 密钥。

适合已经知道要采集哪些公开频道的新闻和加密货币研究人员、品牌和市场分析团队,以及需要为AI知识库准备数据的开发者。

为什么选择这款Telegram频道爬虫?

  • 价格低,按结果计费:每条返回的帖子0.0002美元,即每1,000条0.20美元;频道详情不额外收费,平台用量已包含。没有返回帖子时不收取帖子费用。
  • 无需登录:只需填写公开频道的用户名、@用户名 或 https://t.me/... 链接,不需要Telegram账号或API密钥。
  • 三种导出格式:表格列(compact)适合CSV和Excel,完整记录(full)适合API和数据库,Markdown文档(llm)适合AI知识库和RAG流程。生成Markdown不调用任何AI模型。
  • 按日期和关键词筛选:afterDate 和 beforeDate 支持具体日期或 7 days 这样的相对时间;includeKeywords、excludeKeywords 和 regexFilters 可按正文筛选帖子;postUrls 可直接导出指定帖子。
  • 一键下载CSV和Excel:运行输出中提供 Download CSV 和 Download Excel 链接,包含频道、帖子ID、发布时间、正文、浏览量、表情回应总数和原帖链接七个常用列,使用已采集的帖子生成,不额外采集、不额外收费。
  • 透明的覆盖报告:每次运行都会生成 SUMMARY 和 CHANNEL_REPORT,列出已覆盖的消息ID范围和停止原因,方便确认导出范围是否完整。
  • 可选精确订阅数:同时开启 Include channel details 和 Fetch exact subscriber count,即可读取频道公开主页上的精确订阅人数,无单独费用。

适用场景

  • 新闻和加密货币研究:把已知公开频道的帖子导出为带日期的表格,并保留原帖链接便于核实。
  • 品牌和竞品研究:按日期或关键词筛选所选频道中的帖子,对比正文、浏览量和表情回应。
  • AI知识库和RAG:选择Markdown文档格式,每条帖子生成一份带原帖链接的文档,直接用于索引流程。
  • 频道历史存档:清空帖子数量上限和日期/ID筛选,导出频道可访问的公开历史,用于分析或归档。
  • 增量更新自有数据库:在你的工作流中保存每个频道的 fromMessageId,下次运行只获取ID更大的新帖子。
  • 自动化流程:通过Apify API、n8n、Make或Zapier读取结果;定时任务可重复运行,运行完成的Webhook可触发后续处理。

可以获取哪些数据?

  • 帖子内容:正文、Markdown格式正文和富文本实体,以及从正文中提取的链接、话题标签(hashtag)、提及和 $ 代码(cashtag)。
  • 帖子标识:频道用户名和名称、消息ID、规范原帖链接(可用于去重)、发布时间(ISO 8601 UTC)。
  • 互动数据:公开浏览量(整数和原始显示值,例如 26.2K)、每种表情回应的数量及总数。
  • 媒体和结构:照片、视频、圆形视频、文件、语音、音频和贴纸的链接、缩略图、文件名、大小和时长;相册、投票、链接预览、回复和转发来源。
  • 频道信息:频道名称、简介、订阅人数、认证状态、头像和频道计数。
  • 可选媒体下载:开启 downloadMedia 后,可把可用的媒体文件保存到运行的键值存储中。

价格

按返回的帖子计费,平台用量已包含:

计费项目价格
每条返回的帖子0.0002美元
1,000条帖子0.20美元
10,000条帖子2.00美元
Actor原生启动事件2026年11月19日10:14:58(UTC)之前免费;之后每个内存单位 0.00005美元
频道详情不额外收费

启动事件按内存计算:1 GB及以下计1个单位,之后每增加1 GB再加1个单位。在默认的256–512 MB内存下,启动费生效后,10条帖子共0.00205美元,40条帖子共0.00805美元,单次运行1,000条帖子共0.20005美元;没有返回帖子的运行也会收取启动费。可在 Run options 中设置 Maximum cost per run,限制每次运行的最高费用。请以当前Pricing页面显示的价格为准。

使用方法

  1. 在 Channels to scrape 中添加频道,每行一个:cointelegraph、@cointelegraph 或 https://t.me/cointelegraph 都可以。
  2. 设置 Maximum posts per channel,建议先用10条测试。
  3. 选择导出格式:Spreadsheet columns(CSV/Excel)、Full records(结构化JSON)或 Markdown documents(文本索引)。
  4. 设置 Maximum cost per run,点击 Start,完成后在 Output → Export 导出为CSV、Excel或JSON,或通过API获取。

控制台示例(10条帖子,表格格式):

{
  "channels": ["cointelegraph"],
  "maxMessagesPerChannel": 10,
  "outputPreset": "compact"
}

按日期导出最近7天的帖子:

{
  "channels": ["cointelegraph", "@durov"],
  "afterDate": "7 days",
  "maxMessages": 1000,
  "maxMessagesPerChannel": 500,
  "outputPreset": "full",
  "includeChannelInfo": true,
  "downloadMedia": false
}

也可以直接打开现成的示例任务:10条帖子导出CSV,或 将帖子导出为Markdown,用于AI数据集。每个示例10条帖子的帖子费用最多0.002美元。

中文示例任务: Telegram频道导出:中文加密货币快讯(Foresight News)、Telegram频道导出:少数派中文科技文章

常见问题

采集Telegram频道需要API密钥吗? 不需要。输入公开频道的用户名或链接即可,不需要Telegram账号、手机号或API密钥。

如何把Telegram消息导出为CSV或Excel? 选择 Spreadsheet columns(outputPreset: "compact"),运行后在数据集的 Export 菜单中选择CSV或Excel,或直接使用运行输出中的 Download CSV / Download Excel 链接。

如何导出频道的全部可访问历史? 清空 maxMessages 和 maxMessagesPerChannel(在JSON中设为 null),去掉日期和 fromMessageId 筛选,设置合适的 Maximum collection steps 和运行预算,运行后查看 CHANNEL_REPORT 中的覆盖范围。

会自动下载媒体文件吗? 默认返回可用的媒体链接和元数据。需要把文件一起保存时,开启 Download media files。

Markdown输出会调用AI模型吗? 不会。它只是把采集到的帖子整理成带原帖链接的文档;摘要、向量化等处理在你自己的下游流程中完成。

1,000条Telegram帖子多少钱? 帖子费用为0.20美元,频道信息和平台用量已包含。2026年11月19日10:14:58(UTC)之后,再加每个内存单位0.00005美元的启动事件:默认内存下单次运行1,000条帖子共0.20005美元。

如何只获取新帖子? 把上次保存的最大消息ID作为 fromMessageId 传入,即可只返回ID更大的帖子,检查点由你自己的工作流保存。如果希望由工具自动保存检查点,请使用下方的Telegram新帖监控工具。

可以通过API、n8n、Make或Zapier调用吗? 可以。数据集可以导出为JSON、CSV或Excel,也可以通过Apify API在HTTP客户端、n8n、Make、Zapier等自动化流程中读取;运行完成的Webhook可以触发后续处理。

中文说明会翻译采集到的数据吗? 不会。中文说明只是使用文档;采集到的数据保持来源的原始语言(帖子正文按频道发布时的原文呈现)。

其他Telegram工具

  • YouTube 视频、字幕与评论采集:在 YouTube 上追踪同样的话题,视频、Shorts 与频道,字幕文本和每个视频最多100条评论已包含,每1,000个视频0.19美元起。
  • Telegram关键词搜索工具:不知道该看哪些频道时,按关键词、品牌名或产品名查找Telegram公开帖子,适合品牌提及和舆情监控。
  • Telegram新帖监控工具:同一任务自动保存检查点,定时采集公开频道的新帖子,可选按主题发现频道。

Chinese Traditional

中文說明(繁體):Telegram頻道擷取工具(Telegram Channel Scraper 爬蟲 / API)

Telegram Channel Scraper 將公開Telegram頻道(電報頻道)的貼文匯出為 CSV、Excel 或 JSON:貼文內容、發布時間、瀏覽次數、表情回應總數與原文連結。可依日期範圍或單則貼文連結匯出。每1,000則貼文0.20美元,不按頻道收費,平台用量已包含。不需要Telegram帳號、手機號碼、Bot Token或Telegram API金鑰。

為什麼選擇這款Telegram頻道爬蟲?

  • 不必登入:填寫公開頻道名稱或 https://t.me/... 連結即可。
  • 三種匯出格式:表格欄位(compact)適合CSV與Excel,完整紀錄(full)適合API與資料庫,Markdown文件(llm)適合AI知識庫。
  • 透明的涵蓋報告:每次執行都會產生 SUMMARY 與 CHANNEL_REPORT,列出涵蓋範圍與停止原因。

適用場景

  • 品牌輿情監測:依日期或關鍵字篩選所選頻道的貼文。
  • 競品監測:匯出競爭對手公開頻道的貼文,並保留原文連結方便查核。
  • 新聞追蹤:把已知新聞頻道的貼文匯出為帶日期的表格。
  • 社群研究:匯出頻道可存取的公開歷史,用於分析或歸檔。

使用方法

  1. 在 Channels to scrape 中新增頻道,每行一個:cointelegraph、@cointelegraph 或 https://t.me/cointelegraph。
  2. 設定 Maximum posts per channel(建議先用10則測試),並選擇匯出格式。
  3. 設定 Maximum cost per run,點擊 Start,完成後在 Output → Export 匯出。
{
  "channels": ["cointelegraph"],
  "maxMessagesPerChannel": 10,
  "outputPreset": "compact"
}

現成範例任務:10則貼文匯出CSV、將貼文匯出為Markdown。

中文範例任務: Telegram频道导出:中文加密货币快讯(Foresight News)、Telegram频道导出:少数派中文科技文章

價格

每則回傳的貼文 0.0002美元(1,000則 0.20美元),頻道詳情不另收費,平台用量已包含。Actor原生啟動事件在2026年11月19日10:14:58(UTC)之前免費;之後每個記憶體單位 0.00005美元。

常見問題

需要Telegram API金鑰嗎? 不需要,輸入公開頻道名稱或連結即可。

如何匯出為CSV或Excel? 選擇 Spreadsheet columns(outputPreset: "compact"),或直接使用執行輸出中的 Download CSV / Download Excel 連結。

如何只取得新貼文? 傳入上次的最大訊息ID作為 fromMessageId;需要自動檢查點時請使用 Telegram New Posts Monitor。

中文說明會翻譯擷取到的資料嗎? 不會。說明是中文,資料保留來源的原始語言(貼文內容以頻道發布時的語言呈現)。

完整欄位與輸出範例請見英文說明或简体中文说明。

Which Telegram Actor should I use?

Your goalRecommended ActorStart with an example
Find public posts by keywordTelegram Keyword Search — discovery with literal matches in text or channel title Product mentions → CSV
Export recent posts or accessible historyTelegram Channel Scraper — date filters and CSV, JSON or Markdown layouts Known channels → CSV
Collect newly published posts repeatedlyTelegram New Posts Monitor — reuse the same saved task and checkpoint New posts → saved checkpoint

All three work with public Telegram channels, with no Telegram login.

Run budget and billing diagnostics

Small runs check their remaining post allowance before opening another channel. An exhausted budget stops opening new channels. A channel whose public content cannot be read is reported as CHANNEL_UNREADABLE, separately from a valid empty channel.

Set a maximum cost per run to cap post charges. SUMMARY.postsReturned counts posts successfully saved; chargedPosts counts only confirmed telegram-post charges. billingMode distinguishes active billing from runs without that event. If an active charge is only partially fulfilled, the run stops and savedPostsNotCharged reports the difference. An uncertain budget, storage failure or charging error stops further work, preserves a diagnostic summary and fails the run. Charges are never retried automatically. Start a new run instead of resurrecting a run with saved posts or uncertain billing.

Frequently asked questions

Can I scrape Telegram without an API key?

Yes. Enter a public channel username or URL. No Telegram account, phone number or API key is required.

How do I export Telegram messages to CSV or Excel?

Choose Spreadsheet columns (outputPreset: "compact"), run the Actor, and select CSV or Excel from the dataset’s Export menu.

What does full history include?

The channel history that is publicly visible. Clear both post limits and date/ID filters, set an appropriate Maximum collection steps and run budget, then check the coverage report.

Are media files downloaded automatically?

No. Available media URLs and metadata are returned. Enable Download media files only when you also need available files stored with the run.

How much do 1,000 Telegram posts cost?

The post charge is $0.20 for 1,000 returned posts; channel metadata and platform usage are included. Until 19 November 2026 at 10:14:58 UTC, starting a run is free. After that, add the native $0.00005 start event per memory unit: $0.20005 total for 1,000 posts in one run at the default memory. See Pricing for memory scaling and empty runs.

Can I search all Telegram messages by keyword here?

This Actor starts from known public channels or post URLs, and its text filters select from the posts it reads. For keyword discovery across channels, use the keyword-search Actor.

Why can a run return fewer posts than the limit?

The limit is a maximum. The channel may have fewer public posts, filters may exclude some, or the run budget may be reached first; SUMMARY.quality and CHANNEL_REPORT show which. Optional fields such as reactions are null when not published, not zero.

Does Markdown output call an AI model?

No. It formats the collected post into a document with a source link. Summarization, embeddings and model inference belong in your downstream workflow and may have separate costs.

How do I get help?

Open the Issues tab with the run ID, a public channel or post URL and the expected result. Do not share credentials or private data.

Run outcome and diagnostics

Open Run outcome and next step in Output. SUMMARY.outcome.code (no_matches, no_posts_in_range, empty_public_preview, source_incomplete, scan_limit, charge_limit or a billing code) explains how the run ended, and the accompanying message gives the next step.

The default Maximum collection steps is 100 for the whole run, shared by all channels. It limits how much history is scanned, independently of returned posts and the maximum event charge. Set maxRequests explicitly (1–10,000) for a larger export; prefer a narrower date window first. A run that reaches the cap is reported as partial; keep your checkpoint until the range is complete.

For repeated snapshots, batch known channels into one run where practical and choose a collection interval that matches their posting frequency. If there are no new posts, wait before repeating the same request. Use the separate New Posts Monitor for managed checkpoints.

Optional media downloads default to 10 MiB per file and 25 MiB received per run. Set maxMediaFileBytes (up to 20 MiB) and maxMediaTotalBytes (up to 100 MiB) only when needed. Files above the limit keep their source URL. Full records expose media[].downloadStatus; SUMMARY.media reports received bytes, saved, skipped and failed files. Text and post collection continue when a media file is skipped.

SUMMARY.quality reads bounded when the attempted public scan finished, limited when a selected limit, budget or collection scope bounded the run, and partial when a source error, a known coverage gap or a row without a required post ID, link or timestamp occurred. recordsInspected, missingRequiredFields and optionalFieldsUnavailable are field checks, not billing counters. CHANNEL_REPORT lists unreadable message-ID ranges and, for explicit post URLs, requestedPostIds, missingPostIds and notCheckedPostIds. SUMMARY.channelsNotChecked lists channels not reached when collection stopped.

Only posts belonging to the requested public channel are returned. SUMMARY.sourcePostsIgnored and sourceMismatchPages count posts and pages from other channels that were excluded; they are not returned posts or billable events. Forwarded text and links to other channels inside a valid post are preserved.

Temporary source errors are retried automatically. SUMMARY.scanBudget shows how much of Maximum collection steps was used; it is not a billable event. Only returned posts incur the post event.

Changes on 8 November 2026

BeforeNow
CHANNEL_REPORT reason PREVIEW_UNAVAILABLECHANNEL_NOT_PUBLIC
CHANNEL_REPORT reason UNRECOGNIZED_PUBLIC_PAGECHANNEL_UNREADABLE
A previous reason for a source that could not be preparedSOURCE_UNAVAILABLE
subscribersSource public_profile / public_previewexact / displayed
SUMMARY.requestBudgetSUMMARY.scanBudget (limit, used, reached)

Detailed technical counters were retired from SUMMARY. Use pagesFetched, messagesExamined, scanBudget and CHANNEL_REPORT.

Does the end date include the whole day?

Yes. For a date-only input, afterDate starts at 00:00:00 UTC and beforeDate ends at 23:59:59.999 UTC. Timestamps with a timezone preserve their exact instant. Relative months and years use calendar arithmetic, clamped to the last valid day when necessary. Invalid dates and inverted ranges stop before collection; posts without a valid date do not pass a date filter. This makes historical exports reproducible across timezones.

Real observed output excerpt

Reduced record from an owner verification run observed on 17 October 2026. Field values are retained from that observation and may have changed since then.

{
  "channelUsername": "cointelegraph",
  "messageId": 72711,
  "messageUrl": "https://t.me/cointelegraph/72711",
  "publishedAt": "2026-10-17T11:46:24.000Z",
  "views": 4630,
  "reactionsTotal": 93,
  "scrapedAt": "2026-10-17T17:33:06.260Z"
}

This is the compact preset. Message text and media fields are omitted here. Numeric views and reaction totals are observations at collection time, not unique audience measurements. IDs and source URLs identify the post.

Exact subscriber counts

Enable Fetch exact subscriber count with Include channel details to add the exact public subscriber count once per channel with matching posts. Disabled by default. It uses one step of Maximum collection steps per channel and has no separate event fee. If unavailable or the limit is reached, the displayed rounded count is kept. subscribers uses the exact count when available; subscribersExact is otherwise null and subscribersSource is exact or displayed (see Changes on 8 November 2026). In full output these fields are nested under channel; compact output exposes them directly. subscribersText preserves the original abbreviated displayed value. LLM output uses the selected count in the document. Counts can change between requests.

Actor input Schema

channels (type: array):

Add one channel per line: cointelegraph, @cointelegraph or https://t.me/cointelegraph. For exact post URLs only, clear this field and use Single post URLs below.

maxMessagesPerChannel (type: integer):

Start with 10 for a small test. Clear this limit to request accessible history; also clear the total limit and date/ID filters. Maximum collection steps, spending budget and timeout set how far collection goes.

outputPreset (type: string):

Pick the shape that matches where the data is going next.

afterDate (type: string):

Inclusive start in UTC. Use YYYY-MM-DD or 7 days. Dates and ranges are validated before collection starts.

beforeDate (type: string):

Inclusive end in UTC: YYYY-MM-DD includes the entire day through 23:59:59.999. A timestamp with timezone keeps its exact time.

includeKeywords (type: array):

Keep posts when the text, channel title or poll question contains at least one phrase.

excludeKeywords (type: array):

Discard posts when the text, channel title or poll question contains any phrase.

postUrls (type: array):

Export only these exact posts, e.g. https://t.me/durov/342. Useful for enriching a list of links you already have. Works on its own or alongside the channels above. (Optional)

maxMessages (type: integer):

Optional maximum for the whole run, alongside the per-channel limit. For accessible history, clear both post limits and set an appropriate Maximum collection steps, spending budget and timeout.

fromMessageId (type: integer):

Exclusive lower bound. Use one channel and its last fully collected checkpoint. Keep the checkpoint yourself and pass it to the next run.

sortOrder (type: string):

Orders the selected posts within each channel. With a post limit, the most recent matching posts are selected; Oldest first then lists them from oldest to newest.

regexFilters (type: array):

Keep a message only when its text matches at least one JavaScript-compatible pattern. (Optional)

includeChannelInfo (type: boolean):

Include available channel metadata such as subscriber count, description and verification. No additional result charge.

downloadMedia (type: boolean):

Off by default. Saves available public media files in the run’s key-value store. Source URLs remain available when exposed; downloading can take longer.

maxRequests (type: integer):

Shared scan limit for the whole run, across all channels. Default 100. Raise it for larger historical exports. Set separately from the post limit and spending budget.

maxMediaFileBytes (type: integer):

Default 10 MiB. Oversized files are skipped and keep their source URL. Active only when Download media files is enabled.

maxMediaTotalBytes (type: integer):

Default 25 MiB, shared across files and counting every received byte. Streaming stops after the chunk that crosses this value, so the total can end slightly above it.

exactSubscribers (type: boolean):

Optional exact public subscriber count per channel with matching posts. Uses one collection step per channel; keeps the displayed rounded count when unavailable. No additional event fee. Keep Include channel details enabled.

Actor input object example

{
  "channels": [
    "cointelegraph"
  ],
  "maxMessagesPerChannel": 10,
  "outputPreset": "compact",
  "sortOrder": "newestFirst",
  "includeChannelInfo": true,
  "downloadMedia": false,
  "maxRequests": 100,
  "maxMediaFileBytes": 10485760,
  "maxMediaTotalBytes": 26214400,
  "exactSubscribers": false
}

Actor output Schema

overview (type: string):

Every public post collected in this run, deduplicated by canonical message URL.

downloadCsv (type: string):

Export the collected posts with seven common columns: channelUsername, messageId, publishedAt, text, views, reactionsTotal and messageUrl. Full records and Markdown remain in the dataset. Requires access to this run’s dataset.

downloadExcel (type: string):

Export the collected posts with seven common columns: channelUsername, messageId, publishedAt, text, views, reactionsTotal and messageUrl. Full records and Markdown remain in the dataset. Requires access to this run’s dataset.

runSummary (type: string):

Read outcome.code and outcome.message first. Includes scan budget, collection status, media byte usage, saved and charged counts.

channelReport (type: string):

For each channel: posts returned, the message-ID ranges collected, whether the start of the channel was reached, and the reason collection stopped.

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

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": [
        "cointelegraph"
    ],
    "maxMessagesPerChannel": 10,
    "outputPreset": "compact"
};

// Run the Actor and wait for it to finish
const run = await client.actor("monkey.d.scraping/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

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": ["cointelegraph"],
    "maxMessagesPerChannel": 10,
    "outputPreset": "compact",
}

# Run the Actor and wait for it to finish
run = client.actor("monkey.d.scraping/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

echo '{
  "channels": [
    "cointelegraph"
  ],
  "maxMessagesPerChannel": 10,
  "outputPreset": "compact"
}' |
apify call monkey.d.scraping/telegram-channel-scraper --silent --output-dataset

MCP server setup

{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,monkey.d.scraping/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/YHNv81f5s5RaLdXTf/builds/2ydbbAYPP4o4vebyh/openapi.json