This package makes it easy to send notifications using Twitter with Laravel. If you have an older Laravel application, you can use version 1.*. But be aware that these versions are no longer maintained.
- About
- Installation
- Setting up the Twitter service
- Usage
- Handle multiple Twitter Accounts
- Changelog
- Testing
- Security
- Contributing
- Credits
- License
This package is part of the Laravel Notification Channels project. It provides additional Laravel Notification channels to the ones given by Laravel itself.
The Twitter channel makes it possible to send out Laravel notifications as a Twitter status update
(post on the timeline) or as a direct message
.
If you prefer a video, there is also an introduction video available for you. If not, just read on.
You can install this package via composer:
composer require laravel-notification-channels/twitter
The service provider gets loaded automatically.
You will need to create a Twitter app to use this channel. Within this app, you will find the keys and access tokens
. Place them inside your .env
file. To load them, add this to your config/services.php
file:
...
'twitter' => [
'consumer_key' => env('TWITTER_CONSUMER_KEY'),
'consumer_secret' => env('TWITTER_CONSUMER_SECRET'),
'access_token' => env('TWITTER_ACCESS_TOKEN'),
'access_secret' => env('TWITTER_ACCESS_SECRET')
]
...
This will load the Twitter app data from the .env
file. Make sure to use the same keys you have used there like TWITTER_CONSUMER_KEY
.
To use this package, you need to create a notification class, like NewsWasPublished
from the example below, in your Laravel application. Make sure to check out Laravel's documentation for this process.
<?php
use NotificationChannels\Twitter\TwitterChannel;
use NotificationChannels\Twitter\TwitterStatusUpdate;
class NewsWasPublished extends Notification
{
/**
* Get the notification's delivery channels.
*
* @param mixed $notifiable
* @return array
*/
public function via($notifiable)
{
return [TwitterChannel::class];
}
public function toTwitter($notifiable)
{
return new TwitterStatusUpdate('Laravel notifications are awesome!');
}
}
Take a closer look at the toTwitter
method. Here we define what kind of Twitter message we want to trigger. In this case, it is a status update message, which is just a new message in your timeline.
public function toTwitter($notifiable)
{
return new TwitterStatusUpdate('Laravel notifications are awesome!');
}
It is possible to publish images with your status update too. You have to pass the image path to the withImage
method.
public function toTwitter($notifiable)
{
return (new TwitterStatusUpdate('Laravel notifications are awesome!'))->withImage('marcel.png');
}
If you want to use multiple images, just pass an array of paths.
return (new TwitterStatusUpdate('Laravel notifications are awesome!'))->withImage([
public_path('marcel.png'),
public_path('mohamed.png')
]);
To send a Twitter direct message to a specific user, you will need the TwitterDirectMessage
class. Provide the Twitter user handler as the first parameter and the the message as the second one.
public function toTwitter($notifiable)
{
return new TwitterDirectMessage('marcelpociot', 'Hey Marcel, it was nice meeting you at the Laracon.');
}
You can also provide the user ID
instead of the screen name
. This would prevent an extra Twitter API call. Make sure to pass it as an integer when you do.
public function toTwitter($notifiable)
{
return new TwitterDirectMessage(12345, 'Hey Marcel, it was nice meeting you at the Laracon.');
}
There might be cases where you need to handle multiple Twitter accounts. This means you need to be able to change the provided keys and tokens of your Twitter app. Luckily, Laravel can help you here. In your notifiable model, you can define the routeNotifiactionForTwitter
method. Here you can override the provided settings.
public function routeNotificationForTwitter($notification)
{
return [
'TWITTER_CONSUMER_KEY',
'TWITTER_CONSUMER_SECRET',
'TWITTER_ACCESS_TOKEN',
'TWITTER_ACCESS_SECRET',
];
}
Please see CHANGELOG for more information about what has changed recently.
$ composer test
If you discover any security-related issues, please email c.rumpel@kabsi.at instead of using the issue tracker.
Please see CONTRIBUTING for details.
The MIT License (MIT). Please see License File for more information.