Telegram AI Automation Kit is a public starter kit for turning Telegram bot conversations into AI-assisted business request workflows.
The current app is a frontend implementation with mock data. It demonstrates how incoming Telegram messages can become structured requests, summaries, priorities, suggested replies, logs, and dashboard follow-up without requiring live credentials.
- Shows a Telegram-style intake flow for customer and internal messages.
- Classifies requests by type, priority, status, and owner.
- Displays AI-assisted summaries and suggested replies.
- Provides dashboard views for requests, logs, settings, packages, and use cases.
- Keeps demo settings local to the browser session only.
- Documents the configuration shape needed for live Telegram and AI integrations.
- React, TypeScript, Vite, and Tailwind CSS frontend.
- Mock request data and activity logs for local demos.
- Bot flow simulator for testing intake and response paths.
- Request detail modal with status updates and suggested reply copy action.
- Settings screen for Telegram token, chat ID, AI provider, storage mode, and prompt examples.
- Public safety defaults: no committed secrets, no live API calls, and no persistent credential storage.
- Node.js 18 or newer.
- npm.
- A Telegram bot token from BotFather only if you build or connect a live bot backend.
git clone <your-fork-url>
cd Telegram_AI_Automation_Kit
npm install
cp .env.example .env.local
npm run devFill .env.local with your own values only when testing live integrations. The included frontend mock works without real Telegram, AI, or storage credentials.
Use .env.example as the public configuration reference. It contains placeholders only:
TELEGRAM_BOT_TOKENTELEGRAM_CHAT_IDAI_API_KEYWEBHOOK_SECRET
Do not commit .env, .env.local, .env.production, or any other file containing real credentials.
These commands are defined in package.json:
npm run dev
npm run build
npm run lint
npm run preview
npm run typecheck
npm run test:readinessThe current project builds as a static Vite app:
npm run buildDeploy the generated dist folder to any static hosting provider. For a real Telegram bot, keep bot tokens, AI keys, webhook secrets, and storage credentials on a backend or secret-managed deployment environment. Do not expose live secrets in the browser bundle.
- The repository should contain placeholders only, never real bot tokens or API keys.
- Demo data is synthetic and should not contain private customer information.
- The frontend does not send mock settings to Telegram, AI providers, or storage services.
- Rotate any exposed Telegram bot token immediately and update your deployment secrets.
- See
SECURITY.mdfor reporting guidance.
MIT License. See LICENSE for details.