n8n Agent Workflows
6 import-ready n8n workflows: x402 monitor, change alerts, Stripe log, AI digest and more.
View n8n Agent Workflows
Run your own AI assistant, voice-note transcriber, morning news digest and approval buttons in Telegram, in an afternoon with n8n.

Four importable n8n workflows for Telegram bots, built and checked against n8n 2.46:
| File | What it does |
|---|---|
| workflows/01-telegram-ai-assistant.json | AI assistant bot: answers text messages with an AI Agent that remembers the last 10 messages per chat, /start welcome, private mode (allow-list of user ids), long answers split under Telegram's 4096-character limit |
| workflows/02-telegram-voice-transcriber.json | send or forward a voice note, get back the transcript plus a summary and to-dos (OpenAI transcription) |
| workflows/03-telegram-daily-digest.json | every morning: reads your RSS feeds, keeps fresh, de-duplicated stories, writes a short digest with numbered source links and posts it to a chat or channel |
| workflows/04-telegram-approval-bot.json | POST a request (refund, expense, post to publish...) to a webhook, approve or decline it with buttons in Telegram, the decision goes back to your system |
Each workflow has a Setup sticky note. All logic you might want to change sits in small Code nodes whose source is also in code/ with tests.
The screenshot is real output from the kit’s own commands. Tested from a fresh download of this exact zip: ./run_tests.sh ran 13 tests OK on Python 3.13 and 3.10.

1. In n8n: Workflows > Import from File and pick a file from workflows/. 2. Create a bot with @BotFather (https://t.me/BotFather) and add its token as a Telegram credential; add an OpenAI credential for the AI nodes (or swap the model node for another chat model). 3. Replace REPLACE_ME_CHAT_ID (workflows 3 and 4) with your chat id, a group id or @yourchannel. 4. Activate. Telegram triggers need n8n on a public HTTPS URL (n8n Cloud or a self-hosted instance with WEBHOOK_URL set).
One bot, one trigger. Telegram sends each bot's updates to one webhook, so two active workflows with a Telegram Trigger on the same bot token replace each other. Use a separate bot for workflows 1 and 2, or merge them (route kind = voice from workflow 1 into the transcriber nodes). Workflows 3 and 4 only send messages, so they can share any bot.
./run_tests.sh # workflow structure, n8nlint --strict, and every Code node run on fixtures with Node.js
./demo.sh # shows the Code nodes on sample Telegram updates, feed items and approval requestsBefore release the workflows were also checked with n8n's own node definitions (parameters n8n would drop or flag), imported with the n8n 2.46.6 CLI, and run in n8n with the triggers replaced by the sample data: routing and Code nodes ran as expected up to the first node that needs a real credential. The bundled n8nlint (a static checker for n8n workflow files) runs in the tests.
Zip, 197 KB, v1.0, 29 files. You may use and modify this kit for your own work and for clients you serve, including paid client work. Not affiliated with or endorsed by Telegram or n8n.
4 n8n Telegram workflows: AI assistant bot with memory, voice-note transcriber, daily news digest, approval bot. Tested in n8n 2.46. $19.
6 import-ready n8n workflows: x402 monitor, change alerts, Stripe log, AI digest and more.
View n8n Agent WorkflowsCommunity course: build AI agent workflows in n8n you can trust. 3 modules, 9 lessons, 63 tests in real n8n.
View n8n for AI Agents (community course)n8n invoice review queue: duplicates, totals, bank-detail changes, credit notes. Never pays or posts.
View n8n Bookkeeper Invoice Exceptions PackShort weekly digest of new x402 + MCP tools and free kits, including the MCP OAuth Checker. No spam, unsubscribe any time.