Role-based access control (RBAC) for Telegram automations
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 17 nodes and runs on Telegram events (message) (plus 3 other triggers). Along the way it connects Telegram, Slack, Google Sheets and Airtable and 1 more.
How it runs
Trigger: On Telegram events (message) (plus 3 other triggers).
- Employee database (Data table): get
- Choose Position (Switch): routes items into 3 branches
- Switch: routes items into 3 branches
- 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 (12)
- Telegram Trigger
n8n-nodes-base.telegramTrigger - No Operation, do nothing
n8n-nodes-base.noOp - Switch
n8n-nodes-base.switch - Data table
n8n-nodes-base.dataTable - 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 - n8n Form Trigger
n8n-nodes-base.formTrigger - Schedule Trigger
n8n-nodes-base.scheduleTrigger
From the author
🔐 n8n Workflow: Role-Based Access Control (RBAC) for Telegram Automations This n8n workflow lets you control access to your internal Telegram bots and automation systems based on user roles and departments. It ensures that only authorized team members —…