Menu
Recipe for integrating a Telegram bot into a web app, using webhooks and direct HTTP calls to the Telegram Bot API
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Describes the current local development setup, for when we want to perform development tasks on the actual Rhizome app
How to talk to the deployed plurama apps (treina, …) from the shell with the plurama-cli command — a curl-like client that carries baked-in prod credentials. Use whenever a task means reading or writing live plurama app data over HTTP, when `plurama-cli` is missing or unauthorized, or when a new app must be added to it.
Tracker's HTTP API — authenticate as a machine user, read tasks/meets/journals/today-board, ingest mail messages, write through the recording-mode gate via curl
How to run, test and develop the natural-language Telegram bot that queries tracker. The bot is NOT in tracker — it lives in the plurama umbrella app (plurama/src/plurama/app/agent). Covers the agent architecture, the secrets/config it needs, the locked-box egress-proxy gotcha, seeding a testable conversation, and driving it from the host as if you were Telegram.
To develop the user interface of the application, you need to know how to start, stop, restart the app and where to find it.
Rhizome's local REST API — search, read, and create contexts/items via curl
| name | telegram |
| description | Recipe for integrating a Telegram bot into a web app, using webhooks and direct HTTP calls to the Telegram Bot API |
Recipe for integrating a Telegram bot into a web app, using webhooks and direct HTTP calls to the Telegram Bot API (no wrapper library needed).
/newbot, follow the prompts1234567890:AAH...)openssl rand -hex 32
Save this as your webhook secret.
TELEGRAM_BOT_TOKEN=<your-bot-token>
TELEGRAM_WEBHOOK_SECRET=<your-generated-secret>
Expose a POST /webhook/telegram endpoint. The handler should:
x-telegram-bot-api-secret-token header against your secretbody.message.text (also check body.edited_message)POST https://api.telegram.org/bot<TOKEN>/deleteMessage
Content-Type: application/json
{"chat_id": <chat-id>, "message_id": <message-id>}
Return 200 OK to Telegram on every request (otherwise Telegram retries).
curl -X POST "https://api.telegram.org/bot<TOKEN>/setWebhook" \
-H "Content-Type: application/json" \
-d '{
"url": "https://<your-domain>/webhook/telegram",
"secret_token": "<your-webhook-secret>"
}'
Telegram requires HTTPS. For local development, use a tunnel (e.g. ngrok).
curl "https://api.telegram.org/bot<TOKEN>/getWebhookInfo"
Should show your URL and pending_update_count.
x-telegram-bot-api-secret-token header on every request, so you can authenticate without needing other auth middleware on that route.https://api.telegram.org/bot<TOKEN>/<method> are sufficient./start gracefully (it's sent when a user first interacts with the bot).After processing an incoming message, you can delete it from the Telegram chat so that the bot conversation stays clean. The incoming webhook payload contains everything you need:
{
"message": {
"message_id": 42,
"chat": { "id": 123456789 },
"text": "some note"
}
}
After storing/processing the message, call:
POST https://api.telegram.org/bot<TOKEN>/deleteMessage
Content-Type: application/json
{"chat_id": 123456789, "message_id": 42}
This turns the bot into a "fire and forget" inbox — you send a message, it gets captured by your app, and disappears from the chat.