In this article, we're going to explore the notification system in the Laravel web framework. The notification system in Laravel allows you to send notifications to users over different channels. Today, we'll discuss how you can send notifications over the mail channel.
Basics of Notifications
During application development, you often need to notify users about different state changes. It could be either sending email notifications when the order status is changed or sending an SMS about their login activity for security purposes. In particular, we're talking about messages that are short and just provide insight into the state changes.
Laravel already provides a built-in feature which helps us achieve something similar—notifications. In fact, it makes sending notification messages to users a breeze and a fun experience!
The beauty of that approach is that it allows you to choose from different channels notifications will be sent on. Let's quickly go through the different notification channels supported by Laravel.
- Mail: The notifications will be sent in the form of email to users.
- SMS: As the name suggests, users will receive SMS notifications on their phone.
- Slack: In this case, the notifications will be sent on Slack channels.
- Database: This option allows you to store notifications in a database should you wish to build a custom UI to display it.
Among different notification channels, we'll use the mail channel in our example use-case which we're going to develop over the course of this tutorial.
In fact, it'll be a pretty simple use-case which allows users of our application to send messages to each user. When users receive a new message in their inbox, we'll notify them about this event by sending an email to them. Of course, we'll do that by using the notification feature of Laravel!
Create a Custom Notification Class
As we discussed earlier, we are going to set up an application which allows users of our application to send messages to each other. On the other hand, we'll notify users when they receive a new message from other users via email.
In this section, we'll create the files that are required in order to implement the use-case that we're looking for.
Create the Message Model
To start with, let's create the Message model, which holds messages sent by users to each other.
1 |
$php artisan make:model Message --migration |
We also need to add a few fields like to, from, and message to the messages table. So let's change the migration file before running the migrate command at database/migrations/XXXX_XX_XX_XXXXXX_create_messages_table.php.
1 |
<?php
|
2 |
|
3 |
use Illuminate\Database\Migrations\Migration; |
4 |
use Illuminate\Database\Schema\Blueprint; |
5 |
use Illuminate\Support\Facades\Schema; |
6 |
|
7 |
class CreateMessagesTable extends Migration |
8 |
{
|
9 |
/**
|
10 |
* Run the migrations.
|
11 |
*
|
12 |
* @return void
|
13 |
*/
|
14 |
public function up() |
15 |
{
|
16 |
Schema::create('messages', function (Blueprint $table) { |
17 |
$table->increments('id'); |
18 |
$table->integer('from', FALSE, TRUE); |
19 |
$table->integer('to', FALSE, TRUE); |
20 |
$table->text('message'); |
21 |
$table->timestamps(); |
22 |
});
|
23 |
}
|
24 |
|
25 |
/**
|
26 |
* Reverse the migrations.
|
27 |
*
|
28 |
* @return void
|
29 |
*/
|
30 |
public function down() |
31 |
{
|
32 |
Schema::dropIfExists('messages'); |
33 |
}
|
34 |
}
|
Now, let's run the migrate command, which creates the messages table in the database.
1 |
$php artisan migrate
|
That should create the messages table in the database.
Also, make sure that you have enabled the default Laravel authentication system first so that features like registration and login work out of the box. If you're not sure how to do that, the Laravel documentation will tell you how.
Create the NewMessage Notification Class
Since each notification in Laravel is represented by a separate class, we need to create a custom notification class that will be used to notify users. Let's use the following artisan command to create a custom notification class: NewMessage.
1 |
$php artisan make:notification NewMessage
|
That should create the app/Notifications/NewMessage.php class, so let's replace the contents of that file with the following contents.
1 |
<?php
|
2 |
|
3 |
namespace App\Notifications; |
4 |
|
5 |
use Illuminate\Bus\Queueable; |
6 |
use Illuminate\Contracts\Queue\ShouldQueue; |
7 |
use Illuminate\Notifications\Messages\MailMessage; |
8 |
use Illuminate\Notifications\Notification; |
9 |
|
10 |
class NewMessage extends Notification |
11 |
{
|
12 |
use Queueable; |
13 |
|
14 |
/**
|
15 |
* Create a new notification instance.
|
16 |
*
|
17 |
* @return void
|
18 |
*/
|
19 |
public function __construct() |
20 |
{
|
21 |
//
|
22 |
}
|
23 |
|
24 |
/**
|
25 |
* Get the notification's delivery channels.
|
26 |
*
|
27 |
* @param mixed $notifiable
|
28 |
* @return array
|
29 |
*/
|
30 |
public function via($notifiable) |
31 |
{
|
32 |
return ['mail']; |
33 |
}
|
34 |
|
35 |
/**
|
36 |
* Get the mail representation of the notification.
|
37 |
*
|
38 |
* @param mixed $notifiable
|
39 |
* @return \Illuminate\Notifications\Messages\MailMessage
|
40 |
*/
|
41 |
public function toMail($notifiable) |
42 |
{
|
43 |
return (new MailMessage) |
44 |
->line('The introduction to the notification.') |
45 |
->action('Notification Action', url('/')) |
46 |
->line('Thank you for using our application!'); |
47 |
}
|
48 |
|
49 |
/**
|
50 |
* Get the array representation of the notification.
|
51 |
*
|
52 |
* @param mixed $notifiable
|
53 |
* @return array
|
54 |
*/
|
55 |
public function toArray($notifiable) |
56 |
{
|
57 |
return [ |
58 |
//
|
59 |
];
|
60 |
}
|
61 |
}
|
As we're going to use the mail channel to send notifications to users, the via method is configured accordingly. So this method allows you to configure the channel type of a notification.
Next, there's the toMail method, which allows you to configure various email parameters. In fact, the toMail method should return the instance of \Illuminate\Notifications\Messages\MailMessage, and it provides useful methods that allow you to configure email parameters.
Among various methods, the line method allows you to add a single line in a message. On the other hand, there's the action method, which allows you to add a call-to-action button in a message.
In this way, you could format a message which will be sent to users. So that's how you're supposed to configure the notification class while you're using the mail channel to send notifications.
At the end, you need to make sure that you implement the necessary methods according to the channel type configured in the via method. For example, if you're using the database channel, which stores notifications in a database, you don't need to configure the toMail method; instead, you should implement the toArray method, which formats the data that needs to be stored in a database.
How to Send Notifications
In the previous section, we created a notification class which is ready to send notifications. In this section, we'll create files that demonstrate how you could actually send notifications using the NewMessage notification class.
Let's create a controller file at app/Http/Controllers/NotificationController.php with the following contents.
1 |
<?php
|
2 |
namespace App\Http\Controllers; |
3 |
|
4 |
use App\Http\Controllers\Controller; |
5 |
use App\Message; |
6 |
use App\User; |
7 |
use App\Notifications\NewMessage; |
8 |
use Illuminate\Support\Facades\Notification; |
9 |
|
10 |
class NotificationController extends Controller |
11 |
{
|
12 |
public function __construct() |
13 |
{
|
14 |
$this->middleware('auth'); |
15 |
}
|
16 |
|
17 |
public function index() |
18 |
{
|
19 |
// user 2 sends a message to user 1
|
20 |
$message = new Message; |
21 |
$message->setAttribute('from', 2); |
22 |
$message->setAttribute('to', 1); |
23 |
$message->setAttribute('message', 'Demo message from user 2 to user 1.'); |
24 |
$message->save(); |
25 |
|
26 |
$fromUser = User::find(2); |
27 |
$toUser = User::find(1); |
28 |
|
29 |
// send notification using the "user" model, when the user receives new message
|
30 |
$toUser->notify(new NewMessage($fromUser)); |
31 |
|
32 |
// send notification using the "Notification" facade
|
33 |
Notification::send($toUser, new NewMessage($fromUser)); |
34 |
}
|
35 |
}
|
Of course, you need to add an associated route in the routes/web.php file.
1 |
Route::get('notify/index', 'NotificationController@index'); |
There are two ways Laravel allows you to send notifications: by using either the notifiable entity or the Notification facade.
If the entity model class utilizes the Illuminate\Notifications\Notifiable trait, then you could call the notify method on that model. The App\User class implements the Notifiable trait, and thus it becomes the notifiable entity. On the other hand, you could also use the Illuminate\Support\Facades\Notification Facade to send notifications to users.
Let's go through the index method of the controller.
In our case, we're going to notify users when they receive a new message. So we've tried to mimic that behavior in the index method in the first place.
Next, we've notified the recipient user about a new message using the notify method on the $toUser object, as it's the notifiable entity.
1 |
$toUser->notify(new NewMessage($fromUser)); |
You may have noticed that we also pass the $fromUser object in the first argument of the __construct method, since we want to include the from username in a message.
On the other hand, if you want to mimic it using the Notification facade, it's pretty easy to do so using the following snippet.
1 |
Notification::send($toUser, new NewMessage($fromUser)); |
As you can see, we've used the send method of the Notification facade to send a notification to a user.
Go ahead and open the URL https://your-laravel-site-domain/notify/index in your browser. If you're not logged in yet, you'll be redirected to the login screen. Once you're logged in, you should receive a notification email at the email address which is attached with the user 1.
You may be wondering how the notification system detects the to address when we haven't configured it anywhere yet. In that case, the notification system tries to find the email property in the notifiable object. And the App\User object class already has that property since we're using the default Laravel authentication system.
However, if you would like to override this behavior and you want to use a different property other than email, you just need to define the following method in your notification class.
1 |
public function routeNotificationForMail() |
2 |
{
|
3 |
return $this->email_address; |
4 |
}
|
Now, the notification system should look for the email_address property instead of the email property to fetch the to address.
And that's how to use the notification system in Laravel. That brings us to the end of this article as well!
Conclusion
What we've gone through today is one of the most useful yet least discussed features in Laravel—notifications. It allows you to send notifications to users over different channels.
After a quick introduction, we implemented a real-world example which demonstrated how to send notifications over the mail channel. In fact, it's really handy in the case of sending short messages about state changes in your application.
For those of you who are either just getting started with Laravel or looking to expand your knowledge, site, or application with extensions, we have a variety of things you can study on Envato Market.
