docs: Put your App on Telegram - #23
Merged
Merged
Conversation
New Build page: turn a deployed Aomi App into a Telegram bot via the hosted registration flow (chat.aomi.dev/settings, Bots tab). Create a bot in BotFather, paste the token, pick the Default App, and Aomi verifies the token and activates the webhook, no server to run. Uses Goal Digger as the worked example. Verified against the shipped aomi-telegram bot and the live Bots settings form. Documents only the real path: Default App binding (not /app, which is a fixed built-in set), public vs private App keys, wallet simulate-before- sign, and the SDK-bump caveat. Self-hosted bot.toml is linked as advanced, pointing at the existing Telegram reference page. docs.json places build/telegram-bot after frontend-vercel under Build on Aomi. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Adds a new “Build on Aomi” guide that documents the hosted flow for turning a deployed Aomi App into a Telegram bot, and wires it into the docs navigation.
Changes:
- Adds a new guide page:
build/telegram-bot.mdx(hosted registration flow, commands, groups, keys, and operational notes). - Updates
docs.jsonto place the new page afterbuild/frontend-vercelunder Build on Aomi.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
docs.json |
Adds build/telegram-bot to the Build on Aomi nav group. |
build/telegram-bot.mdx |
New Mintlify MDX guide for registering and using a Telegram bot backed by a deployed App. |
Comments suppressed due to low confidence (1)
build/telegram-bot.mdx:80
- Hyphenate “built-in” when used as a compound adjective before a noun.
`/app` switches among a fixed built in set of sample Apps, not your whole catalog. It is **not** how you reach your own App. Your App is reached by setting it as the bot's **Default App** in Step 2, which is why every registered bot points at one App.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - **Thread Mode**: choose **Single thread** (one running conversation per user) or **Multiple threads** (users can keep separate conversations). Single thread is the simplest to start with. | ||
| 3. Create it. | ||
|
|
||
| Aomi verifies the token with Telegram, stores it encrypted, and turns on the webhook for you. When it says the bot is registered and the webhook is active, you are done. There is nothing to deploy and no server to keep running. |
| | `/settings` | Bot preferences, such as streaming replies. | | ||
| | `/sessions` | Manage conversation threads. | | ||
| | `/apikey` | Set an app key, only needed for a **private** App. See [Keys](#keys). | | ||
| | `/app` | Switch between a small built in set of sample Apps. | |
| Give the same App a branded web page as well as a bot. | ||
| </Card> | ||
| <Card title="Telegram Bot reference" href="/getting-started/telegram"> | ||
| Every command, panel, and the self hosted `bot.toml` configuration. |
victorchimakanu
added a commit
that referenced
this pull request
Jul 30, 2026
Han shipped many-to-many Telegram bots (product-mono #867, aomi #388/#420, merged + live 2026-07-30). The page shipped in #23 documented the old model and is now stale on two fronts: - Surface moved: the chat.aomi.dev/settings Bots tab was removed; bot management is now at build.aomi.dev/integrations (GitHub-gated), verified 200 live. Updated Step 2 accordingly. - Binding is multi-app: one bot serves many Apps via Attached apps (multi-select) + a Primary app, replacing the single Default App. Updated the form fields and framing, and noted you can edit attached apps later. - /app is now dynamic: it switches among the bot's attached Apps. Removed the old warning that /app was a fixed sample set and not how you reach your App; that is no longer true. App Keys reference stays chat.aomi.dev/settings (only the Bots tab moved). mint broken-links passes. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
New Build page Put your App on Telegram (
build/telegram-bot.mdx) — turn a deployed Aomi App into a Telegram bot. Uses Goal Digger as the worked example. Placed afterfrontend-vercelunder Build on Aomi.The path it documents
The hosted registration flow, which is the real shipped path for a deployed App:
chat.aomi.dev/settings→ Bots tab → paste token, pick Default App (this binds the bot to your App), pick Thread Mode, create.Plus: the real command list, groups, public vs private App keys (
/apikey), wallet simulate-before-sign, and the SDK-bump caveat (links to the deploy page's section).Accuracy (verified against source, not guessed)
Checked against the shipped
aomi-telegrambot inproduct-monoand the live Bots settings form. Deliberately avoids things that are not real:/app(which is a fixed built-in set of sample Apps — documented as such).bot.tomlbinary is mentioned only as an advanced path and linked to the existinggetting-started/telegramreference.Verified
mint broken-linkspasses;docs.jsonvalid; all cross-links resolve.🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.