/laravel-agent:notification:make

Overview

The /notification:make command creates Laravel notifications with support for 55+ notification channels. It can generate complete multi-channel notification classes or setup individual channels with all required dependencies, configuration, and routing methods.

Usage

/laravel-agent:notification:make [NotificationName] [--channels=] [--setup=]

Examples

# Create notification with multiple channels
/laravel-agent:notification:make OrderShipped --channels=mail,telegram

# Setup a channel only (no notification class)
/laravel-agent:notification:make --setup=telegram

# Create notification with popular channels
/laravel-agent:notification:make WelcomeUser --channels=mail,discord,twilio

# Create admin alert notification
/laravel-agent:notification:make AlertAdmin --channels=slack,teams

Operating Modes

The command operates in two distinct modes:

Mode 1: Setup Channel Only

Use --setup=<channel> to install and configure a notification channel without creating a notification class. This is useful when you want to prepare your application for a specific channel before creating notifications.

Mode 2: Create Notification

Provide a notification name to create a complete notification class with support for multiple channels. The command automatically installs required packages, configures routing, and sets up environment variables.

Supported Channels

The command supports 55+ notification channels, organized into categories:

Built-in Channels (No Package Required)

Push Notifications

SMS/Voice

Messenger/Chat

Channel Configuration Examples

Here are configuration examples for popular notification channels:

Telegram

Environment configuration:

TELEGRAM_BOT_TOKEN=your-bot-token

User model routing method:

<?php

// In App\Models\User
public function routeNotificationForTelegram(): ?string
{
    return $this->telegram_chat_id;
}

Discord

Environment configuration:

DISCORD_WEBHOOK_URL=https://discord.com/api/webhooks/...

Twilio (SMS)

Environment configuration:

TWILIO_SID=your-account-sid
TWILIO_TOKEN=your-auth-token
TWILIO_FROM=+1234567890

User model routing method:

<?php

// In App\Models\User
public function routeNotificationForTwilio(): ?string
{
    return $this->phone;
}

FCM (Firebase Cloud Messaging)

Environment configuration:

FCM_SERVER_KEY=your-server-key
FCM_SENDER_ID=your-sender-id

User model routing method:

<?php

// In App\Models\User
public function routeNotificationForFcm(): array
{
    return $this->fcm_tokens()->pluck('token')->toArray();
}

WebPush

Environment configuration:

VAPID_PUBLIC_KEY=your-public-key
VAPID_PRIVATE_KEY=your-private-key
VAPID_SUBJECT=mailto:admin@yoursite.com

Generate VAPID keys:

php artisan webpush:vapid

OneSignal

Environment configuration:

ONESIGNAL_APP_ID=your-app-id
ONESIGNAL_REST_API_KEY=your-rest-api-key

Vonage (SMS)

Environment configuration:

VONAGE_KEY=your-key
VONAGE_SECRET=your-secret
VONAGE_SMS_FROM=YourApp

What Gets Created

Depending on the mode, the command creates different components:

Setup Mode Output

Notification Creation Output

Generated Notification Example

Here's an example of a multi-channel notification created by the command:

<?php

namespace App\Notifications;

use Illuminate\Bus\Queueable;
use Illuminate\Contracts\Queue\ShouldQueue;
use Illuminate\Notifications\Messages\MailMessage;
use Illuminate\Notifications\Notification;
use NotificationChannels\Telegram\TelegramMessage;
use NotificationChannels\Discord\DiscordMessage;

class OrderShipped extends Notification implements ShouldQueue
{
    use Queueable;

    public function __construct(
        public $order
    ) {}

    public function via($notifiable): array
    {
        return ['mail', 'telegram', 'discord'];
    }

    public function toMail($notifiable): MailMessage
    {
        return (new MailMessage)
            ->subject('Your Order Has Shipped!')
            ->line('Order #' . $this->order->id . ' has been shipped.')
            ->action('Track Order', url('/orders/' . $this->order->id))
            ->line('Thank you for your purchase!');
    }

    public function toTelegram($notifiable): TelegramMessage
    {
        return TelegramMessage::create()
            ->content('*Order Shipped*')
            ->line('Your order #' . $this->order->id . ' has been shipped!')
            ->button('Track Order', url('/orders/' . $this->order->id));
    }

    public function toDiscord($notifiable): DiscordMessage
    {
        return DiscordMessage::create()
            ->embed(function ($embed) {
                $embed->title('Order Shipped')
                    ->description('Order #' . $this->order->id)
                    ->url(url('/orders/' . $this->order->id))
                    ->timestamp(now());
            });
    }
}

Interactive Prompts

When run without the --channels flag, the command provides interactive prompts:

1. Notification name - Text input for the notification class name
2. Select channels - Multi-select from available channels (Mail selected by default)
3. Queue notifications? - Choose between queued (recommended for external channels) or synchronous delivery
4. Add user preferences? - Optionally create a per-user channel preferences system

Usage Examples

After creating a notification, use it in your application:

<?php

// Send to a single user
$user->notify(new OrderShipped($order));

// Send to multiple users
Notification::send($users, new OrderShipped($order));

// Send to specific channels only
$user->notify((new OrderShipped($order))->onlyChannels(['mail', 'telegram']));

Process Flow

The command follows a systematic process:

For Setup Mode

1. Install the channel package via Composer
2. Publish channel configuration files
3. Add environment variables to .env.example
4. Add routing method to User model
5. Create migration for user identifier field (if needed)

For Notification Creation

1. Parse requested channels from flag or interactive prompt
2. Check for and install required packages for each channel
3. Invoke laravel-queue agent to generate notification class
4. Generate via() method and channel-specific methods (toMail(), toTelegram(), etc.)
5. Add all required environment variables to .env.example

Best Practices

1. Use queueing - Always queue notifications to external services to prevent blocking requests
2. Handle failures gracefully - Implement proper error handling for channel delivery failures
3. Respect user preferences - Allow users to control which channels they receive notifications on
4. Test thoroughly - Test each channel independently before deploying to production
5. Monitor delivery - Track notification delivery rates and failures
6. Use staging credentials - Test with staging/sandbox credentials before using production keys

Related Commands

• /laravel-agent:queue:setup - Setup queue infrastructure for notifications
• /laravel-agent:model:make - Create models that can receive notifications
• /laravel-agent:migration:make - Create migrations for channel identifiers

Documentation Resources

• Laravel Notifications Documentation
• Laravel Notification Channels