Automation library · Alerts and monitoring

Capture and structure Telegram notes for Obsidian with Groq

Started by an incoming Telegram message, and works across Telegram. 11 steps, 2 branches: a working afternoon to understand properly.

Medium

11 stepsMedium: a working afternoon
2Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 1Logic 4Service 6

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

  1. 1Telegram Bot TriggerTelegram triggerStarts it
  2. 2Check for /start CommandIfLogic
  3. 3Send Telegram Welcome MessageTelegramService
  4. 4Route by Message TypeSwitchLogic
  5. 5Download Telegram Voice FileTelegramService
  6. 6Post to Chat Completion APIHttp RequestService
  7. 7Convert OGA to OGG FormatCodeLogic
  8. 8Format Obsidian MarkdownCodeLogic
  9. 9Post to Audio Transcription APIHttp RequestService
  10. 10Upload to GitHub VaultHttp RequestService
  11. 11Notify Telegram with Posts ReadyTelegramService

How it's built

Starts on
An incoming Telegram message
Steps
11, with 2 branches
Size
Medium: a working afternoon
Connects to
Telegram
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Telegram account. 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. 11 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 11 steps before you point it at anything that matters.