- How do I install the Filament WhatsApp connector package?
- Install it with composer require wallacemartinss/filament-whatsapp-conector, then publish the config and migrations and register the plugin in your Filament panel provider. Add the package views and src paths to your Tailwind @source entries and rebuild your panel assets. Put the Evolution API URL and API key in your env file; credentials are never stored in the database.
- Does this package support Laravel 11 and Laravel 12?
- Yes. The package requires PHP 8.2 or newer, Laravel 11.x or 12.x, Filament v5, and Livewire v4. The Filament v5 and Livewire v4 requirements are strict, so panels still on Filament v3 or v4 need an upgrade before adoption.
- Do I need a running Evolution API instance to use this plugin?
- Yes. This is a Filament plugin and HTTP client for an external Evolution API v2 instance; it does not implement WhatsApp itself. You need a running Evolution API v2 deployment, its URL and API key, and a queue worker for webhook processing and sending. Interactive messages require Evolution API v2.4.0 or newer.
- How does multi-tenancy work with this WhatsApp plugin?
- The plugin supports Filament's native multi-tenancy by adding a team_id column to its own tables and relying on Filament's tenant scoping. It assumes one Evolution API deployment and one API key configured through env, not per-tenant credentials or per-tenant Evolution instances. If you need stronger isolation, such as separate instances, keys, or webhook secrets per tenant, you will need to design around that config model.
- How do I send a WhatsApp message from my Laravel code?
- Use the Whatsapp facade or the CanSendWhatsappMessage trait in your own services, choosing the message type through MessageTypeEnum. For the UI, the package ships SendWhatsappMessageAction, which you can drop into any Filament page or table action. Sending and webhook processing rely on queue workers being running in every environment, including staging.
- What message types can I send with this package?
- The package can send text, images, videos, audio, and documents, plus interactive reply buttons, lists, CTA, PIX, and carousel messages. Interactive types require Evolution API v2.4.0 or newer, while the basic message types work on any Evolution API v2 release.
- How are incoming WhatsApp webhooks handled and secured?
- Inbound events from Evolution API are received on a webhook route protected by a shared secret configured in env, and the plugin can persist messages and webhook logs. Before production, confirm that the secret is compared in constant time and decide whether you also need source IP checks or payload signature validation. An unauthenticated webhook that writes to your database is an attack surface.
- Is this Filament WhatsApp package production-ready?
- Treat it as an early-adopter package. It has a small ecosystem footprint, a single maintainer, around 70 stars, and no listed test suite or CI badges, so you are effectively a co-tester. Pin versions carefully because Filament v5, Livewire v4, and Evolution API v2.4.0+ are independent breakage points. Also assess the compliance risk of using the unofficial Evolution API bridge rather than Meta's official Cloud API.
- What are the retention and PII concerns with message storage?
- By default the package persists messages and webhook payloads, with configurable message and webhook retention windows and a cleanup command. Message content is often customer PII, so review data residency, retention, and erasure obligations before enabling the defaults. You can disable message or webhook storage in the package config if you do not need history.
- What are alternatives to using Evolution API for WhatsApp in Laravel?
- The main alternative is Meta's official WhatsApp Cloud API or a managed provider built on it, which reduces the account-ban and terms-enforcement risk of the unofficial Evolution API bridge. Within Laravel and Filament, you could also integrate Evolution API directly or use another Filament WhatsApp package, but this one is tied to Filament v5 and Livewire v4. If you are on older Filament versions, you cannot use it without upgrading.