Manage Supabase database records with Telegram bot commands
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 34 nodes and runs on Telegram events (message). Along the way it connects Telegram and Supabase.
How it runs
Trigger: On Telegram events (message).
- Extract Message Data (Edit Fields (Set)): sets 3 fields: chatId, text, firstName
- Is Authorized? (If): checks a condition and branches into true / false
- Parse Command and Parameters (Code): runs custom JavaScript code
- Route by Command (Switch): routes items into 7 branches
- Add Has Error? (If): checks a condition and branches into true / false
- Filter by Category? (If): checks a condition and branches into true / false
- Get Has Error? (If): checks a condition and branches into true / false
- Update Has Error? (If): checks a condition and branches into true / false
- Delete Has Error? (If): checks a condition and branches into true / false
- Search Has Error? (If): checks a condition and branches into true / false
…plus 23 more steps. See the full node list below.
Services it uses
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 (7)
- Telegram Trigger
n8n-nodes-base.telegramTrigger - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if - Code
n8n-nodes-base.code - Switch
n8n-nodes-base.switch - Supabase
n8n-nodes-base.supabase - Telegram
n8n-nodes-base.telegram
From the author
Manage Supabase database with Telegram commands How it works 1. Receive message — Telegram trigger captures incoming bot messages 2. Validate user — Checks if sender's chat ID is in the authorized list 3. Parse command — Extracts command type (/add, /list,…