Verify Telegram channel subscriptions with access control using Postgres
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 41 nodes and runs on Telegram events. Along the way it connects Telegram, Postgres and Google Drive.
How it runs
Trigger: On Telegram events.
- Variables TG (Edit Fields (Set)): sets or maps fields
- Initialization (Edit Fields (Set)): sets or maps fields
- Is Admin? (If): checks a condition and branches into true / false
- Define Type (Switch): routes items into branches
- Buttons (Switch): routes items into branches
- Get Bot Status (Postgres): uses Postgres
- Update bot status on START (Postgres): uses Postgres
- Define flow (Switch): routes items into branches
- Success (Telegram): uses Telegram
- Commands (Switch): routes items into branches
…plus 30 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 (9)
- Telegram
n8n-nodes-base.telegram - Postgres
n8n-nodes-base.postgres - Aggregate
n8n-nodes-base.aggregate - If
n8n-nodes-base.if - Google Drive
n8n-nodes-base.googleDrive - Edit Fields (Set)
n8n-nodes-base.set - Telegram Trigger
n8n-nodes-base.telegramTrigger - Switch
n8n-nodes-base.switch - Summarize
n8n-nodes-base.summarize
From the author
Who is this for? This workflow is for Telegram bot developers or marketers who want to verify user subscriptions to specific Telegram channels and optionally reward them with downloadable files. What problem is this workflow solving? This workflow ensures…