telegram-worker Isolate Profile

​

⚡ 1. Declared Wrangler Configurations & Bindings

{
  "name": "telegram-worker",
  "main": "src/index.ts",
  "compatibility_date": "2026-05-19",
  "compatibility_flags": ["nodejs_compat"],
  "account_id": "debc6545e63bea36be059cbc82d80ec8",
  "placement": {
    "mode": "smart",
  },
  "kv_namespaces": [
    {
      "binding": "CONFIG_KV",
      "id": "c5917667a21745e390ff969f32b1847d",
    },
  ],
  "r2_buckets": [
    {
      "binding": "UPLOADS_BUCKET",
      "bucket_name": "user-uploads",
    },
  ],
  "vectorize": [
    {
      "binding": "VECTORIZE_INDEX",
      "index_name": "rag-index",
    },
  ],
  "ai": {
    "binding": "AI",
  },
  "secrets": [
    "INTERNAL_KEY_BINDING",
    "TG_BOT_TOKEN_BINDING",
    "TG_CHAT_ID_BINDING",
    "TELEGRAM_SECRET_TOKEN",
  ],
}

​

🔑 2. Environmental Variables & Encrypted Secrets

• TG_BOT_TOKEN_BINDING: Private HTTP bot token generated by @BotFather.
• TG_CHAT_ID_BINDING: Your default Chat ID for receiving notifications.
• TELEGRAM_SECRET_TOKEN: A secure, random token sent as the X-Telegram-Bot-Api-Secret-Token header to validate webhook requests from Telegram.
• INTERNAL_KEY_BINDING: Shared key used to validate calls from hoox or trade-worker.
• AUTHORIZED_CHAT_IDS: Optional comma-separated list of chat IDs allowed to send bot commands. If set, only these chat IDs can interact with the bot.

​

Local Development Mocking (.dev.vars)

TG_BOT_TOKEN_BINDING=mock_telegram_bot_token
TG_CHAT_ID_BINDING=987654321
TELEGRAM_SECRET_TOKEN=local_secure_route_token
INTERNAL_KEY_BINDING=dev_shared_internal_security_key

​

🔌 3. Internal REST API Specification

Note: For the canonical endpoint directory with full request/response examples across all workers, see /docs/devops/api/endpoints.

​

A. Dispatch Notification Endpoint

• Endpoint: /alert
• Method: POST
• Headers: X-Internal-Auth-Key: <INTERNAL_KEY_BINDING>
• JSON Payload:
  {
    "requestId": "9b1deb4d-3b7d-4bad-9bdd-2b0d7b3dcb6d",
    "payload": {
      "chatId": "987654321",
      "message": "<b>📈 Bybit LONG Filled!</b>\nSymbol: <code>BTCUSDT</code>\nPrice: <code>$68,425.50</code>\nQuantity: <code>0.005</code>",
      "parseMode": "HTML"
    }
  }
  
• Success Response (200 OK):
  {
    "success": true,
    "result": { "messageId": 482904 },
    "error": null
  }
  

​

B. Telegram Ingress Webhook Route

• Endpoint: /telegram/<TELEGRAM_WEBHOOK_SECRET>
• Method: POST
• JSON Payload: Standard Telegram update JSON schema.
• Access Control: The worker extracts the incoming message.chat.id. If it does not match your authorized TELEGRAM_CHAT_ID_DEFAULT secret, the payload is silently dropped with a 200 OK return to Telegram to prevent malicious commands.

​

🧠 4. AI-Powered Chatbot & RAG Mechanics

1. Embedding Generation: The worker calls env.AI to generate high-dimensional text embeddings for your prompt using the @cf/baai/bge-base-en-v1.5 model.
2. Vector Query: Passes the vector to env.VECTORIZE_INDEX to retrieve semantically related transaction rows and market summaries from past trades.
3. Context Construction: Formats the matched history into a rich LLM context window.
4. LLM Inference: Invokes LLaMA-3 instruct via env.AI using your multi-provider API keys to generate a highly informed financial summary.

​

🔗 Next Steps

• hoox Gateway Profile — Review how incoming commands route to the gateway.
• Setting Up Telegram Bot Alerts — Step-by-step tutorial for BotFather configuration.