Weave Code
Filament Intercom Laravel Package
apility/filament-intercom
Adds the Intercom messenger to Filament admin panels, letting teams chat with users and handle support without leaving the dashboard. Simple setup, lightweight integration for Laravel and Filament apps.
At a glance
Frequently asked questions about Filament Intercom
- What does apility/filament-intercom do in a Filament admin panel?
- It is a lightweight Filament integration that injects the Intercom messenger into Laravel admin panels, letting support and success teams chat with users from the dashboard. It is aimed at Filament apps rather than public-facing sites. Confirm the exact UI hooks and configuration options against the package source, because the release note is minimal.
- How do I install apility/filament-intercom in a Laravel app?
- Install it with Composer using composer require apility/filament-intercom, pinning the major version that matches your Filament release. For Filament 4, pin v2.0.0 or a compatible 2.x constraint. Then register the plugin in your panel provider and publish any config or assets the package ships. Verify the provider class and registration snippet in the package README or source first.
- Does apility/filament-intercom support Filament 4?
- Yes, v2.0.0 is explicitly released with Filament 4 support, so it is the version to evaluate for Filament 4 panels. The release note does not include a full compatibility matrix, so validate the Composer constraints against your Laravel, PHP, Livewire, and Filament versions. Run composer why-not before merging to catch transitive conflicts.
- Can I use apility/filament-intercom with Filament 3?
- v2.0.0 appears intended for Filament 4 and should not be assumed to work on Filament 3. If your application remains on Filament 3, stay on the v1.x line or defer adoption until you schedule the Filament upgrade. Check the package's composer.json and tags to confirm which major version maps to Filament 3.
- Which Laravel and PHP versions does apility/filament-intercom require?
- The v2.0.0 release note does not publish a compatibility matrix for Laravel or PHP, so do not infer support from the Filament 4 label alone. Read the require and require-dev sections of the package composer.json and compare them with your application constraints. Run composer why-not apility/filament-intercom to see any blocked versions.
- How do I register the Intercom messenger plugin in a Filament panel provider?
- Register it as a Filament panel plugin in the panel provider where you enable admin features, following Filament's plugin registration pattern. The release note does not document the exact plugin class or method chain, so confirm the snippet from the package source or README. After registration, clear config and view caches and smoke-test the panel.
- How do I configure the Intercom app ID or workspace for the messenger?
- Configuration is typically supplied through a published config file or environment variables, but the release note does not list the exact keys. Publish the package config if available and set the Intercom workspace or app ID there rather than hard-coding it in views. Keep separate credentials per environment and confirm the messenger loads only for authenticated staff.
- Are there breaking changes between v1.x and v2.0.0 of apility/filament-intercom?
- No migration guide or breaking-change list is included in the v2.0.0 note, even though the major version implies possible changes to namespaces, config keys, registration APIs, or assets. Treat the upgrade as controlled: pin the exact version, upgrade in a branch, republish config and assets, and re-register the plugin. Review the diff between v1.x and v2.0.0 tags before adopting.
- Does apility/filament-intercom work with multi-tenant Filament panels and authorization?
- Filament tenancy and authorization behavior for the messenger is not documented in the release note, so test it against your panel's tenant scoping and policy setup. Ensure only authorized staff can open Intercom conversations and that user identity is verified server-side to prevent impersonation. Run smoke tests across tenant contexts, not just the default panel.
- How should I test apility/filament-intercom before deploying to production?
- Run a time-boxed pilot in a non-production branch: resolve dependencies with Composer, register the plugin, publish config and assets, clear caches, and test login, navigation, resources, policies, and tenancy. Confirm there are no conflicts with other Filament plugins and check the browser console for messenger or CSP errors. Deploy to a canary environment first and keep a rollback path to the prior package and Filament versions.
Weaver
How can I help you explore Laravel packages today?