Ahoy, crew. A fresh drop landed on r/PromptEngineering. A 15-year-old builder who goes by Zero shipped ZeroBotForge, a desktop app where you make a Telegram bot by wiring nodes together. No code and no terminal commands. If you’ve ever wanted a bot but bounced off the setup work, this is aimed squarely at you.
What’s new
ZeroBotForge is built with TypeScript, React, Electron and npm. You open the app, drop nodes on a canvas, connect them, and tune each one in the interface. That’s the whole build. Because it’s an Electron desktop app, you install it like any other program and work in a window, not in a command line.
Zero says it works for any kind of Telegram bot, from a shop assistant to a startup idea. Picture a bot that greets a customer, asks what they’re looking for, and replies with the right answer. Or a simple helper for your community that answers the same three questions people keep asking. Every node is customizable, so you aren’t boxed into one template.
This is the first version, and Zero says so up front. There aren’t many nodes yet. But a basic, standard bot is already buildable today, and that’s enough to learn the tool and see where it’s headed.
The twist
Here’s the part I like. This isn’t a visual toy that stays trapped inside its own app. ZeroBotForge has a code generation engine. When you press the Generate bot project button, it writes the real bot code from your node graph.
So the nodes are the interface and real code is the output. You never have to touch that code, but it exists. The usual no-code complaint is that you can’t see what’s under the hood or take it with you. Here the project is generated for you. If you learn to code later, or hire someone, there’s an actual project to open instead of a locked box.
The second surprise is the chat preview. You can see how your bot talks before you launch anything. If something feels off, you fix it on the canvas and check again. That quick loop of change, preview, adjust is where most of your time will go, and it’s a fast one.
The mini-workflow
- 🧩 Add nodes to the canvas and connect them in the order the conversation should flow. Think of it like drawing the chat on paper first: who speaks, what comes next, where it ends.
- 🎛️ Click each node and customize it in the UI: messages, behavior, details. Write your replies the way you’d text a friend, short and clear.
- 💬 Open the chat preview and read the conversation like a user would. Try the odd paths too, not just the happy one.
- ⚙️ Go to the Run tab. One button handles the whole chain: build the bot code, compile it automatically, and run the bot locally.
- 📱 Open Telegram and talk to your bot live. Send it a few messages and confirm it behaves the way the preview promised.
That’s the full loop from idea to a running bot, and you never open a terminal.
Pro tips
- Start small. The node library is limited right now, so build a simple flow first. Greeting, one question, one answer. Get it talking, then add to it one node at a time so you always know which change broke what.
- Preview before you run. The chat preview is the cheapest test you have. Use it to catch awkward replies before you test on Telegram. Read every message out loud once. If it sounds stiff, rewrite it.
- Sketch the flow first. Before you open the app, jot down the conversation in a notes file. Three or four lines is enough. It turns node placement into a quick copy job instead of a guessing game.
- Remember it runs locally. The Run tab starts the bot on your own machine. That means it works while your computer is on and the app is running. The post doesn’t cover keeping it online around the clock, so check the repo for hosting details before you promise a client anything.
- Treat it as an early build. Expect rough edges and missing nodes. That’s normal for a first release. If something breaks, note exactly what you clicked, because that detail is gold for the developer.
Why this one is worth a look
Builders in the comments liked the node-based approach. One said most no-code bot tools end up as glorified form fillers, and that seeing the flow and tweaking it visually makes this one feel more approachable. I agree. A canvas makes the logic of a conversation easy to see, and that matters more as bots get longer and branch in more directions. Scrolling through a wall of settings hides the shape of a chat. A graph shows it at a glance.
Zero is also asking for criticism and ideas for the next version, which is the best time to shape a project like this. If you’ve built bots before, you know which nodes are missing. Maybe it’s a way to handle buttons, a way to store what a user said, or a way to branch on a keyword. Tell them.
One more thing. Zero wrote the post in Persian and translated it into English, and still shipped a working tool. That’s the kind of builder worth cheering on!
Call to Action
Check out the repo: github.com/Z-E-7-0-7-R-O/ZeroBotForge. Try it, break it, and leave Zero honest feedback or a node suggestion. Early projects grow fastest when people actually use them, so even a short note about what confused you will help the next version land better.
Frequently Asked Questions
Q: Do I need to know how to code to build a bot with ZeroBotForge?
No. You build the bot by placing nodes on the canvas, connecting them, and customizing each one in the interface, with no terminal commands. The project is still early and has a limited set of nodes, but the post says a standard Telegram bot is already doable. Start with a greeting and one menu, then add branches once that part works.
Q: How can I test a bot before it goes live?
Use the local run and chat preview. It lets you walk through the conversation the way a real user would, so you can catch a broken branch before anyone else sees it. Go several messages deep when you test, because that’s where broken flows tend to hide.
Q: How do I keep a visual bot flow easy to follow as it grows?
Give each node a name that says what it does, like ‘Ask for email’ or ‘Show prices,’ so the canvas reads like a plan instead of a puzzle. Because the whole conversation is laid out as connected nodes, you can change one step without rewriting everything else. Check the flow visually after each change so you don’t lose track of which branch goes where.
ZeroBotForge project: creating a Telegram bot easily, without coding, without terminal commands, completely No-Code, only by connecting nodes together and desired customization of nodes without coding, only with the user interface.
by u/ze707ro in PromptEngineering