Telegram chat access control with user permission database
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 11 nodes and runs on Telegram events (message) (plus 1 other trigger). Along the way it connects Telegram, Slack, Google Sheets and Airtable and 1 more.
How it runs
Trigger: On Telegram events (message) (plus 1 other trigger).
- Database with employees (Data table): get
- Permission (Switch): routes items into 2 branches
- Answer Denied (Telegram): uses Telegram
- Get row(s) in sheet (Google Sheets): uses Google Sheets
- Get a record (Airtable): uses Airtable
- Get a database page (Notion): get (database page)
- If: checks a condition and branches into true / false
- Filter: keeps only the items that match a condition
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.
- Still check Slack Trigger requires a signing secret on the Slack API credential (Slack Trigger).
Nodes used (11)
- No Operation, do nothing
n8n-nodes-base.noOp - Switch
n8n-nodes-base.switch - Telegram
n8n-nodes-base.telegram - Telegram Trigger
n8n-nodes-base.telegramTrigger - Slack Trigger
n8n-nodes-base.slackTrigger - Google Sheets
n8n-nodes-base.googleSheets - Airtable
n8n-nodes-base.airtable - Notion
n8n-nodes-base.notion - If
n8n-nodes-base.if - Filter
n8n-nodes-base.filter - Data table
n8n-nodes-base.dataTable
From the author
🔐 n8n Workflow: Access Control for Internal Chats or Chatbots This n8n workflow helps you restrict access to your internal chats or chatbots so that only authorized team members can interact with them. It's perfect for setups using Telegram, Slack, or other…