Telegram Channel Feed

The Telegram Channel Feed node reads the new posts of a public Telegram channel. It returns them as structured posts, with text, link, date and media, and as one text. It needs no bot and no login, and each run returns only the posts that came after the last run. Use it with a Schedule Trigger to follow a channel, then rewrite or summarize the posts with a Generate Text - Any LLM node and publish the result.

When to use it

• Follow a channel and rewrite its new posts in your own voice.
• Build a daily digest of what several channels posted.
• Repost new posts to your own channel with Telegram Post, or to other networks with Publish to Social.

Quick start

Settings

Outputs

A connection in Each mode from JSON runs the next node once per post. Extract Field and List read the posts directly.

Each post in JSON has these fields:

How new posts are found

The node reads the web preview page of the channel, t.me/s/ followed by the channel name.

• A position for each channel. The node keeps a position: the last post it returned. The position is stored for each node of the saved workflow and for each channel. A new channel starts fresh, and an earlier channel resumes where it stood.
• The first run. The first run, or the first after Reset position, returns the newest posts, up to Max posts per run. The position then moves to the newest post, and older posts are never read.
• Every later run. Each run returns the oldest posts after the position, up to Max posts per run, and moves the position to the last of them. When posts arrive faster than the schedule reads them, each run takes the next batch, so nothing is skipped.
• Posts with nothing to read. A poll, a voice note or a document without a caption is passed over, and the position moves past it.
• The position moves when the posts are read. If a later node of the same run fails, the next run does not return that batch again. Re-fetch the last 5 shows it again.
• No new post. The run completes, returns no post and is not charged. The nodes after the feed that would work on its text are skipped.
• Who moves the position. Scheduled runs, runs of a published app and your own Run share one position. When someone else runs the workflow in the editor, the feed reads the channel without moving the position.

Credits

Each run that returns at least one new post costs 11 credits. A run that finds no new post is free. Re-fetch the last 5 is charged like a run. A failed run, such as one on a private channel, is refunded.

A scheduled feed runs often, so check the cost of the schedule. Every 15 minutes means up to 96 charged runs a day, or at most 1,056 credits. Every hour means up to 24 charged runs a day, or at most 264 credits.

Limits

• Public channels only. The channel must be public and have its web preview turned on, as most public channels do. A private channel, or a channel with the preview turned off, fails the run with a clear error.
• About 40 posts per run. A run reads at most two preview pages, about 40 posts. With a long backlog, the rest comes on the next runs.
• Media links expire. Photo and video links come from Telegram and stop working within days. To keep a picture, pass it on in the same run, for example to an upload node or a generation node, instead of storing the link.

Tips

• Match the schedule to the channel. A channel that posts twice a day does not need a check every 5 minutes.
• Tell the model what the text is. In the instructions of the Generate Text - Any LLM node, say that the input is a set of Telegram posts separated by ---.
• React to your own bot instead. To start a workflow when someone writes to your bot, use the Telegram Trigger.