Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Filament Export Scheduler

Filament Export Scheduler Laravel Package

visualbuilder/filament-export-scheduler

Schedule and automate exports directly from Filament. Create recurring export jobs, choose formats and destinations, and let Laravel handle delivery on your timeline—ideal for reports, backups, and recurring data handoffs without manual downloads.

View on GitHub
Deep Wiki
Context7

Schedule Filament exports

Frequently asked questions about Filament Export Scheduler
What is visualbuilder/filament-export-scheduler used for?
It is a Laravel package for scheduling and automating exports directly from Filament. You can create recurring export jobs, choose export formats and destinations, and let Laravel deliver them on your timeline. It is aimed at reports, backups, and recurring data handoffs without manual downloads.
How do I install visualbuilder/filament-export-scheduler?
Install it with Composer using composer require visualbuilder/filament-export-scheduler. Then follow the package README to register any required Filament panel integration and publish or configure package settings. Check the README for any additional setup steps before scheduling your first export.
Which Laravel versions are supported by filament-export-scheduler?
The provided context does not list Laravel version constraints. Check the package composer.json require section and the README before installing, because Composer will enforce the declared Laravel compatibility. If your app uses an older Laravel release, confirm support before adding it to production.
Which Filament versions does this export scheduler support?
The package is built for Filament, but the supplied context does not specify exact Filament major version support. Review the composer.json constraints and README installation notes to confirm compatibility with your Filament panel version. This is especially important before upgrading Filament.
How do I create a recurring export job in Filament?
Use the package’s Filament scheduling interface to define the export, recurrence, format, and destination. Laravel then handles running the export and delivery according to that schedule. Confirm the exact resource, action, or configuration names in the README for your installed version.
What export formats can I choose?
The package description says you can choose export formats, but it does not enumerate them. Check the package configuration and README for the supported format drivers and any extension points. If your required format is missing, verify whether it can be added through a custom exporter.
Where can scheduled exports be delivered?
The package supports choosing destinations for scheduled exports, but the supplied context does not list specific destination drivers. Review the configuration file and documentation for supported storage disks, notifications, or other delivery targets. Make sure any required credentials and Laravel filesystem disks are configured first.
How should I test scheduled exports in Laravel?
Write feature tests around the Filament scheduling action and assert that the expected export job is registered or dispatched. Use Laravel fakes such as Queue::fake or Bus::fake where appropriate, and freeze or travel in time to verify recurrence behavior. Check the README for any package-specific test helpers.
What should I check before using filament-export-scheduler in production?
Ensure Laravel’s scheduler cron entry is running and that queue workers are available for large exports. Verify destination credentials, disk permissions, retention policies, and failure monitoring so recurring exports do not silently fail. Also confirm that export sizes and schedules fit your infrastructure limits.
What are alternatives to filament-export-scheduler?
Alternatives include Filament Excel export plugins for manual downloads, custom Laravel scheduled commands or jobs for exports, and external BI or reporting tools. The right choice depends on whether you need scheduling inside Filament, recurring delivery, or broader reporting workflows. Review maintenance activity and compatibility before selecting an alternative.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console
pnscripts/filament-broadquill-lite
pnscripts/laravel-sentfold-lite
vleap/mx-sdk-laravel-internal
twidpay/utils
htetmyathlaing/scout-elasticsearch-driver
artisan-toolbox/front-awesome
ls/client-assistant
users-au/laravel-client
cgv/localized-resource
noith/settings
kda/laravel-package
kda/filament-dynamic-navigation
bypersoft/signbox
pairus/product-data
fayne/laravel-filament-cms-core
nodisrupt/laravel-agent
sierratecnologia/media-manager