Notification channels (mail, database, SMS) in Laravel - Step-by-Step Execution

Concept Flow - Notification channels (mail, database, SMS)

Trigger Notification Event

↓

Notification Class Called

↓

Determine Channels: mail, database, SMS

↓

User Receives Notification via Chosen Channels

When a notification is triggered, Laravel calls the notification class, determines which channels to use, then sends the notification via mail, stores it in the database, or sends an SMS.

Execution Sample

Laravel

Notification::send($user, new InvoicePaid($invoice));

// In InvoicePaid Notification class
public function via($notifiable) {
  return ['mail', 'database', 'sms'];
}

This code sends a notification to a user via mail, database, and SMS channels.

Execution Table

Step	Action	Channel	Result	Notes
1	Trigger Notification::send	All	Notification class InvoicePaid instantiated	Start sending notification
2	Call via() method	All	Channels returned: mail, database, sms	Determines channels to send
3	Send mail	mail	Email sent to user email address	Uses mail driver configured in Laravel
4	Save notification	database	Notification record saved in notifications table	Stores data for user to view later
5	Send SMS	sms	SMS sent to user phone number	Uses configured SMS gateway service
6	Complete	All	User receives notification via all channels	Process ends

💡 All specified channels processed, notification delivery complete

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	Final
$channels	null	['mail', 'database', 'sms']	['mail', 'database', 'sms']	['mail', 'database', 'sms']	['mail', 'database', 'sms']	['mail', 'database', 'sms']
$notificationStatus	not sent	pending	mail sent	mail sent, db saved	mail sent, db saved, sms sent	all sent

Key Moments - 3 Insights

Why does Laravel call the via() method before sending notifications?

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

How does Laravel handle sending notifications to multiple channels?

Laravel processes each channel one by one, sending mail, saving to database, and sending SMS separately, as seen in steps 3, 4, and 5.

What happens if one channel fails to send the notification?

Laravel attempts each channel independently; failure in one does not stop others. This is implied by separate steps for each channel.

Visual Quiz - 3 Questions

Look at the execution_table, what channels are returned by the via() method at step 2?

A ['database', 'sms']

B ['mail']

C ['mail', 'database', 'sms']

D []

💡 Hint

Check the 'Result' column at step 2 in the execution_table.

At which step is the notification saved to the database?

A Step 3

B Step 4

C Step 5

D Step 1

💡 Hint

Look for the 'database' channel action in the execution_table.

If the SMS channel was removed from via(), how would the execution_table change?

A Step 5 would be missing

B Step 3 would be missing

C Step 4 would be missing

D No change

💡 Hint

Compare the channels listed in step 2 and the following steps.

Concept Snapshot

Laravel Notification Channels:
- Use via() method to specify channels like 'mail', 'database', 'sms'.
- Laravel sends notifications on each channel separately.
- Mail sends email, database stores notification, SMS sends text message.
- Channels run independently; failure in one doesn't stop others.
- Configure each channel in Laravel settings before use.

Full Transcript

In Laravel, when you want to notify a user, you create a notification class and define which channels to use in the via() method. When Notification::send is called, Laravel checks the channels and sends the notification through each one: mail sends an email, database saves a record, and SMS sends a text message. Each channel works independently, so if one fails, others still run. This process ensures users get notified in multiple ways depending on your app's setup.

Practice

1. In Laravel notifications, which method defines the channels a notification will be sent through?

easy

A. via

B. send

C. channels

D. notify

Solution

1. Step 1: Understand the notification class structure

   Laravel notifications use a method to specify which channels to send the notification through.

2. Step 2: Identify the method name

   The method that returns an array of channels is named via.

3. Final Answer:

   via -> Option A

4. Quick Check:

   Channel selection method = via [OK]

Hint: Remember: 'via' means 'through' which fits channel selection [OK]

Common Mistakes:

• Confusing 'send' with 'via' method
• Using 'channels' instead of 'via'
• Assuming 'notify' defines channels

2. Which of the following is the correct syntax to specify the mail channel in the via method of a Laravel notification?

easy

A. return mail();

B. return 'mail';

C. return ['mail'];

D. return ['MailChannel'];

Solution

1. Step 1: Check the return type of the via method

   The via method must return an array of channel names as strings.

2. Step 2: Identify the correct array syntax

   Returning ['mail'] is correct; returning a string or function call is incorrect.

3. Final Answer:

   return ['mail']; -> Option C

4. Quick Check:

   Channel list must be an array of strings [OK]

Hint: Always return an array of channel names in via [OK]

Common Mistakes:

• Returning a string instead of an array
• Calling a function instead of returning array
• Using incorrect channel class names

3. Given this Laravel notification code snippet, what will be stored in the database when the notification is sent?

public function toDatabase($notifiable) {
    return [
        'invoice_id' => 1234,
        'amount' => 250
    ];
}

medium

A. Only the 'invoice_id' value 1234

B. An array with keys 'invoice_id' and 'amount' and their values

C. A JSON string of the notification class name

D. An error because toDatabase must return a string

Solution

1. Step 1: Understand the toDatabase method role

   The toDatabase method returns an array of data saved in the notifications table.

2. Step 2: Analyze the returned array

   The array contains keys 'invoice_id' and 'amount' with values 1234 and 250 respectively.

3. Final Answer:

   An array with keys 'invoice_id' and 'amount' and their values -> Option B

4. Quick Check:

   toDatabase returns array data saved in DB [OK]

Hint: toDatabase returns array data stored in notifications table [OK]

Common Mistakes:

• Expecting a string instead of array
• Thinking only one key is saved
• Confusing toMail with toDatabase

4. Identify the error in this Laravel notification class snippet for sending SMS via Nexmo:

public function via($notifiable) {
    return ['nexmo'];
}

public function toNexmo($notifiable) {
    return (new NexmoMessage)->content('Hello!');
}

medium

A. Method name should be toSms, not toNexmo

B. The content method is not valid for NexmoMessage

C. The via method should return 'sms' instead of 'nexmo'

D. NexmoMessage class is not imported or aliased

Solution

1. Step 1: Check method names and channel names

   Using 'nexmo' in via and method toNexmo is correct for SMS via Nexmo.

2. Step 2: Verify class usage

   The NexmoMessage class must be imported with use statement or aliased; missing import causes error.

3. Final Answer:

   NexmoMessage class is not imported or aliased -> Option D

4. Quick Check:

   Missing import causes class not found error [OK]

Hint: Always import notification channel classes before use [OK]

Common Mistakes:

• Renaming toNexmo incorrectly
• Returning wrong channel name in via
• Misusing content method on NexmoMessage

5. You want to send a Laravel notification via mail, database, and SMS (Nexmo). Which of the following via method implementations correctly sets all three channels?

hard

A. return ['mail', 'database', 'nexmo'];

B. return ['mail', 'database', 'sms'];

C. return ['MailChannel', 'DatabaseChannel', 'NexmoChannel'];

D. return ['mail', 'db', 'nexmo'];

Solution

1. Step 1: Recall correct channel names for Laravel notifications

   Laravel uses lowercase strings 'mail', 'database', and 'nexmo' to specify channels.

2. Step 2: Compare options for correct channel names

   return ['mail', 'database', 'nexmo']; uses correct channel names; others use incorrect or non-existent names.

3. Final Answer:

   return ['mail', 'database', 'nexmo']; -> Option A

4. Quick Check:

   Use exact channel strings in via array [OK]

Hint: Use exact lowercase channel names: mail, database, nexmo [OK]

Common Mistakes:

• Using 'sms' instead of 'nexmo'
• Using class names instead of strings
• Using shorthand like 'db' instead of 'database'