This package makes it easy to send Twilio notifications with Laravel 5.5+, 6.x and 7.x
You are viewing the 3.x
documentation. Click here to view the 2.x
documentation.
You can install the package via composer:
composer require laravel-notification-channels/twilio
Add your Twilio Account SID, Auth Token, and From Number (optional) to your .env
:
TWILIO_USERNAME=XYZ # optional when using auth token
TWILIO_PASSWORD=ZYX # optional when using auth token
TWILIO_AUTH_TOKEN=ABCD # optional when using username and password
TWILIO_ACCOUNT_SID=1234 # always required
TWILIO_FROM=100000000 # optional default from
TWILIO_ALPHA_SENDER=HELLO # optional
TWILIO_DEBUG_TO=23423423423 # Set a number that call calls/messages should be routed to for debugging
TWILIO_SMS_SERVICE_SID=MG0a0aaaaaa00aa00a00a000a00000a00a # Optional but recommended
Run php artisan vendor:publish --provider="NotificationChannels\Twilio\TwilioProvider"
/config/twilio-notification-channel.php
Publish the config using the above command, and edit the ignored_error_codes
array. You can get the list of
exception codes from the documentation.
If you want to suppress all errors, you can set the option to ['*']
. The errors will not be logged but notification
failed events will still be emitted.
Twilio recommends always using a Messaging Service because it gives you access to features like Advanced Opt-Out, Sticky Sender, Scaler, Geomatch, Shortcode Reroute, and Smart Encoding.
Having issues with SMS? Check Twilio's best practices.
If you're upgrading from version 2.x
, you'll need to make sure that your set environment variables match those above
in the config section. None of the environment variable names have changed, but if you used different keys in your
services.php
config then you'll need to update them to match the above, or publish the config file and change the
env
key.
You should also remove the old entry for twilio
from your services.php
config, since it's no longer used.
The main breaking change between 2.x
and 3.x
is that failed notification will now throw an exception unless they are
in the list of ignored error codes (publish the config file to edit these).
You can replicate the 2.x
behaviour by setting 'ignored_error_codes' => ['*']
, which will case all exceptions to be
suppressed.
Now you can use the channel in your via()
method inside the notification:
use NotificationChannels\Twilio\TwilioChannel;
use NotificationChannels\Twilio\TwilioSmsMessage;
use Illuminate\Notifications\Notification;
class AccountApproved extends Notification
{
public function via($notifiable)
{
return [TwilioChannel::class];
}
public function toTwilio($notifiable)
{
return (new TwilioSmsMessage())
->content("Your {$notifiable->service} account was approved!");
}
}
You can also send an MMS:
use NotificationChannels\Twilio\TwilioChannel;
use NotificationChannels\Twilio\TwilioMmsMessage;
use Illuminate\Notifications\Notification;
class AccountApproved extends Notification
{
public function via($notifiable)
{
return [TwilioChannel::class];
}
public function toTwilio($notifiable)
{
return (new TwilioMmsMessage())
->content("Your {$notifiable->service} account was approved!")
->mediaUrl("https://picsum.photos/300");
}
}
Or create a Twilio call, using either an external TwiML url:
use NotificationChannels\Twilio\TwilioChannel;
use NotificationChannels\Twilio\TwilioCallMessage;
use Illuminate\Notifications\Notification;
class AccountApproved extends Notification
{
public function via($notifiable)
{
return [TwilioChannel::class];
}
public function toTwilio($notifiable)
{
return (new TwilioCallMessage())
->url("http://example.com/your-twiml-url");
}
}
Or create a Twilio call, and send a TwiML response directly:
use NotificationChannels\Twilio\TwilioChannel;
use NotificationChannels\Twilio\TwilioCallMessage;
use Illuminate\Notifications\Notification;
use Twilio\TwiML\VoiceResponse;
class AccountApproved extends Notification
{
public function via($notifiable)
{
return [TwilioChannel::class];
}
public function toTwilio($notifiable)
{
return (new TwilioCallMessage())
->twiml(
(new VoiceResponse())
->say('Hello world')
);
}
}
In order to let your Notification know which phone are you sending/calling to, the channel will look for the phone_number
attribute of the Notifiable model. If you want to override this behaviour, add the routeNotificationForTwilio
method to your Notifiable model.
public function routeNotificationForTwilio()
{
return '+1234567890';
}
from('')
: Accepts a phone to use as the notification sender.content('')
: Accepts a string value for the notification body.messagingServiceSid('')
: Accepts a messaging service SID to handle configuration.
from('')
: Accepts a phone to use as the notification sender.url('')
: Accepts an url for the call TwiML.twiml(VoiceResponse)
: Accepts a \Twilio\TwiML\VoiceResponse containing the call TwiML.
You can use either url() or twiml() on a TwilioCallMessage object, not both.
Please see CHANGELOG for more information what has changed recently.
$ composer test
If you discover any security related issues, please email [email protected] instead of using the issue tracker.
Please see CONTRIBUTING for details.
The MIT License (MIT). Please see License File for more information.