Source

Governance, credentials & audit trail — found from sitemap — n8n

Checked for n8n on 13 Oct 2026

Page: https://n8n.io/workflows/10171-role-based-access-control-rbac-for-telegram-automations/
Checked: 13 Oct 2026, 17:15 UTC
How we may use it: Public page, crawling permitted

Technical details

type: page
http status: 200
content hash: sha256:fb53cd87b79abb266c53f1b550992dc41f8f738d2311a34abe8fea4ece2cdc0d
permission: robots_ok
screenshot: Screenshot on file (internal exhibit, not published)

Cited by

Rbac telegram workflow Report an error

“This n8n workflow lets you control access to your internal Telegram bots and automation systems based on user roles and departments.”
Trigger telegram Report an error

“⚡ Receive Message (Telegram Trigger) Purpose: Captures incoming messages from users interacting with your Telegram bot.”
Employee database lookup Report an error

“📋 Employee Database (Data Table Node) Purpose: Fetches user details such as Position and Type from your internal employee table.”
Position role check Report an error

“🧩 Choose Position (Switch Node) Purpose: Determines the user’s department or role level (e.g., Marketing, Sales, Administration). 🧩 Check Role Type (Switch Node) Purpose: Performs a second-level check — filters users by Type (e.g., SEO, SMM, Target).”
Role logic paths Report an error

“Marketing → SEO → Send to SEO workflow branch Marketing → Target → Send to Ads branch Administration → Manager → Grant full access Sales → Employee → Limited access”
Action routing Report an error

“💬 No Operation Nodes (Placeholders) Purpose: Represent different action branches — each can later be replaced with the logic specific to that department.”
Cross platform adaptable Report an error

“📈 Cross-Platform Ready: Can be adapted for Slack, Discord, or internal chat tools.”
Author Report an error

“CREATED BY Yehor EGMS LAST UPDATE Last update 8 months ago”

2 facts read from this page are not shown because they could not be confirmed on the page as captured.