Filament Discord Driver Laravel Package

Product Decisions This Supports

• Build vs. buy for admin-facing notification plumbing. This package covers the unglamorous middle layer between "our app raises an event" and "a human sees it in Discord": a settings surface for webhook URLs, env-var fallbacks, and per-event routing. That is typically 1–2 sprints of internal work plus ongoing maintenance, so the make-or-buy call is really "do we want a maintainer-owned settings UI, or do we want to own a config screen forever?"
• Operator-configurable alerting without redeploys. Because webhook destinations live in the settings hub rather than hardcoded config, support/ops can retarget or add channels for a new team, region, or incident rotation without a release. This directly reduces the lead time on "we need these errors to go somewhere else" requests.
• Where alerting lives on the roadmap. The v5 line targets Filament v5 with Laravel 12/13, while v4 remains the home for Filament v4 shops. That split is a real planning input: if the platform upgrade to Filament v5 / Laravel 12+ is already on the roadmap, this dependency should be sequenced with it rather than treated as an unrelated chore.
• Reliability confidence for an "invisible" feature. The v5.0.0 fix for settings-hub webhook values never being applied means every deployment relying on the settings UI was silently falling back to env config. For a PM, that is a reminder that notification integrations need a "did it actually deliver?" acceptance check in QA, not just a "settings screen renders" check.
• Fit assessment for the wider Tomatophp/Filament ecosystem. If the product already ships Filament admin panels with sibling Tomatophp packages (alerts, settings hub), marginal cost of adoption is low and consistency is high. If not, this is a single-purpose dependency pulling in a companion package line that must be tracked for major-version alignment.

When to Consider This Package

Adopt when:

• You run a Filament admin panel and want alert configuration surfaced to operators rather than buried in .env.
• You already use (or plan to use) tomatophp/filament-alerts — v5.0.0 hard-requires ^5.0, so the two are a matched pair and should be upgraded together.
• Your target stack is Filament v5 with Laravel 12 or 13; you are on a currently supported framework path with an explicit CI matrix covering it.
• You need Discord as an operational notification channel — internal ops, error triage, or team-facing business event alerts — and want env-var defaults with settings-hub overrides rather than a bespoke integration.
• You value upstream regression coverage: v5.0.0 ships regression tests specifically for the settings-vs-env precedence bug, which lowers the probability of silently undelivered alerts recurring.

Look elsewhere when:

• You are on Filament v4 or Laravel 11 — stay on the v4 branch and plan the cut-over deliberately; do not mix a Filament major upgrade with unrelated feature work.
• Discord is not your channel of interest (Slack, Teams, PagerDuty, email) — this is Discord-specific, not a generic notification router.
• You need guaranteed delivery, retries, escalation policies, or on-call semantics — a webhook to Discord is best-effort. For anything paging a human at 3am, that belongs in a dedicated incident tool.
• You need strong delivery observability (audit trail of what was sent, when, and whether it succeeded). This package configures destinations; it is not a delivery log. Instrument that yourself if alerting is business-critical.
• You cannot absorb major-version churn — v5 is a breaking release tied to Filament v5, and the dependency on filament-alerts ^5.0 means upgrade timing is coupled across packages.

How to Pitch It (Stakeholders)

For executives: This is a small, low-cost piece of infrastructure that lets operators point our internal Discord alerts at the right channels without engineering involvement or a release. The new v5.0.0 release brings us onto the current framework line (Filament v5, Laravel 12/13), fixes a real defect where webhook settings configured in the admin UI were being silently ignored, and adds automated regression tests plus a CI matrix so that class of defect is caught rather than discovered. Decision needed: schedule this alongside the Filament v5 upgrade, not as a standalone change.

For engineering: v5.0.0 is a breaking release — it requires Filament v5 on Laravel 12/13 and tomatophp/filament-alerts ^5.0; the Filament v4 line continues on the v4 branch. Two behavioural fixes land with it: settings-hub webhook values now actually take effect (previously the configured webhook was never applied), and DISCORD_* env config is now preserved when settings-hub values are empty — i.e. the precedence is env-as-default, settings-as-override, which is what we'd expect. Regression tests and a Laravel 12/13 CI matrix come with it. Treat the upgrade as coupled to the Filament v5 / Laravel 12+ migration, and add a manual "alert actually arrives in Discord" verification to the upgrade checklist, since the previous behaviour failed silently.

Ask: approve the upgrade as part of the Filament v5 platform workstream; no separate business case required.