Advanced Telegram Ticketing, Live Chat, and Broadcast System - n8n Workflow

Businesses seeking to centralize Telegram support operations into a multi-agent ticketing system.
Developers who need reliable, stateful user management for their Telegram bots.
Users looking for advanced n8n templates combining API calls, flow control, and external databases (Redis).
Support teams requiring a streamlined workflow for handling client conversations and large-scale message broadcasts.

This advanced n8n workflow provides a robust solution for running a comprehensive customer support system directly through Telegram. By leveraging the forum topic feature in Telegram Supergroups and using Redis for fast, stateful user data storage, this n8n automation creates a dedicated 'ticket' (topic) for every new user interaction. The primary problem this solves is enabling team collaboration: instead of sharing a single bot account, your entire support group can reply to individual customer threads, with all messages seamlessly forwarded back to the client's private chat. Furthermore, the n8n workflow includes built-in broadcasting capabilities, allowing you to send messages from a verified channel to all previously engaged users, while respecting Telegram's strict rate limits using the split in batches n8n node. This particular n8n workflow demonstrates complex flow control and external database integration, making it one of the more comprehensive n8n templates available.

The entire process is initiated by the Telegram-Bot n8n trigger when a new message or channel post is received.

1. Data Preparation: The incoming data is sanitized and formatted using a Code n8n node, then essential bot configuration parameters (token, group IDs) are applied.


2. Flow Routing: A Switch n8n node routes the flow based on the chat type (Private, Supergroup, Channel).


3. Private Chat (User Side): The workflow checks the Redis database for the user's existence. If it's a new user, the n8n workflow saves the data, creates a new support topic (ticket) in the designated group via an HTTP Request n8n node, saves the new topic ID in Redis, and forwards the message. If the user is existing, the workflow retrieves their stored topic ID and forwards the message directly. If the original topic was deleted, error handling logic automatically recreates the topic to ensure continuity.


4. Supergroup Chat (Support Side): If the message originates from the support group and is a reply within a ticket thread, the n8n workflow forwards that reply back to the original user's private chat using an HTTP Request n8n node, completing the live chat loop.


5. Channel Post (Broadcasting): If a post comes from the designated broadcast channel, the n8n workflow retrieves all stored user IDs from Redis. It then filters out any users marked as 'Blocked'. To comply with Telegram API limits, the Split In Batches n8n node segments the users into batches of 29, forwarding the message to each user and applying a time delay via a Wait n8n node, ensuring smooth, large-scale delivery.

1. Import the n8n workflow: Copy the provided JSON data and paste it into your n8n instance using the 'New' -> 'Import from JSON' feature.


2. Configure Credentials: Set up your Telegram API credentials in the Telegram-Bot n8n trigger and the Send User Ticket Created Notification n8n node. You will also need to configure credentials for the Redis n8n node (used for database operations).


3. Update Configuration Node: Open the 'Bot-Config' Set n8n node and replace the placeholder values with your actual Telegram Bot Token, Support Group ID, and Broadcast Channel ID. Note that the bot must be an administrator in both the support group and the channel.


4. Activate: Ensure all necessary connections are configured. Activate the n8n workflow to start listening for Telegram updates.

Telegram-Bot (n8n trigger): The starting point of this n8n workflow, configured to listen for 'message' and 'channel_post' updates from Telegram users and channels.
Bot-Config (Set n8n node): Stores critical variables (Bot Token, Support Group ID, Channel ID) that are referenced throughout the entire n8n workflow for dynamic API calls.
Format & Bot-Fields (Code & Set n8n nodes): These nodes clean, flatten, and sanitize the complex Telegram JSON payload, making it safe and efficient for storage in the Redis database.
Redis (Multiple n8n nodes): Crucial for state management. Used to check if a user is new, save their profile data, retrieve the specific chat topic (ticket) ID, and retrieve all users for broadcasting. This ensures a persistent customer history.
HTTP Request (Multiple n8n nodes): Directly executes actions against the Telegram Bot API, such as createForumTopic, forwardMessage, and copyMessage (for broadcasting).
New User ? & Support Forum (If n8n nodes): Essential components of the core logic flow control, directing traffic based on whether the user is new or if the message originated from the support team.

• Split In Batches (n8n node): Used in the broadcasting path to split the list of users into smaller chunks (batch size 29) to prevent hitting Telegram's API rate limits. This is followed by a Wait n8n node to introduce necessary delays.