Filament Webhook Server Laravel Package

Product Decisions This Supports

• Build vs. Buy: Accelerates development by eliminating the need to build a custom webhook management system for Filament admin panels. Reduces backend effort by leveraging an existing, battle-tested solution.
• Feature Expansion: Enables real-time event-driven workflows (e.g., notifications, integrations, or third-party syncs) without requiring additional API endpoints or manual scripting.
• Roadmap Priorities:
  • Internal Tools: Justify investment in Filament-based admin panels by adding webhook capabilities to reduce dependency on external services (e.g., Zapier).
  • Customer-Facing Products: For SaaS platforms, allows customers to configure webhooks for their own data (e.g., order updates, user actions) via a self-service UI.
  • Compliance/Logging: Supports audit trails by retaining webhook logs (configurable via keepLogs()), addressing regulatory requirements.
• Use Cases:
  • Event-Driven Architecture: Trigger actions in external systems (e.g., Slack alerts, CRM updates) when Filament models change.
  • Multi-Tenant Systems: Isolate webhook configurations per tenant using Filament’s clustering or custom logic.
  • Custom Payloads: Extend functionality for complex data structures via the Webhookable interface (e.g., nested relationships, computed fields).

When to Consider This Package

• Adopt When:

  • Your team uses Filament for admin panels and needs a low-code solution for webhook management.
  • You require model-level granularity (e.g., webhooks for User, Order, but not Role).
  • Your use case aligns with CRUD events (create/update/delete) or simple custom payloads.
  • You need auditability (webhook history logs) without building a custom system.
  • Your stack is Laravel 10+ with Filament v3+ (confirmed compatibility).

• Look Elsewhere If:

  • You need advanced webhook routing (e.g., conditional logic based on payload content).
  • Your payloads require real-time processing (e.g., WebSockets) or high-throughput handling (consider spatie/laravel-webhook-server directly).
  • You’re using non-Filament admin panels (e.g., Nova, Backpack).
  • Your events are non-model-based (e.g., system cron jobs, external API triggers).
  • You need enterprise-grade features (e.g., rate limiting, IP whitelisting, or OAuth validation)—this package delegates to spatie/laravel-webhook-server under the hood.

How to Pitch It (Stakeholders)

For Executives:

*"This package lets us ship webhook integrations 10x faster by embedding a self-service dashboard directly into our Filament admin panel. For example:

• Customer Success: Let customers configure their own webhooks for order updates without engineering help.
• Internal Tools: Automate cross-system syncs (e.g., Salesforce, HubSpot) with zero backend code.
• Cost Savings: Avoids subscriptions to tools like Zapier for simple workflows. It’s low-risk (MIT license, MIT-licensed dependency) and scalable—we can start with basic CRUD events and extend later."*

For Engineering:

*"This wraps spatie/laravel-webhook-server with a Filament UI, giving us:

• Zero setup for basic use cases: Just add WebhookPlugin::make() to your panel config.
• Flexibility: Exclude/include models, customize payloads via Webhookable, or override pages entirely.
• Maintenance: Actively developed (releases every 2–3 months), with contributions from the community. Tradeoff: Delegates to Spatie’s library for core logic, so we inherit its security/performance characteristics. Ideal for MVP or internal tools where speed > customization."*

For Developers:

*"Key perks:

1. Automagic Model Integration: All Eloquent models are auto-detected for webhook events (create/update/delete).
2. Payload Control: Use toWebhookPayload() for custom data shapes or stick with defaults.
3. Filament Native: No context-switching—configure webhooks from the same UI where you manage models.
4. Extensible: Override the entire plugin or just tweak config (e.g., polling interval, SSL verification). Gotchas:

• Webhook delivery reliability depends on Spatie’s library (e.g., retries, timeouts).
• No built-in validation: You’ll need to add middleware if you need to validate incoming webhooks."*