Weave Code
Laravel Crm Filament Laravel Package
venturedrake/laravel-crm-filament
Filament plugin that brings VentureDrake's Laravel CRM into your admin panel. Provides ready-to-use Filament resources, forms, and tables for managing CRM contacts, companies, deals, and activities, so you can run your CRM from an existing Filament dashboard without building custom CRUD screens.
Laravel CRM Filament adds a ready-to-use Filament admin panel to the VentureDrake Laravel CRM package. It transforms CRM records into polished, resource-driven screens so teams can manage customers, pipelines, and sales activity without building custom admin interfaces.
- Prebuilt Filament resources for leads, contacts, organizations, deals, and activities
- Kanban-style sales pipeline and deal tracking
- Inline tasks, notes, and activity logging
- Search, filters, and bulk actions across CRM records
- Configurable navigation and authorization through Filament
Frequently asked questions about Laravel Crm Filament
- What is venturedrake/laravel-crm-filament used for?
- It is a Filament admin panel layer for Venturedrake's Laravel CRM package. It gives you ready-made Filament resources, forms, tables, and widgets for managing contacts, companies, deals, activities, and related CRM records. It is not a standalone CRM; it depends on the core laravel-crm package and your application's Filament stack.
- How do I install laravel-crm-filament with Composer?
- Install it with Composer alongside the core laravel-crm package and your Filament setup. Your application should already be running a compatible core version, currently at least 2.4.2 and below 2.5 for panel v1.3.0. If you use Xero integration, also require dcblogdev/laravel-xero explicitly in the same deploy as core 2.4.5 or later.
- Which versions of laravel-crm does this Filament panel support?
- Panel v1.3.0 requires laravel-crm >=2.4.2 and <2.5. The 2.4.2 floor exists because required core APIs such as PdfContactDetails, PortalLink, Modules, PortalTeam::forDocument(), and SettingService::forTeam() landed in 2.4.1 through 2.4.2. Applications on older core versions need to upgrade the core package first.
- Why is laravel-crm-filament capped below core 2.5?
- The cap is deliberate because a core minor release requires the panel to be checked and released against it. The panel tracks later 2.4 patches without a panel release, but core 2.5 must wait for a compatible panel version. Plan that upgrade gate rather than discovering it during a core upgrade.
- Do I need to install dcblogdev/laravel-xero separately?
- Yes, Xero support is optional and now app-owned. Core moved dcblogdev/laravel-xero from require to suggest, so teams using Xero must add it explicitly, such as with core 2.4.5 or later. Without it, nothing errors and no job fails, but sync simply stops; the Integrations page shows an install notice. Existing tokens and crm_xero_ rows are retained, so installing the package restores the connection without re-authorisation.
- Does laravel-crm-filament work in headless mode?
- Yes, headless installs are handled when LARAVEL_CRM_USER_INTERFACE is false. The Connect and Disconnect actions hide because core does not register those routes in headless mode. This avoids a RouteNotFoundException that would otherwise cause a hard failure.
- How does database field encryption affect CRM search in Filament?
- When encrypt_db_fields is enabled, contact and organization pickers and title searches match decrypted names in PHP instead of using SQL LIKE against ciphertext. With encryption off, search remains in SQL. This fixes a significant correctness issue across lead, deal, quote, order, invoice, and purchase-order forms. Because matching and sorting move into PHP for affected pickers, test performance with realistic large contact and organization datasets.
- What happens when I clear a contact or organization on a quote, order, invoice, or purchase order?
- Clearing the contact or organization on a quote, order, invoice, or purchase order now unlinks it. Previously an empty select was treated as not submitted and kept the existing link. A field that is not submitted at all still keeps the link, but users and support staff should be briefed on the new unlink semantics.
- Can I use Guzzle 8 with laravel-crm-filament?
- The panel caps Guzzle at ^7, and the Xero package also caps Guzzle at ^7. Teams needing Guzzle 8 can use core without Xero, but likely cannot combine this panel with the Xero package until those constraints change. Validate the dependency resolution in Composer and CI before committing to the upgrade.
- Is laravel-crm-filament suitable for production CRM use?
- It is suitable for applications already on a compatible core version, and v1.3.0 includes meaningful operational and performance work such as server-side owner search, eager-loading to remove per-row queries, encryption-aware pickers, and relation-clearing fixes. You should still plan the core 2.5 upgrade gate, explicitly require the Xero package if needed, and performance-test encryption-on pickers with realistic data volumes.
Weaver
How can I help you explore Laravel packages today?