Telegram Bot User Access Management and Permission Gate - n8n Workflow

Ideal Users

Automation Developers: Building internal tools or sensitive automations that should only be accessible to specific users.
System Administrators: Needing to implement a simple yet effective user permission layer for team communication bots.

• n8n Users: Looking for advanced n8n workflow templates that demonstrate robust conditional logic and external data lookups.

This essential n8n workflow solves the common problem of unauthorized usage in automated Telegram bots. If you are leveraging n8n to build services that interact via Telegram, establishing a reliable security boundary is crucial. This n8n templates solution provides a robust, instantaneous permission layer. It uses the Telegram Trigger n8n node to detect incoming messages and then connects to a user database (like an n8n Data Table) to verify the sender's identity and access level. This specific n8n workflow ensures that only users explicitly marked as 'Granted' can proceed to the main automation logic, while others are immediately denied access. By utilizing a switch n8n node for filtering, this approach creates reliable security and granular control over your automated processes.

The entire process is initiated by the Telegram Trigger, which functions as the primary n8n trigger for the automation.

1. Trigger Reception: The Telegram Trigger n8n node listens for incoming messages on your configured Telegram bot.


2. User Extraction and Lookup: Once a message is received, the workflow extracts the sender's username. The 'Database with employees' n8n node (an n8n Data Table) performs a lookup, searching for a record where the stored UserName matches the sender's username.


3. Permission Evaluation: The 'Permission' n8n node, a core Switch component, evaluates the Access status returned from the Data Table. It checks if the value is 'Granted' or 'Denied'.


4. Granted Access: If the status is 'Granted', the flow follows the success path to the 'No Operation, do nothing' node. This is where the user connects their main n8n workflow logic that requires restricted access.


5. Denied Access: If the status is 'Denied', the flow proceeds to the 'Answer Denied' Telegram n8n node, which sends a configured message ('Access denied') back to the user’s chat, thus preventing unauthorized interaction with the underlying n8n automation.

To deploy this powerful n8n workflow, follow these setup steps:

1. Import: Copy the provided n8n workflow JSON and import it into your n8n instance.


2. Telegram Credentials: Obtain a bot token from BotFather in Telegram. Create a new Telegram API Credential in n8n and paste your token.


3. Configure Telegram Trigger: Open the 'Telegram Trigger' n8n node and select your newly created Telegram API credential.


4. Data Table Setup: Create an n8n Data Table containing at least two columns: UserName (matching Telegram usernames) and Access (containing 'Granted' or 'Denied').


5. Configure Database Lookup: In the 'Database with employees' n8n node, select the Data Table ID you just created. Ensure the filter is correctly set to look up records where UserName matches {{ $json.message.from.username }}.


6. Activate: Save and activate the n8n workflow (set Active: ON). Send test messages from permitted and restricted users to verify the access control logic.

This n8n workflow utilizes several key components to manage the access logic:

Telegram Trigger: Function: Acts as the primary n8n trigger, initiating the workflow upon receiving any Telegram message. Key Configuration: Uses specific Telegram API credentials; configured to listen for message updates.
Database with employees (n8n Data Table): Function: Looks up the user's access status based on their Telegram username. Key Configuration: Uses a filter condition (UserName equals {{ $json.message.from.username }}) to fetch the relevant row.
Permission (Switch n8n node): Function: Implements the core access control logic, routing the flow based on the database result. Key Configuration: Checks the incoming data field {{ $json.Access }} and routes to 'Granted' or 'Denied' outputs.
Answer Denied (Telegram n8n node): Function: Sends a denial message back to the user if access is restricted. Key Configuration: Sends the message 'Access dinied' to the originating chat ID ({{ $('Input Data').item.json.message.chat.id }}).

• No Operation, do nothing: Function: Acts as a successful placeholder. Any logic connected here will execute only if the user is 'Granted' access. This simple n8n node ensures a smooth transition to your subsequent automation steps.