Modules¶

Imagine npm packages that already live inside your bot — no require(), no package.json, no "works on my machine" excuses. That's modules.

Hash a password, sign a JWT, parse a CSV, check if an email looks real, grab the BTC price — all from your command's Logic field. Type modules. and autocomplete your way to happiness.

What are modules?¶

Modules are curated third-party utilities (JWT, bcrypt, lodash, zod, ethers, and friends) that TeleBotHost loads and sandboxes for you.

Every module is accessed as modules.<name> — case-sensitive. modules.JWT works. modules.jwt does not. The universe is cruel but consistent.

How to use them¶

Drop this in any command's Logic field:

let id = modules.UUID.uuidv4()
Bot.sendMessage("Your order ID: " + id)

Three things worth knowing upfront:

1. modules is already there — you never import or initialize it.
2. The object is frozen — you can't add your own properties to modules. Nice try though.
3. Some methods need await — parsing and crypto hashing often return Promises. More on that below.

Modules or Libs?¶

TBL has two toolboxes. Pick the right drawer before you rummage:

Full Libs docs: TBL Libraries.

Still not sure? Rule of thumb: if you'd normally npm install it, check modules first. If it's Telegram-bot-specific glue, check Libs.

Pick a module¶

Security and crypto¶

Parsing and data¶

Dates and text¶

Random and IDs¶

Web3 and markets¶

Try it — copy-paste examples¶

Start simple. Each example only introduces what it needs.

Generate a unique ID¶

No setup, no secrets — just an ID:

let ref = modules.UUID.uuidv4().slice(0, 8).toUpperCase()
Bot.sendMessage("Your reference: #" + ref)

Validate an email¶

params is whatever the user typed after your command:

if (!modules.validator.isEmail(params)) {
  return Bot.sendMessage("That doesn't look like an email. Try again.")
}
Bot.sendMessage("Email accepted. Welcome aboard!")

Markdown → HTML for Telegram¶

Telegram's HTML mode is picky. md2html translates your Markdown:

let html = modules.md2html("**Sale!** Visit [our site](https://example.com)")
Bot.sendMessage(html, { parse_mode: "HTML" })

Sign a session token¶

Store your secret in dashboard ENV settings, then read it via process.env:

let token = modules.JWT.sign(
  { uid: user.id },
  process.env.JWT_SECRET,
  { expiresIn: "7d" }
)
Bot.sendMessage("Logged in. Token saved.")

ENV setup: process.env · JWT details: JWT module

Check BTC price¶

let btc = modules.marketHub.getCrypto("BTC")
if (btc) {
  Bot.sendMessage("BTC: $" + modules.marketHub.formatPrice("BTC"))
} else {
  Bot.sendMessage("Price feed is taking a coffee break. Try again soon.")
}

Parse CSV (async)¶

ParseCSV returns a Promise — add await:

let csvText = "name,score\nAlice,9001\nBob,42"
let rows = await modules.ParseCSV.parse(csvText)

for (let row of rows) {
  Bot.sendMessage(row.name + " scored " + row.score)
}

How modules work¶

The internals — useful when something breaks, skippable when you're vibing:

Size limits¶

Parsing modules (ParseCSV, ParseYML, cheerio, md2html, qs.parse, JWT) enforce your plan's max input size:

Go over the limit and you'll see: Input exceeds plan limit (N bytes). The docs didn't write themselves — they had to draw a line somewhere.

Module-specific caps¶

Sync vs async¶

Most modules are synchronous — call them like any function. A few need await:

// Async — don't forget await
let rows = await modules.ParseCSV.parse(csvText)
let hash = await modules.bcrypt.hash(password, 10)

// Sync — just call it
let id = modules.UUID.uuidv4()
let valid = modules.validator.isEmail(email)

Forget await on an async method and you'll get a Promise object instead of the result. JavaScript's favorite prank.

Retired modules¶

These used to exist. They don't anymore. We're sorry for the inconvenience:

Where modules work¶

Pages in this section¶

Every module has its own page — linked in the tables above. Recently added: ethers, marketHub, md2html.