How to build a Telegram Bot with NodeJS

6 min read

On a whim I decided I wanted to learn about how to make a bot on the popular messenger app Telegram. Really wasn’t all that hard I just had no idea what I really wanted this thing to do. I was playing around with the API for a few hours and decided to make my mark on the platform with @ChuckNorrisJokeBot. Yes I am a fan of these jokes they make me belly laugh 😂

Getting Started

Being that the only language I know that was available for use was JavaScript this is being built using NodeJS, specifically I opted to use the micro-bot framework which is similar to the concept of MicroJS which I’m already quite familiar with and like a lot. Micro-bot is built upon the NodeJS library for the Telegram API called Telegraf which I felt was much easier to work with then the several other NodeJS libraries available.

yarn create bot telegram_chuck_norris_bot
cd telegram_chuck_norris_bot

You will need an account with Telegram. It’s not very hard to setup just download the app on iOS/Android/MacOS/Windows/Linux and follow the instructions. Seriously though if you aren’t using Telegram you should be for many many reasons…privacy and data security being just two.

Creating a New Bot with Telegram

Telegram has “one bot to rule them all” called @BotFather. Search for @BotFather and click start he will give you a help menu of all the options you have with him and you should then type in /newbot. You will be prompted for a name and a username for the bot (this must end in bot). Once you have created your bot you will be give a BOT_TOKEN that you will use to work with the Telegram Bot API. This needs to be kept secret and safe so choose to handle your environment variables however you like to do so. Micro-bot actually has a few flags one being -t for passing your token to the command and -e for any other environment variables you might have. You could do something such as:

	"scripts": {
		"start": "micro-bot -t BOT_TOKEN -d DOMAIN -e MY_ENVVAR"

Micro-bot requires that you pass it a token and a domain for the bot to run on and these are already recognized as process.env.BOT_TOKEN and process.env.BOT_DOMAIN. In this tutorial we are going to deploy from CircleCi to the Now platform.

Writing the code for Chuck Norris to kick @$$

The Chuck Norris API is super easy to use and requires no API key to use so it is about as K.I.S.S (Keep It Simple Stupid) as it gets. We will just use the random joke endpoint for the bot and use the isomorphic-fetch package, which FYI is native to node, but not in a CI container…doh! Because this is 2018 we are not interested in callback hell or then/catch chains. No sir we are gonna use that shiny ESNext syntax async/await. We set this up to only return the joke because we want the bot to just tell a joke and have no need for other data here.

yarn add isomorphic-fetch
const fetch = require('isomorphic-fetch')
const { parseString } = require('./utils')
const fetchRandomJoke = async () => {
	try {
		const res = await fetch('')
		const data = await res.json()
		if (data.type === 'success') {
			return parseString(data.value.joke)
	} catch (e) {
		throw new Error(
			"Chuck Norris doesn't throw errors, he throws roundhouse kicks!"
module.exports = {

Due to the JSON data quotes will come back as &quot so we need to replace this with actual quote symbols that is where parseString comes in. We will use the .includes() method to check that the joke string does or does not contain the problemChild and if it doesn’t just return the joke or run the .replace() method on the joke and look for our problemChild and replace it with the desired output.

const problemChild = /"/g
const parseString = str => {
	if (str.includes('&quot')) {
		return str.replace(problemChild, '"')
	return str
module.exports = {

The Bot

Micro-bot exposes the Telegraf API to us in a few different manner and we will be using the Composer class. In the design of micro will will be exporting a single entry point or function as the surface of our Bot’s API.

const { Composer } = require('micro-bot')
const app = new Composer()
module.exports = app

Telegram’s Bot API is designed so that the only way bots can interact with user’s is through user’s interacting with the bots. No bot can message or interact with a user without a command being sent to it by the user.

app.command('our_command', ctx => ourHandler(ctx))

Specifically Telegram’s API states that users will see a Start Button to begin interacting with your bot and that these global commands are available to you for use by default. We will send the user a start up message when they tap the start button that will tell the user who our bot is and what it does.

const { Composer, Markup } = require('micro-bot')
const app = new Composer()
app.command('start', ({ botInfo, replyWithMarkdown, update }) =>
		messages.start(botInfo, update),
		Markup.keyboard(['Tell me something funny Chuck']).resize().extra()
Get started talking with Chuck.

Listening for the user’s response

Now we just need to implement a listener for the user’s response of asking for a joke. This is where our function for making an API call to the Chuck Norris API will come into play. Since the function is an asynchronous function we will make sure to use the async/await syntax here:

app.hears('Tell me something funny Chuck', async ({ replyWithMarkdown }) => {
	const joke = await Chuck.fetchRandomJoke()
Tell me a joke Chuck!

Adding information about your bot

Through @BotFather we can use commands to add information about our bot such as /setdescription, /setabouttext, /setuserpic, etc.

Screen with all the info about Chuck.

Deploying the bot

I decided to write tests that can be found here and use CircleCi to handle the deployment of the bot. Providing the BOT_TOKEN & NOW_TOKEN to CircleCi we can easily kickback and let it manage making sure our bot is ready for production before shipping. The full config.yaml can be found here.

    - image: 'circleci/node:latest'
  working_directory: ~/telegram_chuck_norris_bot
    - attach_workspace:
        at: ~/telegram_chuck_norris_bot
    - run: yarn install
    - run: sudo yarn global add now
    - deploy:
        name: Deploy Bot.
        command: |
          if [ "${CIRCLE_BRANCH}" == "master" ]; then
            now -t ${NOW_TOKEN} -e BOT_TOKEN=${BOT_TOKEN} -n=telegram_chuck_norris_bot
            now -t ${NOW_TOKEN} alias telegram_chuck_norris_bot_v1
          elif [ "${CIRCLE_BRANCH}" == "development" ]; then
            now -t ${NOW_TOKEN} -e BOT_TOKEN=${BOT_TOKEN} -n=telegram_chuck_norris_bot
            now -t ${NOW_TOKEN} alias telegram_chuck_norris_bot_beta
            echo "This failed miserably!"

Wrap Up

Overall it’s not very hard to get a bot deployed to Telegram there is far more you can do so I highly recommend you go checkout the docs on the Bots API and play around with it. I’m really interested in building a bot that will work with an Ethereum smart contract now or maybe waiting to see what Telegram does with their own coming crypto-currency Telegram Open Network (TON). Source code can be found here.

Give ol’Chucky a try if you are on Telegram @ChuckNorrisJokeBot!

~ Cody 🚀

Related Articles

    Going to the Gopher Side

    The chaos that is the JavaScript/TypeScript ecosystem has become too much to bear in my opinion. I have become unhappy with my direction in the tech industry and in late 2023 made the decision to begin teaching myself Go and pivoting my career out of the Frontend & away from JavaScript.

Cody Brunner

Cody is a Christian, USN Veteran, Jayhawk, and an American expat living outside of Bogotá, Colombia where he works as a Senior Frontend Developer for WAO Fintech.