Nova Webhooks Laravel Package

Product Decisions This Supports

• Admin-facing extensibility: Lets non-engineering teams configure outbound webhooks from Nova admin panels—useful when customers or internal ops need event-driven integrations (Slack alerts, CRM sync, provisioning hooks) without a custom build.
• Build vs. buy: Reduces a "wire up custom webhook CRUD, retry logic, and delivery logs" ticket to a package install. Estimate savings in the 1–3 sprint range for a small-to-mid feature.
• Roadmap sequencing: Relevant whenever an integration/automation epic is on the roadmap but not differentiated—enables a "webhooks available now" milestone without committing product engineering to a first-party platform.
• Nova 5 upgrade planning: v2.0.0 is a dependency-alignment release, so this is now a gating item in any Nova 5 migration. Treat it as a migration dependency, not a feature decision.
• Use cases: customer-facing event notifications, third-party SaaS sync, internal ops tooling, low-code automation bridges.

When to Consider This Package

Consider adoption when:

• You already run Laravel Nova as your admin layer and want webhook management exposed there rather than building UI yourself.
• Your need is outbound event notification, not inbound webhook consumption, complex transformation, or guaranteed exactly-once delivery.
• Your Nova version is 5.x—v2.0.0 is the only compatible line. Older Nova installs must stay on v1.1.3.
• Requirements are modest: a curated event list, admin-managed endpoints, and basic delivery visibility are sufficient.
• You want a small, single-maintainer utility over a heavier platform (Svix, Hookdeck, custom queue-based pipeline).

Look elsewhere when:

• You need delivery guarantees, replay, signature verification, or observability at production scale—plan for a dedicated webhook service.
• You are not on Nova, or are planning to move off it; the package's value is entirely Nova-bound.
• Vendor risk tolerance is low: this is a single-maintainer repo, and a major version bump arriving solely as a dependency sync signals reactive rather than proactive maintenance.
• You need inbound webhook handling or bidirectional flows.

How to Pitch It (Stakeholders)

To executives: This is a small, low-cost add-on that gives our admin console the ability to push events to customer and partner systems. It converts a custom development ask into a configuration feature and is a credible "integrations available" line item without platform investment. Cost is a package install plus a Nova 5 upgrade dependency; risk is that it is maintained by a single author, so we should treat it as a convenience layer, not infrastructure we build a contract on.

To engineering: v2.0.0 is a breaking release in the narrow sense—it bumps dependencies for Nova 5 compatibility and drops the prior Nova line. There are no new features. If we are on Nova 5, pin ^2.0; if we are on Nova 4 or earlier, stay on 1.1.3 and expect no further patches. The major-version jump is dependency-driven, not API-driven, so re-verification effort is low but non-zero. Flag in the upgrade checklist: confirm the Nova 5 migration lands before we take this, and confirm we accept single-maintainer risk with a fallback plan (a thin internal replacement is not large).