Weave Code
Nova Webhooks Laravel Package
opscale-co/nova-webhooks
Nova Webhooks is a Laravel Nova package for managing outgoing webhooks directly from your admin panel. Configure endpoints, select triggering events, and keep an eye on deliveries, making it easier to connect Nova-managed apps with external services.
At a glance
Frequently asked questions about Nova Webhooks
- How do I install opscale-co/nova-webhooks in a Laravel Nova application?
- Install it with Composer using composer require opscale-co/nova-webhooks, then publish the package config and migrations, run php artisan migrate, and register the Nova tool in your Nova service provider. You will also need to provision a queue worker, since outbound deliveries should not run on the sync queue. Check the package's composer.json constraints before installing to confirm it matches your Laravel and Nova versions.
- Does nova-webhooks work without Laravel Nova?
- No. Nova Webhooks is built as a Laravel Nova tool, so the subscription management UI depends on an existing Nova installation and its license. If you do not already run Nova, adding it purely to get webhooks means taking on a Nova license cost plus a queue architecture decision. In that case a code-driven package such as spatie/laravel-webhook-server is usually a better fit.
- Which Laravel and Nova versions does nova-webhooks support?
- The package is intended for modern Laravel applications running Nova 4 or 5, but the exact PHP, Laravel, and Nova version floors should be read from the package's composer.json rather than assumed. The v1.2.0 release adopts opscale-co/actions v4, a major version bump of a transitive dependency, so it is worth confirming whether that raised any of the package's own version constraints. Verify the constraints against your application before upgrading.
- Do I need a queue worker to use Nova Webhooks?
- Yes, practically speaking. Outbound HTTP deliveries should be dispatched to a durable queue such as Redis with Horizon or SQS, with workers running continuously. Running deliveries on the sync queue turns third-party endpoint latency into user-facing latency and defeats the purpose of the package. Also confirm your application has reliable network egress to customer-controlled endpoints, including any non-standard ports or TLS configurations.
- How do I configure webhook endpoints and triggering events in the Nova admin panel?
- After registering the tool, you create webhook subscriptions in Nova by specifying the destination URL, the events that should trigger a delivery, and any related settings the package exposes. The package handles subscriptions and delivery logging through its own migrations, so it should not intrude on your domain models. For anything your application dispatches, you will typically need to fire the corresponding events from your own code.
- Does Nova Webhooks guarantee delivery, and does it support retries and idempotency?
- Expect at-least-once delivery semantics, which is the norm for queued outbound webhooks, meaning receivers can see duplicates and must be idempotent. Whether the package exposes delivery IDs, deduplication headers, and configurable retry or backoff behaviour should be confirmed in its documentation before relying on it. The v1.2.0 bump to opscale-co/actions v4 touches the dispatch layer, so re-test retry and backoff behaviour after upgrading.
- How should I verify webhook signatures on my receiving endpoint?
- The package is expected to sign outbound payloads so receivers can verify authenticity, typically with an HMAC over the request body plus a timestamp header to limit replay. Your receiving service should compute the same digest using the shared secret, compare it in constant time, and reject stale timestamps. Confirm the exact signature scheme, header names, and secret rotation story in the package docs, since these are consumer-side concerns the package cannot enforce for you.
- Do webhook delivery logs grow unbounded in the database?
- Nova Webhooks persists delivery records so you can inspect successes and failures from the admin panel, which means the table grows with every delivery attempt. Whether the package ships retention controls, pruning commands, or a configurable log level is not documented in the supplied material, so review the migrations and config before going to production. For high-volume installations, plan a pruning strategy or scheduled cleanup to keep the table manageable.
- Is nova-webhooks a replacement for spatie/laravel-webhook-server?
- They solve overlapping problems differently. spatie/laravel-webhook-server is configured in code and is a good fit when webhook destinations are developer-managed, while Nova Webhooks adds an admin UI for creating endpoints and choosing triggering events. If you already have an in-house dispatcher, run a dual-delivery period before cutover so you can compare behaviour. Avoid running two dispatchers against the same endpoints without a plan, or receivers will see duplicate deliveries.
- Is upgrading to nova-webhooks v1.2.0 safe, and what changed with opscale-co/actions v4?
- The only substantive change in v1.2.0 is adopting opscale-co/actions v4, a major version bump of a transitive dependency shipped inside a minor release. No changes to this package's own public API are documented, but the changelog does not confirm that retry semantics, job payload shape, middleware, or version floors are unchanged. Before upgrading from v1.1.0, read the dependency's release notes and run your queue and delivery tests in staging, keeping in mind that both packages come from the same vendor organisation.
Weaver
How can I help you explore Laravel packages today?