|
| 1 | +For Security Reasons we will summuray the n8n template code into text as follow: |
| 2 | +**Workflow Summary:** |
| 3 | +**Additional Processing:** |
| 4 | +- **Sticky Note4** (n8n-nodes-base.stickyNote) |
| 5 | + Details: |
| 6 | + - **Content**: |
| 7 | +```plaintext |
| 8 | +## Channel Side (Broadcasting) |
| 9 | +**This Part** where the support of brand broadcasting message to all previous users who used this bot before. |
| 10 | +``` |
| 11 | +- **Telegram-Bot** (n8n-nodes-base.telegramTrigger) |
| 12 | +- **Bot-Config** (n8n-nodes-base.set) |
| 13 | +- **Sticky Note3** (n8n-nodes-base.stickyNote) |
| 14 | + Details: |
| 15 | + - **Content**: |
| 16 | +```plaintext |
| 17 | +## User Side |
| 18 | +**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. |
| 19 | +``` |
| 20 | +- **Sticky Note2** (n8n-nodes-base.stickyNote) |
| 21 | + Details: |
| 22 | + - **Content**: |
| 23 | +```plaintext |
| 24 | +## Support Side |
| 25 | +**This Part** is meant to forward replies that sent by support (members in the group) |
| 26 | +``` |
| 27 | +- **Sticky Note1** (n8n-nodes-base.stickyNote) |
| 28 | + Details: |
| 29 | + - **Content**: |
| 30 | +```plaintext |
| 31 | +## Re Create New Topic |
| 32 | +**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). |
| 33 | +``` |
| 34 | +- **Format** (n8n-nodes-base.code) |
| 35 | +- **Bot-Fields** (n8n-nodes-base.set) |
| 36 | +- **1st** (n8n-nodes-base.switch) |
| 37 | +**Error Handling:** |
| 38 | +- **IF Verified Channel** (n8n-nodes-base.if) |
| 39 | +**Additional Processing:** |
| 40 | +- **Check User in Database1** (n8n-nodes-base.redis) |
| 41 | + Details: |
| 42 | + - **Notes**: ```plaintext |
| 43 | +Search Key``` |
| 44 | +- **Format Users** (n8n-nodes-base.code) |
| 45 | +- **Filter Blocked Users** (n8n-nodes-base.filter) |
| 46 | +- **Split In Batches1** (n8n-nodes-base.splitInBatches) |
| 47 | + Details: |
| 48 | + - **Notes**: ```plaintext |
| 49 | +Telegram Limitation 29/sec``` |
| 50 | + |
| 51 | +**Data Fetching and Processing:** |
| 52 | +- **Broadcast Channel Post into Users** (n8n-nodes-base.httpRequest) |
| 53 | +**Additional Processing:** |
| 54 | +- **Set Blocked Member** (n8n-nodes-base.redis) |
| 55 | +- **Wait1** (n8n-nodes-base.wait) |
| 56 | +**Error Handling:** |
| 57 | +- **Support Forum** (n8n-nodes-base.if) |
| 58 | +- **From Ticket** (n8n-nodes-base.if) |
| 59 | +- **IF Topic Created** (n8n-nodes-base.if) |
| 60 | +**Additional Processing:** |
| 61 | +- **Send User Ticket Created Notification** (n8n-nodes-base.telegram) |
| 62 | +**Data Fetching and Processing:** |
| 63 | +- **Forward Support Reply To User** (n8n-nodes-base.httpRequest) |
| 64 | +**Additional Processing:** |
| 65 | +- **Check User in Database** (n8n-nodes-base.redis) |
| 66 | + Details: |
| 67 | + - **Notes**: ```plaintext |
| 68 | +Search Key``` |
| 69 | + |
| 70 | +**Error Handling:** |
| 71 | +- **New User ?** (n8n-nodes-base.if) |
| 72 | +**Additional Processing:** |
| 73 | +- **Update User Data** (n8n-nodes-base.redis) |
| 74 | +- **Get User Chat Topic** (n8n-nodes-base.redis) |
| 75 | +- **Save User Data** (n8n-nodes-base.redis) |
| 76 | +**Data Fetching and Processing:** |
| 77 | +- **Create Topic (Chat Ticket)** (n8n-nodes-base.httpRequest) |
| 78 | +**Additional Processing:** |
| 79 | +- **Save Topic ID** (n8n-nodes-base.redis) |
| 80 | +**Data Fetching and Processing:** |
| 81 | +- **Forward New Message** (n8n-nodes-base.httpRequest) |
| 82 | +**Error Handling:** |
| 83 | +- **IF No Topic Created** (n8n-nodes-base.if) |
| 84 | +**Data Fetching and Processing:** |
| 85 | +- **ReCreate Topic (Chat Ticket)** (n8n-nodes-base.httpRequest) |
| 86 | +**Additional Processing:** |
| 87 | +- **ReSave Topic ID** (n8n-nodes-base.redis) |
| 88 | +**Data Fetching and Processing:** |
| 89 | +- **Forward New Message to the recrated topic** (n8n-nodes-base.httpRequest) |
| 90 | +**Additional Processing:** |
| 91 | +- **No Operation, do nothing** (n8n-nodes-base.noOp) |
| 92 | +- **Sticky Note** (n8n-nodes-base.stickyNote) |
| 93 | + Details: |
| 94 | + - **Content**: |
| 95 | +```plaintext |
| 96 | +## Use **Config Bot** to setup your telegram details, like: |
| 97 | +1- Telegram Group ID (Don't forget add bot as admin) |
| 98 | +2- Telegram Channel ID (Don't forget add bot as admin) |
| 99 | +3- Your telegram Bot Token. (Generate through @BotFather) |
| 100 | +
|
| 101 | +
|
| 102 | +
|
| 103 | +
|
| 104 | +
|
| 105 | +
|
| 106 | +
|
| 107 | +
|
| 108 | +
|
| 109 | +
|
| 110 | +## Setup data & filter & route to the correct Side. |
| 111 | +0- None of them - Soon - Wait V2 |
| 112 | +1- Chat Type (`Private`) |
| 113 | +2- Chat Type (`Supergroup`) |
| 114 | +3- Chat Type (`Channel`) |
| 115 | +
|
| 116 | +
|
| 117 | +
|
| 118 | +
|
| 119 | +
|
| 120 | +
|
| 121 | +
|
| 122 | +
|
| 123 | +
|
| 124 | +
|
| 125 | +
|
| 126 | +
|
| 127 | +
|
| 128 | +
|
| 129 | +
|
| 130 | +## Remember: |
| 131 | +* Do not make your support group public. Every message sent in the group on various topics will be forwarded to the user's ticket. |
| 132 | +* There is no need to promote your broadcasting channel; the main reason for the channel is to organize and broadcast messages. |
| 133 | +* You can host a Redis database without any coding/server management skills through Coolify.io. |
| 134 | +* In the next version, I will add the **edit messages** feature, where the forwarded messages will be updated with the new edited one. |
| 135 | +## Why use this method? |
| 136 | +* 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. |
| 137 | +* 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. |
| 138 | +* 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. |
| 139 | +``` |
0 commit comments