Turn your Telegram bot into a simple help desk. Every user message becomes a ticket inside a forum topic in your support group, and team replies go back to the user chat. Great for brands that support customers on Telegram and want clear threads, fast replies, and safe chat history.

Under the hood, a Telegram event starts the flow. User and chat data are cleaned, then stored in Redis with the user id. If the user is new, a forum topic is created in the support group and the topic id is saved. Messages are forwarded into the correct topic. If a topic was deleted, the system creates a new one and tries again. Replies from the support group thread are sent back to the user. A broadcast path also takes channel posts, pulls all saved users from Redis, filters blocked users, and sends messages in batches with a wait step to respect Telegram limits.

You need a Telegram bot, a forum supergroup for support, a channel for announcements, and a Redis database. Add the bot as an admin to the group and channel. Expect faster handling, better context for every case, and no lost history if someone deletes messages. Use it for customer support, pre sales questions, and channel to user announcements with safe rate control.

• Telegram event trigger listens to private chats, group threads, and channel posts.
• Creates a forum topic per user in the support group and saves the topic id.
• Stores and updates user profiles and thread ids in Redis for fast access.
• Forwards new user messages into the correct forum thread for team handling.
• Recreates a topic automatically if it was deleted and retries the forward.
• Relays support replies from the forum thread back to the user chat.
• Broadcasts channel posts to all saved users using batches and a wait step to respect limits.
• Sends a ticket created notice to the user when a new thread is opened.

• Reduce manual ticket sorting from hours each day to a few minutes by auto creating topics per user.
• Protect chat history by keeping a copy in the support group even if a user deletes their messages.
• Streamline message routing and replies to cut response time from minutes to seconds.
• Respect Telegram limits with batching and waiting so you can handle high volume safely.
• Unify user data in Redis for quick lookup and consistent routing.

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Telegram and Redis. See the Tools Required section above for links to create accounts with these services.
3. Create a Telegram bot with BotFather and copy the bot token.
4. In the n8n credentials manager, double click the Telegram nodes and create new Telegram credentials. Paste the bot token and save.
5. Prepare a Telegram forum supergroup for support and a channel for broadcasts. Add the bot as an admin in both. Copy the group id and channel id.
6. Open the Bot-Config node in n8n and fill in BotToken, Support Group ID, and Channel ID fields.
7. Set up Redis in the n8n credentials manager. Create a new Redis credential and enter host, port, password, and enable SSL or TLS if your provider uses it.
8. Activate the workflow so the Telegram webhook is registered by the Telegram trigger node.
9. Send a private message to your bot. Check your support group for a new forum topic and confirm you receive a ticket created message.
10. Reply in the created forum thread from the support group. Confirm the reply is delivered to the user chat.
11. Test recovery by deleting the forum thread. Send another user message and confirm a new topic is created and the message is forwarded.
12. Post a message in the linked channel. Verify users stored in Redis receive the broadcast in batches and that waits occur between batches.
13. Troubleshoot thread not found errors by confirming the group is a forum supergroup and the bot is admin. If some sends fail, check the Filter Blocked Users and Set Blocked Member nodes.
14. Open Redis and confirm keys like TG-USER user id exist and include a message_thread_id value.