Another Cloudflare Workers Telegram Bot is inspired by cvzi/telegram-bot-cloudflare. This is wrapped up as a class to make it easy to to used like any NPM library. You can handle telegram update the way you wish by override onUpdate method.
Examples are about the same demos from cvzi/telegram-bot-cloudflare.
- Get your new bot token from @BotFather: https://core.telegram.org/bots#6-botfather
- Sign up to Cloudflare Workers: https://workers.cloudflare.com/
- In the Cloudflare Dashboard go to "Workers", then click "Create application" and then "Create worker"
- Choose a name and click "Deploy" to create the worker
- Click on "Configure worker" -> "Settings" -> "Variables"
- Add a new variable with the name
ENV_BOT_TOKEN
and the value of your bot token from @BotFather - Add a new variable with the name
ENV_BOT_SECRET
and set the value to a random secret. See https://core.telegram.org/bots/api#setwebhook - Click on "Quick Edit" to change the source code of your new worker
- Copy and paste the code from bot.js into the editor
- Add new file named telegram-bot.js and copy code from telegram-bot.js into the editor again
- Optional: Change the
WEBHOOK
variable to a different path. See https://core.telegram.org/bots/api#setwebhook - Click on "Save and Deploy"
- In the middle panel append
/registerWebhook
to the url. For example: https://my-worker-123.username.workers.dev/registerWebhook - Click "Send". In the right panel should appear
Ok
. If 401 Unauthorized appears, you may have used a wrong bot token. - That's it, now you can send a text message to your Telegram bot
- open any shell and put command:
npm create [email protected] "YOUR_NEW_PROJECT_FOLDER_PATH"
- Choose
"Hello World" Worker
for type of application - Choose
No
for not to use TypeScript - Choose if you like to use git for version control?
No
if you aren't sure - Choose
No
for not to deploy yet - Copy content of bot.js to overwrite all content of src/index.js
- Copy telegramBot.js to src/ folder
- add env variables to wrangler.toml like below
[vars]
ENV_BOT_TOKEN= "1234567890:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" # bot token from [@BotFather](https://t.me/botfather)
ENV_BOT_SECRET= "ANY_RANDOM_WORDS" # See https://core.telegram.org/bots/api#setwebhook
- cd to
YOUR_NEW_PROJECT_FOLDER_PATH
and put command:npm run deploy
- command:
curl "https://my-worker-123.username.workers.dev/registerWebhook"
. You can find your worker url at step 8. - You should see
Ok
in step 9. If 401 Unauthorized/404 Not Fount appears, you may have used a wrong bot token.
The bot will send the original message back with Echo:
prepended.
If you want to change it, look at the function onMessage()
. It receives a Message object and sends a text back:
/**
* Handle incoming Message
* https://core.telegram.org/bots/api#message
*/
function onMessage(message) {
return bot.sendPlainText(message.chat.id, `Echo:\n${message.text}`);
}
The file example_inlineButtons.js contains an improved bot, that demonstrates how to react to commands, send and receive inline buttons, and create MarkdownV2-formatted text.
The file example_inlineQueriesAndVoice.js contains an improved version that replies inline queries with voice messages.
The voice messages should be stored in OPUS format and .ogg in the cloud you most like.
The audio files are listed in a JSON array with the following structure in a KV namespace called NAMESPACE
and with following content under the key input_files
.
Go to Workers & Pages -> KV and create a new namespace. Add a new key input_files
and store the JSON structure from below with your own audio files.
Now in Overview -> your-worker -> Settings -> Variables -> KV Namespace Bindings bind the namespace to a variable called NAMESPACE
.
[
[
"File Name",
"URL",
duration,
"<tg-spoiler> caption </tg-spoiler>"
],
[
"test",
"https://example.com/my_file.ogg",
5,
"<tg-spoiler>Description in a spoiler</tg-spoiler>"
],
]
The file example_reaction,js is a bot that randomly reacts to messages received. It demostrates how to use big reactions when the ๐ emoji gets chosen.