Why I Built a Modern TypeScript SDK for Telegram Bots (and You Should Use It Too)

Dmytro — Tue, 22 Apr 2025 01:08:43 +0000

When I first started building Telegram bots in Node.js, I expected it to be fun.
But pretty quickly I ran into a familiar wall: boilerplate, manual wiring, poor DX (developer experience). You know how it goes.

You want to just send a message or set a webhook — and instead, you’re copy-pasting code from Stack Overflow, manually writing fetch requests, building URLs by hand, and dealing with vague error messages like "Bad Request" with no clue what’s wrong.

There are libraries out there, sure. But most of them are either outdated, bloated, or just not friendly if you’re building something serious, especially with TypeScript.

That’s when I realized:
I’d rather invest time into building a clean SDK than keep fighting with spaghetti code every time I need a bot.

So I built gramflow — a modern, minimalistic, developer-focused SDK for the Telegram Bot HTTP API.

⸻

🚀 What makes gramflow different?
• Uses native fetch — no weird wrappers, no magic
• Fully typed — thanks to TypeScript, your IDE is your best friend
• Clear structure — BotService, httpClient, and typed error handlers
• Built with readability and extensibility in mind
• Works out of the box with NestJS, Express, and Fastify
• Easy to test, easy to reason about, easy to extend

No classes trying to be too smart. No runtime hacks. Just clean, modern code.

⸻

🛠 What’s under the hood?
• 💡 A lightweight and testable httpClient
• 🔒 Custom error types like ChatNotFoundError, UnauthorizedError, and more
• 🎯 Consistent DTOs and response contracts
• ✅ Unit tests using nock and jest so you don’t have to test Telegram’s servers

⸻

📦 Quick install

npm i @oravone/gramflow

⸻

📚 Example usage

import { BotService } from '@oravone/gramflow';

const bot = new BotService('123:ABC');

const info = await bot.getMe();
console.log(info.username); // your bot’s username

await bot.setWebhook({ url: 'https://yourapp.com/webhook' });

⸻

🤝 What’s next?

gramflow is just getting started, but the roadmap is 🔥:
• Support for receiving updates (long polling / webhook parsing)
• More Telegram methods: sendMessage, sendPhoto, editMessageText, and others
• Middlewares and interceptors for clean message flows
• NestJS-ready module: GramflowModule
• Auto-generated types based on Telegram Bot API schema (like OpenAPI)

⸻

❤️ Why I’m building this

Because bots are awesome — but the ecosystem should be better.
Because we deserve better DX, and less boilerplate.
Because I wanted a tool I would actually enjoy using.

If you’ve ever built bots in Node or TypeScript and thought “ugh, again?”, this is for you.

⸻

🧠 Final thoughts

gramflow is still early, but growing fast. I’m actively adding features, testing real-world use cases, and planning integration with frameworks and automation tools.

If this sounds interesting — check out the GitHub repo, leave a ⭐, open an issue, or just drop a “hey” in discussions.
I’d love to hear your ideas, feedback, or even feature requests.

Let’s make bot development joyful again.
Let’s build something cool — together 👨‍💻🔥

With ❤️ from Me and Oravone Team

DEV Community: Dmytro

Why I Built a Modern TypeScript SDK for Telegram Bots (and You Should Use It Too)