Weave Code
Filament Laravel Package
gowa-php/filament
Filament integration for the gowa-php WhatsApp gateway client. Adds admin resources and UI components to manage WhatsApp sessions, devices, and messaging directly from your Laravel Filament panel.
Official Filament v5 / v4 / v3 plugin for integrating GOWA (go-whatsapp-web-multidevice) WhatsApp instances into Laravel Filament applications.
Frequently asked questions about Filament
- What does the gowa-php/filament package actually do?
- It is the official Filament plugin for the gowa-php WhatsApp gateway client, which talks to a GOWA (go-whatsapp-web-multidevice) server. The plugin registers Filament resources and UI components so you can manage WhatsApp sessions, devices, and messaging from your existing Laravel Filament panel instead of building screens yourself. It is a UI layer on top of the gowa-php client, so all API communication still goes through the GOWA gateway.
- Which Laravel and Filament versions are supported?
- The plugin supports Filament v5, v4, and v3, so it covers both current and legacy panels. Because Filament versions have different APIs, the package ships version-specific integration code. Check the composer.json constraints in the repository to confirm the exact Laravel and PHP versions required by your Filament major version before upgrading.
- How do I install gowa-php/filament with Composer?
- Install it with composer require gowa-php/filament, making sure the version constraint matches your Filament major version. The package is a Filament plugin rather than a full application, so it expects the base gowa-php client and a reachable GOWA server to already be available. After installing, register the plugin in your panel provider so its resources appear in the admin navigation.
- Do I need a running GOWA server to use this plugin?
- Yes. The plugin is only a Filament front end; the actual WhatsApp connection, QR pairing, and message delivery are handled by a go-whatsapp-web-multidevice server. You need at least one reachable GOWA instance plus its API credentials configured in your Laravel environment. Without a working gateway, the resources will load but the device and session actions will fail.
- How do I register the plugin in my Filament panel provider?
- Add the plugin to the panel configuration inside your PanelProvider, typically by chaining the plugin's make() method onto the panel's plugin() call. Once registered, the WhatsApp resources and components are automatically discovered and added to the navigation. If you use multiple panels, register it only in the panel where administrators should see WhatsApp management screens.
- Can I manage multiple WhatsApp devices and sessions from the panel?
- Yes, multi-device support is the point of the underlying GOWA server, and the plugin exposes that through its Filament resources. You can list connected devices, start new sessions, and trigger QR-based pairing flows from the panel UI. Each device is managed independently, so one panel installation can serve several WhatsApp numbers.
- How do I send WhatsApp messages from a Filament resource or action?
- The plugin provides UI components and actions for composing and sending messages to a selected device or chat. Under the hood these call the gowa-php client, so anything you can do through the client can be wired into a Filament action or page. For automated or bulk sending, prefer queued jobs that use the client directly rather than triggering requests from the browser.
- How do I control who can access the WhatsApp admin resources?
- Because the screens are regular Filament resources, you control access with Filament's usual authorization mechanisms such as policies, canViewAny checks, and panel access rules. Restrict the plugin's resources to an admin or operations role, since anyone with access can read conversations and send messages as your WhatsApp numbers. You can also hide the resources from navigation for users who should not see them.
- How do I configure the GOWA connection and test it safely before going live?
- Connection settings such as the GOWA base URL, username, and password belong in your environment file and config, not in committed code. Point a staging panel at a separate GOWA instance and a test WhatsApp number first, so pairing and sending can be verified without touching production chats. In production, keep credentials out of version control and avoid exposing the gateway directly to the public internet.
- Should I use this plugin or build a custom integration with the gowa-php client?
- Use the plugin if you already run Filament and want ready-made resources for sessions, devices, and messaging without writing screens yourself. Build a custom integration if you need a very specific workflow, non-Filament UI, or a different WhatsApp provider entirely. Since the plugin sits on the gowa-php client, you can also start with the client alone and add the plugin later when you want admin screens.
Weaver
How can I help you explore Laravel packages today?