Block 1 - Telegram Trigger
- Type / Role
- n8n-nodes-base.telegramTrigger - telegramTrigger
- Config choices
- Version 1.1
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 ...
n8n-nodes-base.telegramtrigger, n8n-nodes-base.set, n8n-nodes-base.if, n8n-nodes-base.code, n8n-nodes-base.switch, n8n-nodes-base.supabase, n8n-nodes-base.telegram, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Diego Alejandro Parrás.
Original n8n.io sourceTurn your Telegram into a powerful database management interface. This workflow lets you create, read, update, delete, and search records in your Supabase database using simple chat commands — no SQL knowledge required.
Small business owners, freelancers, and teams who need to manage data on the go without opening dashboards or writing queries. Perfect for inventory tracking, simple CRM, expense logging, or any scenario where you need quick mobile access to your database.
Managing database records typically requires logging into admin panels or writing SQL queries. This workflow eliminates that friction by letting you interact with your data through familiar Telegram messages, from anywhere, on any device.
| Command | Format | Example |
|---|---|---|
/add |
name, price, quantity, category | /add iPhone 15, 999.99, 50, electronics |
/list |
[category] | /list or /list electronics |
/get |
id | /get 15 |
/update |
id field=value | /update 15 price=899 quantity=45 |
/delete |
id | /delete 15 |
/search |
text | /search iPhone |
/help |
— | Shows all available commands |
/newbot and follow the promptsRun this SQL in your Supabase project's SQL Editor:
CREATE TABLE products (
id SERIAL PRIMARY KEY,
name TEXT NOT NULL,
price DECIMAL(10,2),
quantity INTEGER DEFAULT 0,
category TEXT,
created_at TIMESTAMP DEFAULT NOW()
);
123456789 with your actual chat ID from step 2Send /help to your bot to verify everything works!
chatId equals [new user's chat ID]products to your table name in all Supabase nodesDifficulty level: Intermediate Estimated setup time: 15-20 minutes Monthly operating cost: $0 (Telegram and Supabase free tiers)
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 37 workflow blocks. Download the JSON for the full node graph.
| Workflow | Manage Supabase database records with Telegram bot commands |
|---|---|
| Complexity | advanced |
| Nodes | 37 |
| Categories | Document Extraction |
| Author | Diego Alejandro Parrás |
| Published | 02 Feb 2026 |
Use the JSON export at /data/workflows/13166/13166.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
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 ...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Document Extraction use case.