Automation library · Integrations

GitHub Public Repository Releases RSS To Telegram

Started by an event in a connected app, and works across RSS. 9 steps, 1 branch, 1 loop or waits: a working afternoon to understand properly.

Medium

Download free
9 stepsMedium: a working afternoon
1Branch: places the flow splits
1Loop or waits
1Service it connects to

The flow

Starts it 1Logic 7Service 1

The steps in the order they run, from what starts it.

  1. 1RSS Feed TriggerRss Feed Read triggerStarts it
  2. 2If not emptyIfLogic
  3. 3ConfigSetLogic
  4. 4No Operation, do nothingNo OpLogic
  5. 5Convert HTML Rss to MarkdownMarkdownLogic
  6. 6Clean & split the content for telegram limits. CodeLogic
  7. 7Loop posting the content based on sizeSplit In BatchesLogic
  8. 8Telegram Loop Message PartsHttp RequestService
  9. 9Save Message ID for ReplySetLogic

How it's built

Starts on
An event in a connected app
Steps
9, with 1 branch, 1 loop or waits
Size
Medium: a working afternoon
Connects to
RSS
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own RSS account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an event in a connected app.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 9 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 9 steps before you point it at anything that matters.