# Telegram video merger bot with FTP and Postgres: n8n workflow

> Started by an incoming Telegram message, and works across FTP, Postgres and Telegram. 42 steps, 5 branches: large, and worth reading before you trust it...

Source: https://millionrounds.com/workflow/telegram-video-merger-bot-with-ftp-and-postgres (Millionrounds; every figure on the page links to its filing or article)

[Automation library](https://millionrounds.com/workflows) · [Content](https://millionrounds.com/workflows?category=Content#library)

# Telegram video merger bot with FTP and Postgres

Started by an incoming Telegram message, and works across FTP, Postgres and Telegram. 42 steps, 5 branches: large, and worth reading before you trust it with anything live.

Large

[Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Ftelegram-video-merger-bot-with-ftp-and-postgres)

**42 steps** Large: read it before trusting it with anything live

**5** Branches: places the flow splits

**0** Loops or waits

**3** Services it connects to

## The flow

Starts it 1 Logic 15 Service 26

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

- 1 **TT** Telegram trigger *Starts it*
- 2 **SP** Code *Logic*
- 3 **C** If *Logic*
- 4 **SU** Ftp *Service*
- 5 **CMD1** Switch *Logic*
- 6 **IN** Code *Logic*
- 7 **CLP** Code *Logic*
- 8 **M** Telegram *Service*
- 9 **GL** Postgres *Service*
- 10 **RS** Postgres *Service*
- 11 **CL** Postgres *Service*
- 12 **IM** If *Logic*
- 13 **MV** Ssh *Service*
- 14 **EM** If *Logic*
- 15 **RST** Ssh *Service*
- 16 **IS** If *Logic*
- 17 **ENQ** Code *Logic*
- 18 **WLM** Telegram *Service*
- 19 **EA** Ssh *Service*
- 20 **LE** Telegram *Service*
- 21 **VL** Code *Logic*
- 22 **CL1** Telegram *Service*
- 23 **VLL** Code *Logic*
- 24 **UP** Postgres *Service*
- 25 **SU1** Ftp *Service*
- 26 **VL1** Telegram *Service*
- 27 **MR** Telegram *Service*
- 28 **VL2** Code *Logic*
- 29 **WH** Http Request *Service*
- 30 **RS1** Ssh *Service*
- 31 **NV** Telegram *Service*
- 32 **ST** Code *Logic*
- 33 **FL** Postgres *Service*
- 34 **SRT** Ftp *Service*
- 35 **GL1** Telegram *Service*
- 36 **AS** Ssh *Service*
- 37 **MRG** Execute Workflow *Logic*
- 38 **SD** Ftp *Service*
- 39 **C1** Telegram *Service*
- 40 **CL2** Ssh *Service*
- 41 **CL3** Postgres *Service*
- 42 **DN** No Op *Logic*

## How it's built

- **Starts on:** An incoming Telegram message
- **Steps:** 42, with 5 branches
- **Size:** Large: read it before trusting it with anything live
- **Connects to:** FTP, Postgres, Telegram
- **Model:** None. This is plumbing, not judgement

## Questions

What does it need to run?

An n8n account, plus your own FTP, 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?

Take your time. At 42 steps it is large: read it before trusting it with anything live.

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

## Run it in n8n

- **Create your n8n account** Free to start. n8n is where the workflow runs. [Create an n8n account ↗](https://millionrounds.com/n8n)
- **Download the workflow** Free with a Millionrounds account. [Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Ftelegram-video-merger-bot-with-ftp-and-postgres)
- **Paste it into n8n** Open a new workflow in n8n and paste. Then connect your own accounts.

Stored with the author's traces removed: canvas notes, instance identifiers, saved credential names and any live document they had left behind.

## Connects to

Each opens the other workflows that use it.

[FTP](https://millionrounds.com/workflows?service=FTP#library)[Postgres](https://millionrounds.com/workflows?service=Postgres#library)[Telegram](https://millionrounds.com/workflows?service=Telegram#library)

## Workflows like it

Also content, with the same services where possible, closest in size first.

- [**Telegram bot for item multi select and saving to Postgres** 42 steps · Postgres, Telegram](https://millionrounds.com/workflow/telegram-bot-for-item-multi-select-and-saving-to-postgres)
- [**Automatic Instagram content creation with OpenAI and Telegram** 42 steps · calls a model · Airtable, Telegram](https://millionrounds.com/workflow/automatic-instagram-content-creation-with-openai-and-telegra)
- [**Generate Blog Posts on Autopilot with Tavily and WordPress** 42 steps · calls a model · Google Drive, Google Sheets](https://millionrounds.com/workflow/generate-blog-posts-on-autopilot-with-tavily-and-wordpress)
- [**Automate Telegram channel posts with Postgres** 43 steps · Postgres, Telegram](https://millionrounds.com/workflow/automate-telegram-channel-posts-with-postgres)
- [**Generate a full startup plan from one sentence with Postgres** 43 steps · Gmail, Google Drive](https://millionrounds.com/workflow/generate-a-full-startup-plan-from-one-sentence-with-postgres)
- [**Verify Telegram channel subscriptions with Postgres** 41 steps · Google Drive, Postgres](https://millionrounds.com/workflow/verify-telegram-channel-subscriptions-with-postgres)