Use Config Bot to setup your telegram details, like:
Configured with Filter, HTTP Request, Redis, Loop Over Items, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Routing
- Code
- Transform
- Web / API
- Data store
- Messaging
- Trigger
- Wait
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| New User ? | Routing | If | See node parameters |
| Format | Code | Code | See node parameters |
| Bot-Fields | Transform | Edit Fields | See node parameters |
| Create Topic (Chat Ticket) | Web / API | HTTP Request | See node parameters |
| Save Topic ID | Data store | Redis | set |
| Get User Chat Topic | Data store | Redis | get |
| Forward New Message | Web / API | HTTP Request | POST |
| IF No Topic Created | Routing | If | See node parameters |
| ReCreate Topic (Chat Ticket) | Web / API | HTTP Request | See node parameters |
| ReSave Topic ID | Data store | Redis | set |
| Update User Data | Data store | Redis | set |
| Save User Data | Data store | Redis | set |
| Support Forum | Routing | If | See node parameters |
| From Ticket | Routing | If | See node parameters |
| Forward Support Reply To User | Web / API | HTTP Request | POST |
| IF Topic Created | Routing | If | See node parameters |
| Forward New Message to the recrated topic | Web / API | HTTP Request | POST |
| No Operation, do nothing | Routing | No Op | See node parameters |
| Check User in Database | Data store | Redis | keys |
| Send User Ticket Created Notification | Messaging | Telegram | See node parameters |
| Bot-Config | Transform | Edit Fields | See node parameters |
| Telegram-Bot | Trigger | Telegram Trigger | See node parameters |
| 1st | Routing | Switch | See node parameters |
| Split In Batches1 | Routing | Loop Over Items | See node parameters |
| Wait1 | Wait | Wait | See node parameters |
| Format Users | Code | Code | See node parameters |
| Broadcast Channel Post into Users | Web / API | HTTP Request | POST |
| Set Blocked Member | Data store | Redis | set |
| IF Verified Channel | Routing | If | See node parameters |
| Filter Blocked Users | Routing | Filter | See node parameters |
| Retrieve all users in DB | Data store | Redis | keys |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
redistelegramApi
Workflow notes
Use **Config Bot** to setup your telegram details, like:
Use Config Bot to setup your telegram details, like:
1- Telegram Group ID (Don't forget add bot as admin) 2- Telegram Channel ID (Don't forget add bot as admin) 3- Your telegram Bot Token. (Generate through @BotFather)
Setup data & filter & route to the correct Side.
0- None of them - Soon - Wait V2
1- Chat Type (Private)
2- Chat Type (Supergroup)
3- Chat Type (Channel)
Remember:
- Do not make your support group public. Every message sent in the group on various topics will be forwarded to the user's ticket.
- There is no need to promote your broadcasting channel; the main reason for the channel is to organize and broadcast messages.
- You can host a Redis database without any coding/server management skills through Coolify.io.
- In the next version, I will add the edit messages feature, where the forwarded messages will be updated with the new edited one.
Why use this method?
- If you deal with Telegram P2P, anyone can delete messages from both sides. If you run a business, then one of your clients may delete all messages, causing you to lose the history. This solution prevents people from deleting messages; every message forwarded into the support group will not be possible to delete by the sender.
- Team collaboration: Why share one account when you can convert the whole group into a ticketing system? With this project, you can invite all your coworkers to reply and provide support to your clients through Telegram.
- Integrate with third-party services? Using N8N will pave the way for integrating your Telegram users' data into a CRM. In V2, we will enable the option to force new users to share their leads before receiving support.
Re Create New Topic
Re Create New Topic
Sometimes in support group may the team delete or close a ticket (topic) in case of that this steps will create topic again for the user, and store the new ticket id (topic/thread ID).
Check User in Database
Search Key
Support Side
Support Side
This Part is meant to forward replies that sent by support (members in the group)
User Side
User Side
This Part is meant to save user data on a RAM database which is fast, and in same time forward the message to support after creating a new ticket (Topic) dedciated for the user id in the support group.
Split In Batches1
Telegram Limitation 29/sec
Channel Side (Broadcasting)
Channel Side (Broadcasting)
This Part where the support of brand broadcasting message to all previous users who used this bot before.
Use Config Bot to setup your telegram details, like:
Use Config Bot to setup your telegram details, like:
Purpose and structure
This folder contains the Use Config Bot to setup your telegram details, like: workflow. Its executable nodes use code, filter, httpRequest, if, noOp, redis, set, splitInBatches, switch, telegram, telegramTrigger, wait. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Telegram-Bot
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Telegram/0383_Telegram_Wait_Create_Webhook.json MIT; preserve source notices.