Capture and structure Telegram notes for Obsidian with Groq and GitHub
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 11 nodes and runs on Telegram events (message). Along the way it connects Telegram. It also calls api.groq.com over HTTP.
How it runs
Trigger: On Telegram events (message).
- Check for /start Command (If): checks a condition and branches into true / false
- Send Telegram Welcome Message (Telegram): uses Telegram
- Route by Message Type (Switch): routes items into 2 branches
- Download Telegram Voice File (Telegram): work with file
- Post to Chat Completion API (HTTP Request): calls api.groq.com (POST)
- Convert OGA to OGG Format (Code): runs custom JavaScript code
- Format Obsidian Markdown (Code): runs custom JavaScript code
- Post to Audio Transcription API (HTTP Request): calls api.groq.com (POST)
- Upload to GitHub Vault (HTTP Request): calls an HTTP API (PUT)
- Notify Telegram with Posts Ready (Telegram): uses Telegram
Services it uses
HTTP calls to: api.groq.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (6)
- Code
n8n-nodes-base.code - Telegram Trigger
n8n-nodes-base.telegramTrigger - If
n8n-nodes-base.if - Telegram
n8n-nodes-base.telegram - Switch
n8n-nodes-base.switch - HTTP Request
n8n-nodes-base.httpRequest
From the author
Quick overview This workflow captures Telegram voice notes or text messages, uses Groq (Whisper and Llama) to transcribe and structure them, converts the result into an Obsidian-ready Markdown note, commits it into a GitHub-hosted vault, and replies in…