Weave Code
Filament Form Builder Laravel Package
tomatophp/filament-form-builder
Filament Form Builder for Laravel lets you create dynamic forms in Filament with a drag-and-drop builder, reusable fields, and stored submissions. Manage forms and entries from your admin panel without writing code.
Manage your forms using database and drop/drag component to build the form with Livewire component support for FilamentPHP
Frequently asked questions about Filament Form Builder
- How do I install tomatophp/filament-form-builder in a Laravel app?
- Install it with Composer using composer require tomatophp/filament-form-builder, then let Laravel's package auto-discovery register the service provider. The provider publishes the package assets, so run the vendor:publish command for the tags listed in the README if you need to customise anything. Check the README for any required migration or panel-registration step before opening the resource in your Filament panel.
- Which Laravel and FilamentPHP versions does Filament Form Builder support?
- The package targets FilamentPHP and standard Laravel package conventions, but the supported Laravel and PHP ranges are not documented in the release notes, so read the require block in composer.json before installing. The 5.x line matters most on Laravel 11 and 12, where view:cache is folded into php artisan optimize and provider-level path defects surface as deploy failures. Confirm the Filament major version constraint too, since Filament 3 and 4 APIs are not interchangeable.
- How does the drag-and-drop form builder work inside Filament?
- You manage forms from a Filament resource in your admin panel: create a form, drag components onto the canvas to define fields and layout, and save the schema to the database. The stored schema is rendered back as a live form, so you can change fields later without shipping new code. Submissions are then captured as entries you can browse from the same panel.
- Where are form submissions stored and can I export them?
- Entries are persisted in your application database rather than in a file or external service, which is why the package is described as database-driven. You can read them through the package's Filament resource or query the underlying models directly if you need a custom report. Export is not documented in the release notes, so if CSV or spreadsheet output is a requirement, plan on building it on top of the stored entries.
- Can I add Livewire components to a dynamic form?
- Yes. Livewire component support is an explicit feature of the package, so you can drop interactive components into a built form alongside standard fields. That makes it practical to reuse existing Livewire UI inside generated forms instead of recreating every widget as a plain input. Check the documented component list before relying on deeply stateful components, since they run inside the builder's own rendering pipeline.
- Do I need to publish config or migrations before using the package?
- The service provider publishes package assets, and forms plus submissions need database tables, so run the publish and migrate steps the README documents. If migrations are not auto-loaded by the provider, publish them with the package tag and run php artisan migrate. Verify which paths the provider still registers or publishes in 5.0.1, because the patch release removed a registration pointing at a directory the package does not ship.
- Is Filament Form Builder safe to use in production?
- The upgrade risk is low: 5.0.1 is a patch release confined to service provider registration, with no public API or config schema changes described. The real production concern is pipeline hygiene, because a provider referencing unshipped paths only fails when view:cache runs, which is exactly what a deploy does. Add php artisan optimize to your CI smoke test against a clean Laravel skeleton so this class of defect is caught before release.
- Why does php artisan optimize or view:cache fail with this package, and does 5.0.1 fix it?
- Version 5.0.0 registered and published a resources/views directory that the distributed artifact does not contain, so walking registered view paths during view:cache could abort the command and, on Laravel 11+, the whole optimize step. Release 5.0.1 removes that registration, so upgrading to ^5.0.1 is the fix. If you pinned 5.0.0 or added a workaround such as skipping view:cache or hand-creating the vendor view directory, remove it in the same change so your pipeline exercises the real code path.
- How do I test forms built with Filament Form Builder?
- Treat the built form as a Livewire component and use Livewire's testing helpers plus Filament's resource test utilities to assert that fields render and submissions persist. Use RefreshDatabase so entry tables are migrated per test run, and seed a form schema in a factory or fixture instead of clicking through the builder. If you extended the package, also cover the case where a stored schema references a field type that no longer exists.
- What are good alternatives to Filament Form Builder for dynamic Laravel forms?
- The closest alternative is composing Filament's native form components, repeaters, and Builder fields yourself, which gives full control but no stored schema or entry management out of the box. Other form-builder packages exist in the Laravel ecosystem, so compare them on field types, Livewire support, submission storage, and recent release activity. Whichever you pick, verify it passes a clean php artisan optimize run before committing it to a deploy pipeline.
Weaver
How can I help you explore Laravel packages today?