Weave Code
Filament Fcm Driver Laravel Package
tomatophp/filament-fcm-driver
Firebase Cloud Messaging driver for Filament that lets you send push notifications to mobile and web clients from your Laravel admin panel. Configure FCM credentials, target devices, and manage notification delivery directly within Filament.
Firebase Cloud Messaging driver for Filament Alerts Sender
Frequently asked questions about Filament Fcm Driver
- What does tomatophp/filament-fcm-driver actually do?
- It is a thin adapter that binds the filament-alerts package to the laravel-notification-channels/fcm driver so you can send push notifications to mobile and web clients from your Filament panel. It also adds an admin surface for uploading the Firebase service account key and generates the web service worker. It is an add-on for panels already standardised on filament-alerts rather than a new notification subsystem, so it assumes filament-alerts is installed and configured.
- How do I install filament-fcm-driver in a Laravel app?
- Install it with Composer alongside filament-alerts, then run php artisan filament-fcm-driver:install. After that you upload your Firebase service account key through the Filament panel and confirm the generated service worker is served over HTTPS at the correct scope. You also need a queue worker provisioned for the filament-alerts queue, otherwise notifications will silently stall.
- Which Laravel and Filament versions does this package support?
- Version 5.0.0 targets Filament v5 with Laravel 12, and the package also references Laravel 13 support, which should be treated as forward-looking and validated against your pinned framework. Because v5.0.0 requires filament-alerts ^5.0, the Filament v5 line is effectively mandatory for this release. Older Filament v4 projects should stay on the v4 branch of the package.
- Can I use this package on a Filament v4 panel?
- Not with the 5.x release. Version 5.0.0 is coupled to filament-alerts ^5.0 and the Filament v5 line, so it cannot be adopted in isolation. On Filament v4 you should pin the v4 branch and plan the Filament v5 and filament-alerts upgrade as a separate piece of work.
- Where is the Firebase service account key stored and is it secure?
- The package stores the service account key JSON on the private local disk, which is the right direction compared with public storage. Old keys keep working after an upgrade, so no forced re-upload is required, which is good migration ergonomics. However, the evaluation found no documented support for key rotation, per-environment separation, encryption at rest, or secret manager and KMS backends, so treat the credential as a long-lived private key and plan your own rotation policy.
- Is it safe to send a public notification to every user with this driver?
- Be careful. The package documents that public notifications go to every user holding an FCM token, which implies an unbounded recipient set with no documented batching or rate limiting. That is a thundering-herd risk against your FCM project quotas and queue depth on large user bases. If you have a big audience, chunk the fan-out yourself, add rate limiting, and handle FCM quota backoff in your own job layer.
- Which queue do FCM notifications use and can I change it?
- Single-user notifications are queued on the filament-alerts queue, and the evaluation flags the queue-name coupling as a risk because workers must be provisioned for that exact queue or sends stall silently. Confirm your supervisor or Horizon configuration listens on the correct queue in every environment before going live. Whether the queue name is configurable and what retry and backoff policy applies on failure are not documented, so verify against the source for your version.
- Do I need to generate a service worker for web push notifications?
- Yes, web push requires a Firebase service worker, and the package generates it with an artisan command. The evaluation notes it is unclear whether regeneration is needed per release, whether the file is fingerprinted for cache busting, or how it behaves behind a CDN. Serve it over HTTPS at the scope your app expects and check your cache headers after each deploy.
- Does the package prune invalid or unregistered FCM tokens automatically?
- Automatic pruning of stale tokens on UNREGISTERED or INVALID_ARGUMENT responses is not documented in the package evaluation. Without pruning, invalid tokens accumulate and inflate your public fan-out cost and failure rate. Plan to capture FCM error responses in your own notification or listener layer and delete tokens that Firebase reports as no longer registered.
- Is filament-fcm-driver actively maintained and production ready?
- It is effectively a single-maintainer package with community pull requests, and it now supports both a v4 and a v5 branch, which doubles the maintenance surface area and means you should not expect a fast fix for v5 edge cases. Two documented regression-fix markers, for push notification actions and the lcobucci/jwt constraint, show the v5 port has had rough edges. There is also no clear committed support window published for the v4 branch, so evaluate it as a convenience adapter and keep an eye on releases before committing to it in production.
Weaver
How can I help you explore Laravel packages today?