Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Laragram Laravel Package

milly/laragram

Laragram is a Laravel package for building Telegram bots with a clean, expressive API. It wraps Telegram Bot API calls and follows Laravel conventions for configuration, routing, webhooks, commands, and responses, making bot development simpler and more maintainable.

View on GitHub
Deep Wiki
Context7

Laravel package to develop telegram bot inside laravel project

Frequently asked questions about Laragram
What is milly/laragram and what does it do?
milly/laragram is a Laravel package for developing Telegram bots inside a Laravel application. It wraps Telegram Bot API calls and follows Laravel conventions for configuration, routing, webhooks, commands, and responses. It is best suited to teams that want bot logic to live alongside an existing Laravel codebase rather than in a separate runtime.
How do I install milly/laragram in a Laravel app?
Install it with Composer, publish the package configuration, and store your Telegram bot token in an environment variable or secret manager. Then register the webhook route and configure any queue or command settings required by your bot. Check the README and composer.json first because exact publish tags, middleware, and route setup are package-specific.
Which Laravel and PHP versions does milly/laragram support?
The provided context does not list exact Laravel and PHP version constraints, so you should verify them in the package composer.json and README before committing. Confirm the illuminate/* dependency range and test against your application's Laravel and PHP versions. Because adoption is low, treat major Laravel upgrades as an explicit compatibility check rather than assuming support.
Does Laragram support webhook mode, polling mode, or both?
The package overview emphasizes Laravel routing and webhook integration, so webhook mode is the most likely primary path. The available context does not confirm whether polling mode is supported or first-class. Review the documentation and test both modes with a dedicated bot before designing production traffic around either approach.
How should I secure Telegram webhook requests in Laravel with Laragram?
Use HTTPS ingress, keep the bot token in a secret store, and configure Telegram's webhook secret token if the package supports it. Ensure your Laravel route excludes CSRF checks appropriately while still validating the webhook secret header or another trusted mechanism. Add replay and idempotency controls in application code for sensitive commands, and confirm the package's documented security model before production use.
Can I queue Telegram updates and responses with milly/laragram?
Queue support is important for production bots, but the provided context does not confirm whether updates are queued by default or how retries are handled. You can still design your integration to dispatch application handlers onto Laravel queues and keep bot command logic behind an adapter. Verify the package's documented queue behavior and test failures, retries, and rate-limit handling before launch.
Does milly/laragram support multiple bots in one Laravel application?
Multi-bot support is a key question for this package, and the provided context does not confirm that it is first-class. Check whether configuration allows isolated tokens, routes, and handlers per bot, and test that updates cannot cross between bots. If support is limited, keep bot-specific configuration in your application layer and isolate each bot behind a clear adapter.
How do I test a Laravel Telegram bot built with Laragram?
Start with a dedicated test bot and avoid pointing automated tests at production credentials. Test webhook payload handling, command routing, queue dispatch, and failure paths with mocked HTTP calls or Laravel's HTTP and queue fakes. Add contract tests around your own bot handler interface so you can replace the package later. The package's own test coverage and CI posture should be checked separately before relying on it.
What are the risks of using milly/laragram in production?
The main risk is low ecosystem validation: the project has around 41 stars, zero dependents, and likely a single-maintainer bus factor. MIT licensing is permissive but provides no warranty, and Telegram Bot API or Laravel major-version changes may require package updates. Pin the version, monitor releases and issues, keep secrets and webhook handling under your control, and define a rollback to raw Bot API calls or another SDK.
What alternatives to milly/laragram exist for Laravel Telegram bots?
Common alternatives include irazasyed/telegram-bot-sdk, nutgram, or direct calls to the Telegram Bot API from Laravel services. The safest approach is to wrap your bot logic behind an internal interface and implement it with milly/laragram so you can switch later. Compare maintenance activity, Laravel version support, queue behavior, webhook security, and multi-bot support before choosing.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
jinas/dhivatar
store-doc/laravel-storage-driver
plus-it/laravel-translation-manager
diephp/perhaps
diephp/telegraph
osmaviation/spreadsheet
microsoft/fluentui-system-icons
mmccook/php-json-canonicalization-scheme
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console
pnscripts/filament-broadquill-lite
pnscripts/laravel-sentfold-lite
vleap/mx-sdk-laravel-internal
twidpay/utils
htetmyathlaing/scout-elasticsearch-driver
artisan-toolbox/front-awesome
ls/client-assistant
users-au/laravel-client
cgv/localized-resource