Botxona

Deploy your first bot in 10 minutes

This guide takes you from start to finish: even if you don't have a bot yet, by the end you'll have a working bot you can test in Telegram.

Steps

1. Get a token (BotFather)

Open a chat with @BotFather in Telegram, send /newbot, and give your bot a name and a username. The reply contains a long token — your bot's "key". Details: Getting a token.

2. Prepare the bot code

If you have code, zip it. If not, give a ready-made task from the Prompt library to an AI and it will write the code for you. The code must follow the 6 rules — for example, the token comes from the BOT_TOKEN environment variable and data is stored inside DATA_DIR.

3. Upload the ZIP

In the dashboard, click "New bot", choose the ZIP file (or paste a GitHub repo link), name the bot and enter the token. File requirements: Preparing a ZIP.

You can also skip the website and do it right in Telegram: send /newbot to @botxona_uz_bot — it asks for the token, then you send the ZIP file as a document (or pick one of the ready-made bots). The check result and the trial and payment buttons arrive in the same chat.

4. Review the check result

After upload, the system automatically checks the code against the 6 rules and for security, then builds it in a docker container. If the result is 🟢 (green) or 🟡 (yellow), you can go ahead. If it's 🔴 (red), you'll see the reason and a ready-made AI prompt to fix it. Details: Reading the check result.

5. Test it

If the build succeeds, the bot starts in a 15-minute free trial. Open your bot in Telegram and send /start — you should get a reply.

6. Pay

If you liked the bot during the trial, choose a plan and pay — by card, for the exact amount. Details: How payment works. Once the payment is confirmed, the bot switches to 24/7 operation.

Common mistakes

  • Token entered incorrectly — copy the whole line from BotFather's message (the digits:letters-and-symbols sequence) with no spaces.
  • Several folders inside the ZIP — a single project folder at the archive root is fine, but if requirements.txt/package.json can't be found you'll get an error. See: Preparing a ZIP.
  • Including the .env file in the archive — for security, such a file is removed automatically; you enter settings separately in the dashboard.

Next step

Once the bot is running: Dashboard tour, Reading logs, Analytics.