Filament Discord Laravel Package

Product Decisions This Supports

• Ship vs. defer Discord alerting in the admin panel. This package turns existing Filament notifications into Discord channel posts through a webhook, so the feature is measured in days of integration work rather than a platform build. That makes it a low-cost "yes" for a pilot and an equally cheap "no" if the team doesn't live in Discord.
• Roadmap sequencing against the Filament v5 migration. v5.0.0 targets Filament v5 / Laravel 12–13; Filament v3 panels stay on a separate v3 branch. Adoption is therefore coupled to the panel upgrade, not a standalone backlog item. If the Filament v5 migration is already planned, this rides along nearly free. If it isn't, adopting now means either pinning a legacy branch or deferring — both are explicit roadmap decisions rather than accidents.
• Build vs. buy (borrow). MIT-licensed, a narrow surface, and small enough to review in an afternoon. The v5 test suite — which fakes Discord HTTP calls — materially lowers review and fork cost, strengthening "borrow" over a hand-rolled webhook. That holds only while the need is genuinely "post a message to a channel."
• Use-case validation for internal tooling. Strongest fit: low-volume operational signal — new records, approvals, form submissions, failed jobs, error reports to a #errors channel. Weakest fit: paging, on-call escalation, or anything with a delivery guarantee. Deciding which of those two the team actually needs is the real product question; it determines whether this package is the answer or a detour.
• Rollout and environment policy. v5 skips sending when no webhook is configured, and the error reporter never throws. That makes it safe to enable across local/staging/prod without creating a new failure mode — but silence becomes ambiguous. A deliberate decision about where webhooks are configured, plus a post-deploy smoke check, belongs in the rollout plan rather than being discovered later.
• Risk acceptance on a low-adoption dependency. Two stars, zero dependents, no support contract. Acceptable for a tactical utility if we pin the version, keep a thin internal wrapper around the vendor call, and retain the fork option. Unacceptable as core infrastructure. Record that decision now so it isn't rediscovered during the next upgrade.

When to Consider This Package

Consider it when:

• The panel is on Filament v5 with Laravel 12/13 — or you accept tracking the v3 branch for older panels — and you want Discord notifications with minimal integration work.
• Discord is already where the team operates. The value is proximity to the conversation, not the transport.
• Alerts are operational, not mission-critical: awareness and convenience, not delivery guarantees.
• The need is narrow and stable: send a Filament notification to a Discord webhook. No routing rules, no escalation matrix, no templating engine.
• Safe-by-default behavior in non-production is a plus — silent skip on missing webhook, non-throwing error reporter — so enabling it doesn't introduce a new failure mode during rollout.
• You can review and vendor/fork a small package; the v5 test suite makes that materially cheaper than it used to be.
• Volume is modest and basic message delivery is sufficient.

Look elsewhere when:

• You need multi-channel notifications (Slack, Teams, email, SMS, PagerDuty) or a unified notification platform. Evaluate a notification service, not a webhook plugin.
• Alerts are mission-critical and require SLAs, retries, audit trails, or on-call escalation. "Never throws" protects the request lifecycle; it does not deliver the page.
• You need enterprise support, a security review, or compliance guarantees. Two stars and zero dependents is the whole signal.
• You're not on Filament, or you need workflow integration deeper than a webhook notification.
• You need rich interactive Discord messages (buttons, components, threaded replies) or high throughput — Discord's per-webhook limits (~30 req/min, ~2000 characters per message) bind quickly.
• You're on Filament v3 and unwilling to carry a separate maintenance branch. Factor that into upgrade planning before adopting, not after.

How to Pitch It (Stakeholders)

For executives: This is a small, MIT-licensed utility that lets our Filament admin panel post notifications to Discord channels via webhook — alerts, activity, and error reports where the team already talks. It is a days-not-quarters integration, it can't take down a request (failures are swallowed by design), and it can't accidentally spam production during rollout because it no-ops when no webhook is configured. The trade-off is equally clear: two stars, no dependents, no support contract — so we treat it as a tactical convenience, pin the version, and keep a thin internal wrapper that lets us replace or fork it without touching product code. Approve it as internal tooling, not as infrastructure.

For engineering: Keep the coupling explicit. The v5 line is Filament v5 / Laravel 12–13 only; Filament v3 lives on a v3 branch, so land this alongside the panel upgrade rather than as a surprise bump. Read tests/ first — it is the authoritative behavior spec. Webhook URLs are bearer credentials: .env only, rotate on any leak. Route severity across separate webhooks (#activity, #alerts, #errors), queue everything triggered from a request, and log the response status inside our wrapper, because the send path fails silently. Set a dummy webhook in the test environment, otherwise "it sent" assertions pass vacuously.