You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@
13
13
...
14
14
15
15
16
-
This package contains a node which act as a Telegram Client. It is based on gramjs which implements the mtproto mobild protocol. (see https://core.telegram.org/mtproto). Unlike node-red-contrib-telegrambot it does not support the telegram bot api. The package can be used to create so-called userbots or selfbots which to automate things under your own user-name. However you should be aware of the fact, that if you cause flooding and other havoc telegram will quickly ban your account either for 24h or even forever. It is recommended to use a test account while developing.
16
+
This package contains a node which act as a Telegram Client. It is based on gramjs which implements the mtproto mobile protocol. (see https://core.telegram.org/mtproto). Unlike node-red-contrib-telegrambot it does not support the telegram bot api. The package can be used to create so-called userbots or selfbots which to automate things under your own user-name. However you should be aware of the fact, that if you cause flooding and other havoc telegram will quickly ban your account either for 24h or even forever. It is recommended to use a test account while developing.
17
17
18
18
19
19
# Thanks for your donation
@@ -53,14 +53,15 @@ Changes can be followed [here](/CHANGELOG.md).
53
53
## Basics
54
54
### Authentication
55
55
The *Telegram client receiver* node receives messages from like a telegram client. You need to login with a phone-number and an API ID and API Hash in order to be able to receive message under your own user name.
56
+
In addition to that you can also login using a bot token retrieved from @botfather.
56
57
57
58
You can create an API ID and Hash when you login to your telegram account here https://my.telegram.org/auth
58
59
Then go to 'API Development Tools' and create your API ID and API Hash. Both are required when configuring your nodes. The nodes login only once to create a so-called session string. This string can be created from within
59
60
the config node or as an alternative you can also create it online here https://tgsnake.js.org/login
60
61
This session string is used instead of interactive login (where you need to enter a phone-code and your password if set).
61
62
62
63
### Receiver Node
63
-
The *Telegram client receiver* node receives message which are sent to your account. Just add a debug node to the
64
+
The *Telegram client receiver* node receives message which are sent to your account or bot. Just add a debug node to the
64
65
output and investigate the objects in `msg.payload`.
<inputtype="text"id="node-config-input-bottoken"placeholder="(Enter the bot token from botfather here)">
158
+
<divclass="form-tips"style="width: auto"><b>Tip:</b> If you don't have a token yet, you can create a new one here: <ahref="https://t.me/BotFather">@BotFather</a>.</div>
0 commit comments