vegas / messenger-notification

v1.0.2 2026-09-27 09:09 UTC

Requires

• php: ^7.2.5 || ^8.0
• ext-json: *
• guzzlehttp/guzzle: ^7.0
• illuminate/console: ^7.0 || ^8.0 || ^9.0 || ^10.0 || ^11.0 || ^12.0 || ^13.0
• illuminate/notifications: ^7.0 || ^8.0 || ^9.0 || ^10.0 || ^11.0 || ^12.0 || ^13.0
• illuminate/support: ^7.0 || ^8.0 || ^9.0 || ^10.0 || ^11.0 || ^12.0 || ^13.0
• irazasyed/telegram-bot-sdk: ^3.9
• vegas/laravel-notification-channel-max: ^1.0

Requires (Dev)

• mockery/mockery: ^1.4
• orchestra/testbench: ^5.0 || ^6.0 || ^7.0 || ^8.0 || ^9.0 || ^10.0 || ^11.0
• phpunit/phpunit: ^8.5 || ^9.6 || ^10.5 || ^11.0 || ^12.0

MIT

• Vegas

• notifications
• laravel
• Messenger
• telegram
• max

Published on Packagist.org on 2026-09-27 09:10 UTC

README

Unified Telegram and MAX notification channels for Laravel. Each channel can independently send directly, use an external relay, or be disabled.

The package contains no relay endpoint, bot token, chat ID, or project secret. All values are configured by the consuming application.

Installation

composer require vegas/messenger-notification
php artisan vendor:publish --tag=messenger-config

Configuration

Direct Telegram and relay MAX:

TELEGRAM_NOTIFICATION_DRIVER=direct
TELEGRAM_BOT_TOKEN=
TELEGRAM_CHANNEL_DEFAULT_ID=
TELEGRAM_PROXY=

MAX_NOTIFICATION_DRIVER=vegas-services

VEGAS_SERVICES_URL=
VEGAS_SERVICES_PROJECT=
VEGAS_SERVICES_SIGNING_KEY=

Supported drivers are direct, vegas-services, and off. An empty driver also disables the channel and is the default. If VEGAS_SERVICES_SIGNING_KEY is empty, a stable signing key is derived from the application's APP_KEY.

Laravel notifications

use Vegas\MessengerNotification\Channels\MaxChannel;
use Vegas\MessengerNotification\Channels\TelegramChannel;
use Vegas\MessengerNotification\Messages\MessengerMessage;

public function via($notifiable)
{
    return [TelegramChannel::class, MaxChannel::class];
}

public function toMessenger($notifiable)
{
    return MessengerMessage::create('*New order*')
        ->idempotencyKey('order-created:' . $notifiable->id)
        ->button('Open', route('orders.show', $notifiable));
}

Documents

use Vegas\MessengerNotification\Messages\MessengerMessage;
use Vegas\MessengerNotification\MessengerNotifier;

app(MessengerNotifier::class)->send(
    MessengerMessage::create('Competitor prices changed.')
        ->idempotencyKey('competitor-prices:' . hash_file('sha256', $path))
        ->document($path, 'prices.xls', 'application/vnd.ms-excel')
);

Diagnostics

php artisan messenger:signing-key
php artisan messenger:test all
php artisan messenger:test telegram
php artisan messenger:test max

Relay contract

Relay requests are sent to VEGAS_SERVICES_URL/api/v1/notifications as signed JSON. The HMAC-SHA256 signature covers the timestamp, project slug, and exact request body. Document contents are included as Base64 and should be limited by the relay server.