Weave Code
Plivo Laravel Package
laravel-notification-channels/plivo
Send SMS notifications through Plivo in Laravel. This channel plugs into Laravel's notification system so you can deliver text messages via the Plivo API using a simple toPlivo method on your notifications, with support for configuring the sender ID and recipient numbers.
Plivo SMS notifications driver for Laravel
Frequently asked questions about Plivo
- How do I install laravel-notification-channels/plivo?
- Run composer require laravel-notification-channels/plivo. Then add Plivo credentials to config/services.php and implement routeNotificationForPlivo on your notifiable model. Because the last tagged release is from June 2021, expect to resolve illuminate/support constraints for modern Laravel versions, possibly with a fork or inline reimplementation.
- Does this package support Laravel 10 or Laravel 11?
- Compatibility is unverified. The last release was 2021-06-17, so its illuminate/support constraint almost certainly predates Laravel 10 and 11. Run a spike with your exact PHP and Laravel versions before adopting; be prepared to bump constraints in a fork or reimplement the roughly 100-200 lines of glue code.
- How do I send an SMS with a Laravel notification using Plivo?
- Add PlivoChannel to the via() array of your notification and return a PlivoMessage from a toPlivo method. The channel builds the from, to, and body payload and calls the official plivo/plivo-php client's message create endpoint. Your notifiable must expose routeNotificationForPlivo() so the channel knows the recipient number.
- How do I configure Plivo credentials and sender ID in Laravel?
- Add PLIVO_AUTH_ID and PLIVO_AUTH_TOKEN to config/services.php, typically sourced from environment variables. Configure the sender ID through the PlivoMessage you build in your notification. Credentials are read by the thin wrapper around the Plivo REST client and are not persisted by the package.
- What is routeNotificationForPlivo and how do I set the recipient number?
- routeNotificationForPlivo() is the Laravel notification routing hook that returns the destination phone number for a notifiable. Implement it on your model or user class so the channel can pass that number as the to value in the PlivoMessage. You can also use Notification::route() for on-demand notifications without a persisted notifiable.
- Is laravel-notification-channels/plivo still maintained and safe for production?
- Treat it as unmaintained by default. The last release was June 2021, it has 9 stars and zero dependents, and there is no observable production validation against current Laravel or Plivo SDK versions. For revenue-path SMS, fork and maintain it or reimplement the small adapter in-house behind your own interface.
- What are alternatives to this package if I need a maintained Laravel SMS channel?
- If the vendor is still open, laravel-notification-channels/twilio or Vonage has orders of magnitude more usage and maintenance. If you must use Plivo, the practical alternatives are forking this package with a bumped illuminate/support constraint and updated SDK calls, or writing a small in-house SmsChannel. The in-house route also lets you add idempotency and structured error mapping by design.
- Can I queue Plivo SMS notifications in Laravel?
- Yes. Because the package is a thin notification channel, it composes with Laravel's queue system through ShouldQueue on your notification. The package has no queue of its own and adds no persistence layer, so standard queue workers and retries apply. Just verify the Plivo API call is safe to retry for your use case.
- Does it support delivery receipts, two-way messaging, or MMS?
- No, not out of the box. Notification channels of this vintage typically omit delivery receipts, webhooks, two-way messaging, MMS edge cases, idempotency keys, per-message rate limiting, and structured error typing. If you need those capabilities, this package is a starting point rather than a complete solution.
- How do I test Plivo notifications in Laravel and what errors does it throw?
- Expect a generic PlivoException to be thrown into the notification pipeline on API failures, without structured error typing. For tests, fake or swap the underlying Plivo client or use Laravel's notification fakes, and run a spike against the real API in staging. Verify the plivo/plivo-php SDK version and method signatures before relying on it.
Weaver
How can I help you explore Laravel packages today?