Automation library · Content

Telegram chat limit with Postgres

Started by an incoming Telegram message, and works across Postgres and Telegram. 8 steps, 2 branches: small enough to read in one sitting and change without fear.

Small

8 stepsSmall: readable in one sitting
2Branches: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 1Logic 3Service 4

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

  1. 1Telegram TriggerTelegram triggerStarts it
  2. 2Get User IDPostgresService
  3. 3If user id existIfLogic
  4. 4Create new rowPostgresService
  5. 5Get the rowPostgresService
  6. 6Take the ID SetLogic
  7. 7If user can ask more IfLogic
  8. 8TelegramTelegramService

How it's built

Starts on
An incoming Telegram message
Steps
8, with 2 branches
Size
Small: readable in one sitting
Connects to
Postgres, Telegram
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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

What starts it?

It starts on an incoming Telegram message.

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?

Not long. At 8 steps it can be read in one sitting and changed without fear.

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 8 steps before you point it at anything that matters.