# Answer FAQs and route Telegram users to support with Postgres: n8n workflow

> Started by an incoming Telegram message, and works across Postgres and Telegram. 29 steps, 6 branches: large, and worth reading before you trust it with...

Source: https://millionrounds.com/workflow/answer-faqs-and-route-telegram-users-to-support-with-postgre (Millionrounds; every figure on the page links to its filing or article)

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

# Answer FAQs and route Telegram users to support with Postgres

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

Large

[Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fanswer-faqs-and-route-telegram-users-to-support-with-postgre)

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

**6** Branches: places the flow splits

**0** Loops or waits

**2** Services it connects to

## The flow

Starts it 1 Logic 11 Service 17

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

- 1 **Telegram Trigger** Telegram trigger *Starts it*
- 2 **Variables TG** Set *Logic*
- 3 **Initialization** Set *Logic*
- 4 **Starts?** If *Logic*
- 5 **Welcome Message** Telegram *Service*
- 6 **Button?** If *Logic*
- 7 **Upsert bot status on START** Postgres *Service*
- 8 **Buttons** Switch *Logic*
- 9 **Get Bot Status** Postgres *Service*
- 10 **Main Menu** Telegram *Service*
- 11 **List FAQ** Postgres *Service*
- 12 **Define Flow** Switch *Logic*
- 13 **Union Number with Text** Set *Logic*
- 14 **Command OR Answer?** If *Logic*
- 15 **Commands** Switch *Logic*
- 16 **Add User Request** Postgres *Service*
- 17 **Union List** Summarize *Service*
- 18 **Get Answers** Postgres *Service*
- 19 **Set FAQ Start** Set *Logic*
- 20 **Request** Telegram *Service*
- 21 **Error** Telegram *Service*
- 22 **Request Success for User** Telegram *Service*
- 23 **List FAQ** Telegram *Service*
- 24 **Edit Fields** Set *Logic*
- 25 **Update bot status on MANAGER** Postgres *Service*
- 26 **Request Success for Manager** Telegram *Service*
- 27 **Update bot status on FAQ** Postgres *Service*
- 28 **Answer** Telegram *Service*
- 29 **Update bot status on START** Postgres *Service*

## How it's built

- **Starts on:** An incoming Telegram message
- **Steps:** 29, with 6 branches
- **Size:** Large: read it before trusting it with anything live
- **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?

Take your time. At 29 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 29 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%2Fanswer-faqs-and-route-telegram-users-to-support-with-postgre)
- **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.

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

## Workflows like it

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

- [**Automate B2B SaaS renewal risk management with CRM** 30 steps · Gmail, HubSpot](https://millionrounds.com/workflow/automate-b2b-saas-renewal-risk-management-with-crm)
- [**Advanced Telegram bot, ticketing system, liveChat, user** 31 steps · Redis, Telegram](https://millionrounds.com/workflow/advanced-telegram-bot-ticketing-system-livechat-user)
- [**WhatsApp to Chatwoot message forwarder with Postgres and Redis** 31 steps · Postgres, Redis](https://millionrounds.com/workflow/whatsapp-to-chatwoot-message-forwarder-with-postgres-and-red)
- [**Automated customer support system with Gmail** 31 steps · calls a model · Gmail, Google Sheets](https://millionrounds.com/workflow/automated-customer-support-system-with-gmail)
- [**Answer HR questions with OpenAI and PostgreSQL** 26 steps · calls a model · Pinecone, Postgres](https://millionrounds.com/workflow/answer-hr-questions-with-openai-and-postgresql)
- [**Answer Telegram data questions with DeepSeek and Open-Meteo** 25 steps · calls a model · Google Sheets, Telegram](https://millionrounds.com/workflow/answer-telegram-data-questions-with-deepseek-and-open-meteo)