Weave Code
Laravel Notification Whatsapp Laravel Package
netflie/laravel-notification-whatsapp
Send WhatsApp notifications from your Laravel app using this channel for the built-in notification system. It supports multiple drivers, queued messages, and a simple API for delivering text and media messages to your users.
Laravel notification channel for Whatsapp Cloud API
Frequently asked questions about Laravel Notification Whatsapp
- How do I install and configure netflie/laravel-notification-whatsapp for Laravel?
- Install it with Composer using composer require netflie/laravel-notification-whatsapp, then publish the package configuration. Add your WhatsApp Business API phone number ID, access token, and other required credentials to your environment variables. The package provides the Laravel notification channel plumbing, but you still need an approved Meta WhatsApp Business account and templates before messages can be delivered.
- Does netflie/laravel-notification-whatsapp support Laravel 12?
- Yes. The 1.4.0 release adds Laravel 12 support by widening the illuminate/notifications and illuminate/support constraints. Teams on Laravel 12 can adopt the channel without workarounds. You should still confirm the supported PHP version range and check Composer constraints if you are upgrading Laravel at the same time.
- What credentials are required to send WhatsApp notifications from Laravel?
- You need a WhatsApp Business API account from Meta, a phone number ID, an access token, and approved message templates. These values are configured through the package configuration and environment variables. The package handles the Laravel-side channel, but Meta controls account setup and template approval.
- How do I send a WhatsApp notification from a Laravel Notifiable model?
- Use Laravel's built-in notification system and add the WhatsApp channel to your notification's via method. Implement the message payload using the package's simple text and media API, then send the notification to any Notifiable model. It works alongside existing email, SMS, and push channels without a separate messaging abstraction.
- Are queued WhatsApp notifications supported by this package?
- Yes, the package is designed to work with Laravel's notification queueing, so high-volume WhatsApp notifications can be queued like other notification channels. You should still configure workers and monitor throughput because WhatsApp Cloud API rate limits and pricing apply. Queueing does not bypass Meta template approval or the 24-hour customer service window.
- Can I send images, documents, audio, and other media through the WhatsApp channel?
- The package supports text and media messages, including document messages with an optional filename in 1.4.0. For other media types, rely on the package's media API and confirm support for your specific format against the WhatsApp Cloud API requirements. Existing document calls are non-breaking because the filename parameter is optional.
- Do I need approved WhatsApp message templates to use this Laravel package?
- Yes. WhatsApp Business API requires approved message templates, and the package handles the Laravel-side sending rather than the Meta approval process. You should plan template creation and approval as part of integration, especially for business-initiated messages. The 24-hour customer service window also affects when free-form messages are allowed.
- How are WhatsApp API errors and rate limits handled by netflie/laravel-notification-whatsapp?
- The package handles Laravel-side notification plumbing, but WhatsApp Cloud API errors and rate limits come from Meta and must be handled in your application. In practice, catch exceptions from sending, add retry or backoff logic where appropriate, and log failures for monitoring. Template rejections and policy restrictions should also be surfaced to your team.
- What are the main production risks of using WhatsApp Cloud API notifications in Laravel?
- The main risks are external: WhatsApp Business API policy changes, rate limits, template approval workflows, per-message pricing, and the 24-hour customer service window. The package itself is stable for the 1.4.0 release with no breaking changes, but maintenance risk is moderate because it depends on a single maintainer. Secure your API tokens and phone number ID using standard Laravel secret management.
- Is upgrading from 1.3.0 to 1.4.0 of netflie/laravel-notification-whatsapp safe?
- Yes, the 1.4.0 release is non-breaking. Existing calls to the document method continue to work, and the new filename parameter is optional. Update composer.json, run composer update, and optionally adopt the filename parameter where you need named file attachments.
Weaver
How can I help you explore Laravel packages today?