This workflow follows the Telegram → Telegram Trigger recipe pattern — see all workflows that pair these two integrations.

The workflow JSON

Copy or download the full n8n JSON below. Paste it into a new n8n workflow, add your credentials, activate. Full import guide →

Download .json

Credentials you'll need

Each integration node will prompt for credentials when you import. We strip credential IDs before publishing — you'll add your own.

Pro

For the full experience including quality scoring and batch install features for each workflow upgrade to Pro

Zalo User Demo Connect Telegram. Uses n8n, telegram, telegramTrigger, n8n-nodes-zalo-user. Webhook trigger; 18 nodes.

Source: https://gist.github.com/thanhsm/1da2ca45eb6e6890273c33aab73d6fa7 — original creator credit. Request a take-down →

Workflows that share integrations, category, or trigger type with this one. All free to copy and import.

Slack & Telegram

Zalo User Demo Connect Telegram. Uses n8n, n8n-nodes-zalo-user, telegram, telegramTrigger. Webhook trigger; 19 nodes.

n8n, N8N Nodes Zalo User, Telegram +1

Slack & Telegram

Demo2. Uses n8n-nodes-zalo-user, n8n, telegram, telegramTrigger. Webhook trigger; 17 nodes.

N8N Nodes Zalo User, n8n, Telegram +1

Slack & Telegram

AIPA - Multi-Business Calendar Management. Uses telegram, supabase, telegramTrigger, googleCalendar. Webhook trigger; 20 nodes.

Telegram, Supabase, Telegram Trigger +1

Slack & Telegram

AIPA - BMF Work Logging. Uses telegram, telegramTrigger, supabase, httpRequest. Webhook trigger; 19 nodes.

Telegram, Telegram Trigger, Supabase +1

Slack & Telegram

N8N Complete Final. Uses telegramTrigger, dataTable, telegram, mqtt. Event-driven trigger; 58 nodes.

Telegram Trigger, Data Table, Telegram +3