- How do I install Filament Notifier in a Laravel FilamentPHP app?
- Install it with composer require usamamuneerchaudhary/filament-notifier, run the notifier:install command, then register the plugin in your Filament panel provider. The installer publishes migrations and a config file, so review the schema before running migrations against an existing database. Confirm your Laravel and Filament versions satisfy the package's composer constraints first, since v2 does not publish a supported-version matrix.
- Which Laravel and FilamentPHP versions does Filament Notifier v2 support?
- The v2.0 release notes do not state a supported Laravel or Filament version matrix; they link to CHANGELOG.md with no inline detail. Check the composer.json constraints on the tagged v2 release and test against your exact Laravel and Filament versions in staging. Filament APIs change between majors, so do not assume backward compatibility.
- Does Filament Notifier work in a plain Laravel app without Filament?
- It is a FilamentPHP panel plugin, not a framework-agnostic notification library. Without Filament you still inherit its migrations, models, routes, REST API and service layer, but you lose the dashboards and resources that justify the package. If your app has no Filament admin panel, native Laravel notifications are usually the lower-coupling choice.
- Which notification channels does Filament Notifier support?
- Email, SMS, Slack, Discord and push are listed as supported channels, with custom drivers available. Each channel driver is relatively thin, so verify provider SDK versions and config keys after the v2 major bump rather than assuming unchanged signatures. Test every channel you actually rely on end to end.
- How do scheduled and event-driven notifications work in Filament Notifier?
- The package supports scheduled notifications and event-based triggers, but the v2 release notes do not document the scheduler trigger model or the assumed queue connection. Confirm whether dispatch relies on Laravel's scheduler via schedule:run or on a queue worker, and set the connection explicitly in config. Load-test before trusting it for time-critical sends.
- How does Filament Notifier email open and click tracking work with queued mail?
- Email tracking records opens through a tracking pixel and clicks through link rewriting, exposed in the analytics dashboard. Whether that survives queued mail, multiple mailers, and non-HTML or plain-text parts is not documented and should be verified in your own mail configuration. Test with the exact mailer and queue setup you run in production.
- How does the Filament Notifier user preferences REST API handle authentication and multi-tenancy?
- User preferences are managed through the package's own REST API, which is part of the coupling surface you take on. The docs do not describe the authentication guard or tenant isolation model, so review the published routes and middleware before exposing them. For multi-tenant apps, add explicit scoping and authorization rather than relying on defaults.
- Is Filament Notifier production-ready and actively maintained?
- Treat it as the current head of a moving line rather than a stabilized release. Adoption signals are weak, with roughly 36 stars, zero dependents and a single maintainer, so there is little crowd to shake out upgrade bugs before you hit them. Run a proof of concept against your Filament version and real channels, and read the source for the areas you depend on.
- How do I upgrade Filament Notifier from v1 to v2 and what are the breaking changes?
- There is no inline upgrade guide; the v2 release notes point to CHANGELOG.md without a breaking-change list or deprecation runway. Diff the source between the v1 and v2 tags for model, migration, route, config and driver signature changes. Plan a staging migration with a database backup, since the package owns schema and routes.
- How do I add a custom channel driver to Filament Notifier, and what are the alternatives?
- The package supports custom channel drivers alongside the built-in email, SMS, Slack, Discord and push channels. Implementing a driver means conforming to the package's channel contract, which is versioned by the v2 major, so pin the version you build against. If you only need email and database notifications, Laravel's native Notification system plus Filament is a lighter alternative with less schema ownership.