Weave Code
Filament Automation Bridge Laravel Package
ashrafic/filament-automation-bridge
A Laravel/Filament bridge for connecting automation workflows to your admin panel. Trigger webhooks, manage integrations, and automate tasks directly from Filament resources with a simple, configurable setup.
Turn any Eloquent model event into an automation trigger for Zapier, Make, or n8n — without writing code.
Frequently asked questions about Filament Automation Bridge
- How do I install ashrafic/filament-automation-bridge in a Laravel Filament app?
- Install it with Composer as a Filament plugin, then run the package's install artisan command and publish the Spatie-style config and migration stubs. The package registers a service provider, routes under the automation-bridge prefix, and a WebhookBridge facade. After publishing, configure your queue worker and open the Filament resource or template page to create destinations and triggers.
- Which Laravel and Filament versions does filament-automation-bridge support?
- It is built for Laravel apps using Filament v4 or v5, with PHP constraints defined in its composer.json. Recent commits specifically repair Filament v5 deprecations, so v5 support is actively maintained. Check the composer constraints before installing because the context does not pin an exact Laravel version.
- How do I trigger a webhook when an Eloquent model is created or updated?
- Create an automation trigger using the ModelEvent trigger type and select the Eloquent model event you want to listen for. You can pair it with conditions evaluated by ConditionEvaluator and a PayloadFormatter that shapes the JSON sent to Zapier, Make, or n8n. Delivery is handled by DeliveryService through queue jobs, so model events become outbound automation calls without custom code.
- Which automation platforms and auth modes are supported?
- The bridge targets outbound webhook workflows for Zapier, Make, and n8n, and any endpoint that accepts the configured HTTP payload. Destination auth modes include Basic, Header, Bearer, and API key. Destinations are configured through the package config and Filament UI rather than hard-coded in your models.
- How are webhook secrets stored, and does it prevent SSRF?
- Destination auth supports Basic, Header, Bearer, and API key modes, and SecurityService includes HMAC signing and SSRF prevention. The available release context does not confirm whether secrets live in config, env, or an encrypted DB column, whether they are redacted in delivery logs, or the exact SSRF allow/deny semantics for private IPs, redirects, and DNS rebinding. Verify those details in SecurityService and the UI before production, especially if users can supply webhook URLs.
- What queue and retry setup does DeliveryService require?
- DeliveryService is queue-backed and assumes a working Laravel queue connection, such as database or Redis, with a running worker. Historical sync and scheduled triggers also depend on the queue. The context does not specify the assumed connection or retry/backoff policy, so review the package config; if the worker is down, deliveries wait until processing resumes.
- Can I extend trigger types, conditions, and payload formatters?
- Yes. TriggerManager uses an extensible trigger-type contract with built-in Schedule, Manual, Event, ModelEvent, StatusChanged, and DateCondition types. ConditionEvaluator has pluggable operators, and PayloadFormatter and ConditionOperator contracts let you shape payloads and conditions. That contract-driven core is intended to be extended without forking the package.
- What breaks when migrating from filament-webhook-bridge to filament-automation-bridge?
- The rename may change the Composer package name, service provider namespace, config key, route prefix, facade alias, and table names. The context does not mention a compatibility shim or migration guide, so treat the new package as a greenfield install and audit any old config, published migrations, and internal notes. Pin versions until the namespace and config key stabilize.
- Does filament-automation-bridge support multi-tenant or per-team triggers and delivery logs?
- The provided evaluation does not confirm multi-tenant or per-team scoping; it explicitly asks whether the package is single-tenant only. Before using it in a multi-tenant app, inspect the migrations, Filament resource queries, and authorization policies for tenant scoping. If scoping is absent, add it at the application layer or wait for documented support.
- How do I test webhook automations and debug failed deliveries?
- The package includes an install command plus cache, prune, sync, and test artisan commands, and the Filament side provides a delivery log page and health widget. Use the test command with a controlled endpoint, then inspect delivery logs and queue failures for payload and auth issues. For production, keep the queue worker monitored and prune logs with the provided command.
Weaver
How can I help you explore Laravel packages today?