In this section, we will see how Laravel 11 handles notifications and emails within an API context. Whether you're building a ping service or any application that requires user communication, you’ll likely need to notify users when certain actions occur, such as a service failure. Let's walk through the process of generating a notification, sending it via email, and integrating different communication channels like Slack or SMS.

Setting Up Notifications

We all use emails, but sometimes we need more dynamic notifications. In our example, when a check fails in a ping service, we want to notify the user immediately. Laravel makes it simple to send notifications through various channels.

php artisan make:notification CheckFailed

This command generates a notification class called CheckFailed. Now, we’ll decide how to send this notification—via email, Slack, or SMS. For now, let's focus on email.

Find out more about notifications in Laravel Notifications Documentation

Sending Emails When a Check Fails

In our example, whenever a check fails, we’ll trigger an email alert. Here’s how we can configure the email notification:

public function toMail($notifiable)
{
    return (new MailMessage)
        ->subject('Service Check Failed')
        ->line('We just checked your service, and it seems to be down.')
        ->action('Check Service Status', url('/'))
        ->line('Thank you for using our application!');
}

This email will be sent whenever a check fails, alerting the user about the service downtime.

Tip: Consider using queues to handle email notifications asynchronously to prevent performance issues. Learn more about Laravel Queues.

Handling Status Codes

We want to ensure that our notification only triggers when a specific HTTP status code is returned, such as a 200 OK. If the service returns anything else (e.g., 404 Not Found), the notification will be triggered.

if ($response->status() !== 200) {
    $user->notify(new CheckFailed($check));
}

By checking the status code, we ensure that we only send notifications when the service fails to respond as expected.

Optimizing Queue Handling

One of the best practices in Laravel is to use queues for tasks like sending emails. It prevents the application from slowing down when multiple notifications are being processed.

class CheckFailed extends Notification implements ShouldQueue
{
    // Notification logic here
}

By implementing the ShouldQueue interface, you’re telling Laravel to handle this notification in the background, improving overall performance.

Learn more about Laravel Queues.

Using Observers to Trigger Notifications

Laravel Observers are another powerful tool to automate tasks. In our example, we can create an observer that triggers when a new report is created.

php artisan make:observer ReportObserver

In this observer, we'll notify the user when a report is created and associated with a failed check:

public function created(Report $report): void
{
    $user = $report->check->service->user;
    $user->notify(new CheckFailed($report->check));
}

This ensures that users are notified immediately whenever a new report indicates a failure in the system.

Want to learn more? Check out the official Laravel Observers Documentation.

Multiple Notification Channels

Laravel supports sending notifications across multiple channels, not just email. If you need to notify users via Slack, SMS, or WebSockets, Laravel has built-in support for these methods. You can even combine channels to ensure users get notified no matter what.

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

This allows you to send the same notification via email and Slack, ensuring that users are always in the loop.

Learn more: Laravel Notification Channels

Summary

In this segment, we’ve explored how to send notifications and emails using Laravel 11. From triggering notifications when a service check fails to optimizing performance with queues, Laravel provides a flexible system to manage user alerts. Don't forget to check out the official Laravel SDK and explore further channels like WebSockets for real-time notifications.