Creating notifications in Laravel - Visual Walkthrough

Concept Flow - Creating notifications

Define Notification Class

↓

Set Notification Channels

↓

Create Notification Content

↓

Trigger Notification

↓

Notification Sent to User

↓

User Receives Notification

This flow shows how Laravel creates and sends notifications step-by-step from defining to delivering.

Execution Sample

Laravel

use Illuminate\Notifications\Notification;
use Illuminate\Notifications\Messages\MailMessage;

class InvoicePaid extends Notification {
  public function via($notifiable) { return ['mail']; }
  public function toMail($notifiable) {
    return (new MailMessage)->line('Invoice paid.');
  }
}

$user->notify(new InvoicePaid());

This code defines a notification class and sends an email notification to a user.

Execution Table

Step	Action	Evaluation	Result
1	Define InvoicePaid class extending Notification	Class created	Notification class ready
2	Call via() method	Returns ['mail']	Channels set to mail
3	Call toMail() method	Creates MailMessage with text 'Invoice paid.'	Mail content prepared
4	Call notify() on user with InvoicePaid instance	Notification dispatched	Notification queued for sending
5	Mail system sends email	Email sent to user's email address	User receives notification email
6	End	No more actions	Notification process complete

💡 Notification sent and process ends

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
$notification	null	InvoicePaid instance created	MailMessage prepared	Notification dispatched	Notification sent
$channels	null	['mail']	['mail']	['mail']	['mail']
$mailMessage	null	null	MailMessage with 'Invoice paid.'	MailMessage queued	MailMessage sent

Key Moments - 3 Insights

Why do we need the via() method in the notification class?

The via() method tells Laravel which channels to use for sending the notification, as shown in step 2 of the execution_table.

What happens if we forget to call notify() on the user?

Without calling notify(), the notification is never dispatched, so no notification is sent. This is shown by the absence of step 4 in the execution_table.

How does Laravel know what content to send in the notification?

Laravel calls the channel-specific method like toMail() to get the content, as shown in step 3 where MailMessage is prepared.

Visual Quiz - 3 Questions

Look at the execution_table, what does the via() method return at step 2?

A null

B ['database']

C ['mail']

D ['sms']

💡 Hint

Check the 'Evaluation' column in step 2 of the execution_table.

At which step is the notification actually sent to the user?

A Step 5

B Step 4

C Step 3

D Step 6

💡 Hint

Look for when the mail system sends the email in the execution_table.

If we change via() to return ['database'], what changes in the execution_table?

A Step 5 sends an email as usual

B Step 3 calls toArray() instead of toMail()

C Step 4 is skipped

D Notification is never dispatched

💡 Hint

Consider which channel method Laravel calls based on via() return value.

Concept Snapshot

Laravel notifications:
- Create a Notification class
- Define via() to set channels (mail, database, etc.)
- Define channel methods (toMail, toArray)
- Call notify() on user to send
- Laravel sends notification via chosen channels

Full Transcript

In Laravel, creating notifications involves defining a Notification class with methods to specify channels and content. The via() method returns an array of channels like 'mail'. Laravel calls the corresponding method like toMail() to build the notification content. Then, calling notify() on a user sends the notification through the specified channels. This process ensures users receive messages like emails or database alerts. The execution steps show defining the class, setting channels, preparing content, dispatching, and sending the notification.

Practice

1. What is the primary purpose of notifications in Laravel?

easy

A. To inform users about important events or updates

B. To create database tables automatically

C. To handle user authentication

D. To optimize application performance

Solution

1. Step 1: Understand the role of notifications

   Notifications are designed to keep users informed about events or updates in the application.

2. Step 2: Compare with other options

   Creating tables, authentication, and performance optimization are unrelated to notifications.

3. Final Answer:

   To inform users about important events or updates -> Option A

4. Quick Check:

   Notifications = Inform users [OK]

Hint: Notifications inform users about events [OK]

Common Mistakes:

• Confusing notifications with database migrations
• Thinking notifications handle authentication
• Assuming notifications improve performance directly

2. Which artisan command is used to create a new notification class in Laravel?

easy

A. php artisan make:notify NotificationName

B. php artisan generate:notification NotificationName

C. php artisan create:notification NotificationName

D. php artisan make:notification NotificationName

Solution

1. Step 1: Recall the artisan command for notifications

   The correct command to create a notification class is php artisan make:notification followed by the notification name.

2. Step 2: Identify incorrect commands

   Other commands like make:notify, create:notification, or generate:notification do not exist in Laravel.

3. Final Answer:

   php artisan make:notification NotificationName -> Option D

4. Quick Check:

   Use make:notification to create notifications [OK]

Hint: Use 'make:notification' with artisan [OK]

Common Mistakes:

• Using 'make:notify' instead of 'make:notification'
• Confusing 'create' or 'generate' commands
• Omitting the notification class name

3. Given this code snippet, what will be the result?

use App\Notifications\InvoicePaid;
$user = User::find(1);
$user->notify(new InvoicePaid($invoice));

medium

A. Throws an error because notify() is not a valid method

B. Sends an InvoicePaid notification to the user with ID 1

C. Creates a new user with an InvoicePaid notification

D. Deletes the user with ID 1 after notification

Solution

1. Step 1: Understand the notify() method

   The notify() method sends the given notification instance to the user model.

2. Step 2: Analyze the code behavior

   The code finds the user with ID 1 and sends them the InvoicePaid notification.

3. Final Answer:

   Sends an InvoicePaid notification to the user with ID 1 -> Option B

4. Quick Check:

   notify() sends notification to user [OK]

Hint: notify() sends notification to the user model [OK]

Common Mistakes:

• Thinking notify() creates or deletes users
• Assuming notify() is not a valid method
• Confusing notification sending with user creation

4. Identify the error in this notification sending code:

$user = User::find(5);
$user->notify(InvoicePaid);

medium

A. InvoicePaid should be instantiated with new keyword

B. User::find should be User::get

C. notify() method does not exist on User model

D. User ID 5 does not exist

Solution

1. Step 1: Check how notifications are sent

   The notify() method requires a notification instance, so InvoicePaid must be created with new InvoicePaid().

2. Step 2: Verify other parts

   User::find(5) is correct to get a user by ID, and notify() exists on the User model. User existence is not guaranteed but not a syntax error.

3. Final Answer:

   InvoicePaid should be instantiated with new keyword -> Option A

4. Quick Check:

   Notifications need new instance [OK]

Hint: Always use 'new' to create notification instances [OK]

Common Mistakes:

• Passing class name without instantiation
• Using User::get instead of find for single user
• Assuming notify() method is missing

5. You want to send a notification only via email and database channels. Which method should you define in your notification class to specify these channels?

hard

A. public function sendChannels() { return ['mail', 'database']; }

B. public function channels() { return ['email', 'db']; }

C. public function via($notifiable) { return ['mail', 'database']; }

D. public function notifyChannels() { return ['email', 'database']; }

Solution

1. Step 1: Recall the via() method role

   In Laravel notifications, the via() method defines which channels the notification uses.

2. Step 2: Check correct channel names and method signature

   The method must accept the $notifiable parameter and return an array with channel names like 'mail' and 'database'. Other method names or channel names are incorrect.

3. Final Answer:

   public function via($notifiable) { return ['mail', 'database']; } -> Option C

4. Quick Check:

   via() defines notification channels [OK]

Hint: Use via() method to list channels [OK]

Common Mistakes:

• Using wrong method names like channels()
• Using incorrect channel names like 'email' instead of 'mail'
• Omitting the $notifiable parameter