- How do I send webhooks from a Filament resource action (e.g., after saving a record)?
- Use the `webhook()` helper method inside your Filament resource’s `afterSave` or custom action. For example, `webhook()->to('https://api.example.com')->send(['data' => $record->toArray()])`. The package integrates seamlessly with Filament’s event system, so no extra setup is needed beyond defining the endpoint and payload.
- Does this package support async webhooks via Laravel queues?
- Yes, the package supports async webhooks out of the box. Configure the queue driver in the published config file (`config/filament-webhook-server.php`), and webhooks will automatically dispatch to your queue worker (e.g., `app:send-webhooks`). For production, monitor queue jobs using Laravel Horizon or similar tools to avoid bottlenecks.
- What Laravel and Filament versions are officially supported?
- The package requires **Filament v3+** and is tested with **Laravel 10/11**. For PHP, it supports **8.1+**. Always check the `composer.json` of your project and the package’s GitHub repo for the latest compatibility notes, as minor updates may introduce breaking changes.
- Can I validate or transform webhook payloads before sending?
- Absolutely. Use the `beforeSend` callback to modify payloads dynamically. For example, `webhook()->beforeSend(fn ($payload) => $payload['metadata'] = auth()->user()->id)->send()`. You can also leverage Laravel’s HTTP middleware to add signing, authentication, or payload validation logic.
- How do I test webhook endpoints in CI/CD or local development?
- Use Laravel’s `HttpTests` facade or Pest’s `actingAsWebhook` helper to simulate incoming webhooks. For outgoing webhooks, mock the `webhook()` method or use `Http::fake()` to assert payloads. The package includes built-in tools to inspect payloads via the Filament admin UI, making debugging straightforward.
- What happens if a webhook fails to deliver? Are there retries or fallbacks?
- Failed webhooks are retried by default (configurable in the package settings). For critical failures, implement a dead-letter queue or set up notifications via Laravel’s `FailedJob` events. The package logs all delivery attempts, and you can extend this with custom error handlers or alerts.
- Is there a way to monitor webhook deliveries in real-time from the Filament panel?
- Yes, the package includes a dedicated **Webhook Monitor** widget in the Filament admin UI. It displays delivery statuses, payloads, timestamps, and error logs. You can filter by endpoint, event type, or status to troubleshoot issues without leaving your Filament dashboard.
- Can I use this package for receiving *incoming* webhooks (e.g., from Stripe or GitHub)?
- The package is primarily designed for **sending** webhooks from Filament apps, but you can extend it to handle incoming webhooks by creating custom Filament resources or pages to process payloads. For robust incoming webhook handling, consider pairing it with packages like `spatie/webhook-client` or building a separate API endpoint.
- How do I secure webhook endpoints to prevent abuse or unauthorized access?
- Leverage Laravel’s built-in middleware to secure webhook endpoints. Add `throttle`, `signed`, or `auth:sanctum` middleware to routes. For outgoing webhooks, use the `webhook()->withHeaders(['Authorization' => 'Bearer ' . $token])` method to include authentication tokens. Always validate payloads and use HTTPS for all endpoints.
- Are there alternatives to this package for Filament webhooks? What makes this one unique?
- Alternatives include rolling your own HTTP client logic or using generic Laravel packages like `spatie/laravel-webhook-client` (for receiving) or `fruitcake/laravel-webhook-client`. However, this package is **Filament-specific**, offering a **visual admin UI** for monitoring, a **declarative syntax** for sending webhooks, and deep integration with Filament’s event system. It’s ideal if you want to avoid boilerplate while keeping everything in your Filament workflow.