Weave Code
Filament Mails Laravel Package
backstage/filament-mails
Filament Mails adds a searchable mail log to your Filament admin panel, letting you browse, preview and inspect emails sent by your Laravel app, review recipients, subjects and content, and debug delivery issues without leaving the dashboard.
Filament Mails is a plugin for Filament that lets you browse and inspect every email your Laravel application sends, directly from the admin panel. It captures outgoing mail through Laravel's mail events, stores it alongside its recipients and status, and presents it in a clean, searchable resource — so debugging delivery issues no longer means digging through logs.
- View sent emails with rendered HTML and plain-text previews
- Track recipients, subject lines, and send status at a glance
- Search and filter mail history from a dedicated Filament resource
- Works with your existing Laravel mailer configuration out of the box
- Lightweight setup via Composer, with publishable migrations and config
Frequently asked questions about Filament Mails
- Does backstage/filament-mails send and log emails, or only display them?
- It is a presentation-layer plugin: it renders and manages mail records inside a Filament panel rather than acting as a mail transport. Whether it ships its own logging mechanism (event listener or middleware plus a table) or expects a companion logger must be confirmed in a short spike. Either way, it does not change how your application actually sends mail.
- How do I install backstage/filament-mails in a Laravel app?
- Run composer require backstage/filament-mails, register the plugin in your target PanelProvider, publish the config with vendor:publish, and run php artisan migrate for the log table. Plan roughly half a day for a developer already fluent in Filament, or one to two days including queue verification and access-control hardening.
- Which Laravel, PHP, and Filament versions does backstage/filament-mails support?
- Check the Composer constraints in the package before committing, because Filament ships majors quickly and carries breaking changes across its plugin API. Treat the package's Filament constraint as a constraint on your own upgrade path and re-test at every Filament major. It is a single-maintainer project, so verify its Laravel and PHP support against your target versions during the spike.
- Can I preview and send test emails for a mailable directly from Filament?
- Yes. You can browse the mail classes in your application, render their templates with sample data, and send test emails without leaving the admin panel. That shortens the template iteration and debugging loop considerably, since you never switch to a separate mail viewer or inbox.
- Does backstage/filament-mails work with queued mail and Mail::fake() in tests?
- Verify this during your spike: does capture happen synchronously with the send call, and does it behave correctly under queue workers and inside database transactions? Confirm that a capture failure can never propagate into the send path. If the package ships no test suite or CI matrix, write your own smoke test asserting that mail still sends successfully with logging enabled.
- Is it safe to store mail bodies, PII, and password-reset links in the admin database?
- Logged mail routinely contains PII, password-reset links, invitation tokens, and sometimes customer data or credentials in the body. Persisting that widens the compliance scope of your admin database and brings GDPR erasure, retention limits, access logging, and encryption at rest into play. Treat it as a policy decision rather than a package setting, and confirm whether bodies and attachments are stored at all and whether selective capture or redaction is configurable.
- How do I stop the mail log table from growing too large?
- One row per outbound mail with a body column grows linearly with notification volume, and without pruning it can become a top-three table within a year on a mid-traffic app. Check whether the package ships a pruning command or a documented schedule, and add your own if it does not. Also confirm the index strategy behind the list view before you reach millions of rows.
- Who can see logged emails in the Filament panel?
- Because the plugin lives inside the panel, it inherits your Filament auth, tenancy, and policy model, which is architecturally clean but also the main security dependency. Confirm how records are scoped (global, per-tenant, per-user) and whether Filament policies or gates are enforced or visibility is simply implied by panel access. If panel access is broad, mail content becomes broadly readable, so consider a dedicated permission for the mail resource.
- What are the alternatives to backstage/filament-mails for inspecting sent mail?
- If your admin is built on Nova, Backpack, or a decoupled SPA, this package is a non-starter. For local development, Mailpit or MailHog capture outgoing mail without writing it to your application database. Inside Filament, the realistic alternatives are another mail-log plugin or a small event listener plus your own Filament resource.
- Is backstage/filament-mails actively maintained and safe to use in production?
- The project has around 163 stars and no dependents on record, which signals low production evidence rather than poor quality, and it is maintained by a single author. MIT licensing is the practical mitigation, since fork-and-maintain is viable at this codebase size. Run a timeboxed spike rather than designing by analogy, and budget a compatibility check at each Filament upgrade.
Weaver
How can I help you explore Laravel packages today?