Laravel Telegram Group Management Bot (TeleGroupBot) is a comprehensive, Laravel-based solution for automating and moderating Telegram groups. It handles the day-to-day work of running a community β filtering spam, censoring keywords, managing service messages, restricting new members, scheduling announcements, and surfacing member-activity insights β so admins can keep their groups clean, safe, and engaged.
Beyond moderation, the project is built as a SaaS-ready platform: it includes a web dashboard, multilingual support, subscriptions/plans, QR-code generation, an update system, and integrations with a wide range of payment gateways (PayPal, Stripe, Razorpay, Mollie, Flutterwave, Paystack, Mercado Pago, Xendit, and more). Real-time events are powered by Pusher, queues by Redis/Predis, and storage can be backed by AWS S3.
It's ideal for community managers, agencies, and developers who want to offer Telegram group automation as a product or run it for their own communities.
π Keywords: telegram bot, telegram group management, laravel telegram bot, telegroupbot, group moderation, message filtering, keyword censor, scheduled messages, community management, saas, subscription payments.
- π‘οΈ Group management β automate routine tasks to run your Telegram group efficiently.
- π Privacy & security β keep your group protected and well-moderated.
- π§© Customizable β adapt the bot to the unique needs of each community.
- π« Advanced message filtering β automatically filter messages to keep discussion clean and relevant.
- π€ Keyword monitoring β censor specific words to keep the group respectful.
- π Service-message management β control "user joined" / "user left" and other service messages.
- π New-member restrictions β set limits and rules for newcomers.
- β° Scheduled messages β broadcast announcements and reminders on a schedule.
- π Member activity insights β understand engagement and interaction patterns.
- π Ban & mute β effectively handle problematic members.
- π Multilingual β built-in translation management.
- π³ Subscriptions & payments β multiple gateways (PayPal, Stripe, Razorpay, Mollie, and more).
- π Webhook-driven β receive and process Telegram updates via webhook.
| Layer | Technologies |
|---|---|
| Backend | Laravel 8, PHP 7.3 / 8.x, Laravel Sanctum, Tinker |
| Messaging | Telegram Bot API (webhook), Pusher (realtime) |
| Queue & Cache | Redis / Predis |
| Storage | AWS SDK, Flysystem S3 |
| Frontend | Blade, Tailwind CSS, Alpine.js, Laravel Mix, SweetAlert2 |
| Payments | PayPal, Stripe, Razorpay, Mollie, Flutterwave, Paystack, Mercado Pago, Xendit, Instamojo, Myfatoorah, Senangpay, Toyyibpay, Paymaya, Yoomoney |
| Utilities | Simple QrCode, LaravelCollective HTML, Joe Dixon Translation |
- PHP β₯ 7.3 (8.x recommended) with Composer
- MySQL β₯ 5.7
- Node.js & npm (for frontend assets)
- A Telegram bot token (from @BotFather)
# 1. Clone the repository
git clone https://github.com/morpheusadam/laravel-management-telegram-bot.git
cd laravel-management-telegram-bot
# 2. Install dependencies
composer install
npm install
# 3. Create and configure your environment
cp .env.example .env
php artisan key:generate
# 4. Run migrations (and optionally seed)
php artisan migrate
php artisan db:seed # optional
# 5. Build assets
npm run devStart the server and open http://localhost:8000:
php artisan serveβοΈ Configure your Telegram bot token, database, Pusher, and payment gateway credentials in
.env, then point your bot's webhook to the app's webhook endpoint.
laravel-management-telegram-bot/
βββ app/
β βββ Http/Controllers/ # Bot, Webhook, Dashboard, Subscription...
β βββ Providers/Payment/ # PayPal, Stripe, Razorpay, Mollie, ...
β βββ Models/ # Telegram_bot, Usage_log, User
β βββ Events/ # ChatEventPusherTelegram / Whatsapp
β βββ Jobs/ # SendEmailJob
βββ .github/workflows/ # CI (php.yml)
βββ resources/ # Blade views & Tailwind assets
βββ routes/ # web, api & webhook routes
Contributions are welcome! Fork the repository and submit a pull request, or open an issue with ideas and bug reports.
Released under the MIT License β see the LICENSE file (or add one) for details.