Discord Webhook Bundle Laravel Package

Product Decisions This Supports

• Ops and incident notification plumbing. Routing deploy events, error spikes, signup milestones, or moderation flags into Discord channels is a recurring small ask. This package turns it into a config entry instead of a backlog ticket — Discord is often where small teams already live, so the value is removing friction, not adding capability.
• Build vs. adopt. The real deliverable here isn't the HTTP call (that's ~20 lines of Guzzle); it's config-driven webhook endpoints plus DI wiring, so URLs live in env/config rather than hardcoded, and services receive a notifier rather than constructing one. That's roughly half a day of plumbing saved.
• Multi-destination routing. If the bundle supports named webhooks in config, you get per-channel fan-out (#alerts vs. #product-activity) without a new service per channel — useful for separating signal from noise in team channels.
• Community/product ops notifications. Consistent with LabyMod's origins in gaming community tooling: creator-program alerts, support triage pings, moderation flags.
• Not for anything user-facing or interactive. Webhooks are one-way. Slash commands, buttons, threads, message editing, and OAuth are bot/API territory. A dropped message must never be a product defect, which constrains where this belongs.

One correction worth flagging up front: despite the "Laravel/PHP" framing, this is a Symfony bundle, not a Laravel package. If the roadmap decision is "how do we notify Discord from our Laravel app," this package does not serve that decision.

When to Consider This Package

Adopt if:

• Your stack is Symfony and you want labymod/discord-webhook wired through the container with config-driven endpoints.
• The need is strictly outbound, one-way messages (content/embeds) to a handful of channels.
• You accept it as a thin, low-blast-radius dependency you could replace in an afternoon.
• It still resolves against your Symfony version. This is the gating check: last release was January 2022, so constraints likely target Symfony 4/5. Symfony 6.x/7.x compatibility is unverified and is probably the deciding factor before anything else matters.

Look elsewhere or build in-house if:

• You're on Laravel — use a Laravel-native notification channel or a small Http::post() wrapper.
• You need retries, queueing, rate-limit handling, or delivery guarantees. Nothing here suggests those are solved, and silent failure is the wrong failure mode for an alerting path.
• You need slash commands, interactive components, or message editing — that's a bot, not a webhook.
• Dependency hygiene is a stated concern. 2 stars, 0 dependents, and no release in ~3 years is a maintenance signal. It isn't a disqualifier for a wrapper this small, but it means you own it now.
• You'd be the only consumer — the fork cost equals the build cost, so just build it.

How to Pitch It (Stakeholders)

Executives: This is a small convenience wrapper, not a platform bet. It's MIT-licensed and free, and it removes a few hours of internal plumbing so engineers can ship Discord notifications in a day instead of a sprint. The risk is maintenance, not money: the project is effectively unmaintained (last release 2022, near-zero adoption), so treat it as code we adopt, own, and are prepared to fork. Recommend a time-boxed spike, not a standard.

Engineering: It's a Symfony bundle around labymod/discord-webhook — config-driven webhook endpoints injected as a service. Verify Symfony version compatibility first; the 2022 release likely predates 6.x/7.x and may not resolve at all. If it does resolve, wrap it behind our own notifier interface so it's swappable and testable, and keep it off critical alerting paths unless we add retries and queueing ourselves. Otherwise the equivalent is a small HTTP client plus config — same outcome, zero dependency risk.