Automation library · Alerts and monitoring

Telegram bot with Supabase and OpenAI

Started by an incoming Telegram message, and works across Supabase and Telegram. 10 steps, 1 branch: a working afternoon to understand properly.

Medium

10 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 1Logic 2Service 7

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

  1. 1Get New MessageTelegram triggerStarts it
  2. 2Find UserSupabaseService
  3. 3If User existsIfLogic
  4. 4MergeMergeLogic
  5. 5OPENAI - Create threadHttp RequestService
  6. 6OPENAI - Send messageHttp RequestService
  7. 7Create UserSupabaseService
  8. 8OPENAI - Run assistantHttp RequestService
  9. 9OPENAI - Get messagesHttp RequestService
  10. 10Send Message to UserTelegramService

How it's built

Starts on
An incoming Telegram message
Steps
10, with 1 branch
Size
Medium: a working afternoon
Connects to
Supabase, Telegram
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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

Plan an afternoon. 10 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 10 steps before you point it at anything that matters.