- How do I install filament-webhooks in a Laravel application?
- Install it with Composer using composer require jeffersongoncalves/filament-webhooks, then publish the package config and migrations with the vendor:publish command. Run the migrations and register the plugin in your target Filament panel provider. The package assumes Laravel 10/11+ with a Filament 3.x panel and a relational database. Confirm the exact version constraints in its composer.json before you pin it.
- Which Laravel and Filament versions does filament-webhooks support?
- The package targets Laravel 10/11+ and Filament 3.x panels, and it is designed as a panel plugin rather than a standalone package. The technical assessment notes that no composer.json was supplied, so verify the exact constraints against your installed Filament major version before adopting. If your panel runs a different Filament major, check for a matching release branch first.
- Can I use filament-webhooks as a headless webhook dispatcher?
- No. filament-webhooks extends the Filament admin panel layer and is meant for managing endpoints, event subscriptions, and delivery logs through a UI. It is not a headless webhook dispatcher and should not be evaluated as one. If you need programmatic delivery with no admin panel, scope a dedicated delivery package instead.
- How do I retry a failed webhook delivery from the Filament dashboard?
- Open the webhook delivery log in your Filament panel and use the retry action on the failed entry. The plugin lets you retry failed deliveries directly from the dashboard, so you can recover from transient endpoint errors without writing code. Inspect the stored payload and response first to confirm the failure was not a payload or signature problem.
- How are webhook requests signed and how do I set the signing secret?
- The plugin supports configurable signing secrets so receiving endpoints can verify outbound requests. Publish the package config and set the secret per endpoint there. Signing and secret-rotation logic is reported as unchanged between 3.0.0 and 3.1.0, but diff the release before sign-off if signing is security-critical for you.
- Where does filament-webhooks store delivery logs and payloads?
- Delivery logs, payloads, and responses are surfaced in the Filament UI and backed by the package migrations, so review the published migration to confirm table names and schema. Check that those tables do not collide with existing names in your application. If your retention or observability requirements are strict, confirm whether the log table is one you control and can export from before enabling it in production.
- Is filament-webhooks an alternative to spatie/laravel-webhook-server?
- Not a direct one. spatie/laravel-webhook-server handles outbound webhook delivery, signing, and retries in the domain layer, while filament-webhooks adds a Filament admin UI for managing endpoints and inspecting deliveries. The technical assessment explicitly suggests pairing spatie's package with a bespoke UI if you are not on Filament. If your admin panel is Filament-based, this plugin covers the management and inspection side.
- Is it safe to upgrade filament-webhooks from 3.0.0 to 3.1.0?
- Yes. 3.1.0 is an additive minor release: it adds 17 locales plus documentation and CI housekeeping, with no migrations, no deprecations, and no API or config surface changes. It is a drop-in upgrade. Pin to ^3.1, but review minor bumps on your normal cadence rather than auto-merging, given the single-maintainer risk profile.
- How do I translate or override the filament-webhooks admin UI language?
- Translations resolve through Laravel's standard lang pipeline using namespaced keys, so you can override any string by publishing the language files. The 3.1.0 release added ar, az, de, es, fa, fr, hi, it, ja, nl, pl, pt, ru, tr, uk, uz, and zh_CN. Note that zh_CN is region-qualified while pt and de are not, so apps using zh-Hans or pt_BR conventions must map locales at the application layer.
- How do I test webhook deliveries before enabling real subscribers?
- Install into a non-production environment, publish and review the config and migrations, and run the migrations against a staging replica. Register the plugin in the panel provider behind a feature flag, then fire test calls from the dashboard against a request-bin endpoint. Verify the signed payload and the logged response before pointing any real subscriber at it.