Telegram Channel Posts: Text, Views and Date by Channel

Per-item lookup actor for Telegram Channel Posts: Text, Views and Date by Channel. See README for pricing and evidence.

How to use

1. In the Apify Console. Open the actor page and click Start — the channels field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. Via the API. Call it directly with a POST request — no Console needed once you have an API token:

   curl "https://api.apify.com/v2/acts/accountable_eel~telegram-channel-posts-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"channels":["telegram"]}'
   

3. On a schedule. Save this actor as an Apify Task with the input you want, then add a Schedule (hourly, daily, weekly) so it runs on its own — no server of your own required.

Input

{
  "channels": [
    "telegram"
  ]
}

One public channel per line: telegram, @telegram or https://t.me/telegram. Private channels and invite links are not supported. Accepted formats: telegram, @durov, https://t.me/s/telegram.

{
  "items": ["<identifier-1>", "<identifier-2>"],
  "maxConcurrency": 5
}

items is a list of Public Telegram channel usernames. One dataset row is returned per item; rows with "found": false are never charged.

Output

One row per item, for example:

query	found	status	channel	channelTitle	channelUrl	subscribers	postCount	monitorStatus	posts	postId	postUrl	text	date	views	viewsRaw	mediaType	linkUrl	isNew	firstSeenAt	scrapedAt
telegram	true	OK							<all posts (full list)>							<media (photo / video)>				1970-01-01T00:00:00.000Z

A miss comes back as a row with "found": false and is never charged.

Pricing

Pay-per-event. A flat per-run fee covers session/proxy warmup; you're billed per item only when data is actually found and returned — see .actor/pay_per_event.json for exact prices. A miss is never charged.

Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

curl "https://api.apify.com/v2/acts/accountable_eel~telegram-channel-posts-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"channels":["telegram"]}'

n8n. Add an HTTP Request node: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~telegram-channel-posts-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body Content Type JSON, JSON Body {"channels":["telegram"]} (swap in an expression from an earlier node for a real value).

Clay. Add an "HTTP API" column: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~telegram-channel-posts-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body {"channels":["{{channel}}"]}, mapping the row's channel into the channels array.

MCP. In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "telegram channel posts scraper" — the agent will find and run this actor.