Weave Code
Facebook Laravel Package
laravel-notification-channels/facebook
Laravel Notification Channels Facebook adds a Facebook channel to Laravel’s native notification system, letting you deliver notifications through Facebook from your app using the familiar Laravel notification API with simple setup and integration.
Facebook Notifications Channel for Laravel
Frequently asked questions about Facebook
- What is laravel-notification-channels/facebook used for?
- It adds a Facebook channel to Laravel's native notification system, letting a notifiable receive notifications through Facebook by adding 'facebook' to via() and defining toFacebook(). It is a thin bridge that sends outbound Graph API calls using a configured page or app access token. It does not include an SDK, persistence layer, or queue worker.
- How do I install and configure laravel-notification-channels/facebook?
- Install it with Composer, add a services.facebook config block with the required access token, and add the channel to your notification. The package follows the laravel-notification-channels convention and uses a FacebookMessage value object for message content. You still need a Meta app, a Facebook Page, and a token with the correct scopes.
- Does this package support Laravel 10 or Laravel 11?
- Version 0.3.0 declares Laravel 9 support, which was the first compatibility update since 0.2.1. Laravel 10 and Laravel 11 are not validated in the provided release context. If your application is on Laravel 10 or 11, assume compatibility is not guaranteed without testing.
- Is the Facebook notification channel still supported by Facebook's Graph API?
- The package targets app-to-user notifications via the /{user-id}/notifications Graph edge, which Meta deprecated and withdrew for most app types. Messenger-based delivery through the Send API still exists, but it uses a different endpoint, the pages_messaging permission, and separate policy rules. Version 0.3.0 made no endpoint, API-version, or permission changes, so you must verify current API viability with a live send.
- How do I send a Facebook notification in Laravel with this package?
- Add 'facebook' to the via() array on your notification and implement a toFacebook() method that returns a FacebookMessage. The channel class reads that message and sends the Graph API request using your configured access token. No service provider overrides or schema changes are needed.
- What Facebook app review or permissions are needed for this package?
- You need a Meta app, a Facebook Page, and an access token with the scopes required for the endpoint you are using. Anything beyond a small number of test users typically requires Business Verification and App Review. For Messenger delivery, the permission set includes pages_messaging, which is separate from the deprecated app-to-user notification flow.
- Can I queue Facebook notifications sent through this channel?
- The package is additive to Laravel's notification pipeline and does not override queue behavior or event dispatch. If your notification implements ShouldQueue, Laravel queues it as usual. The package itself has no queue worker or persistence layer.
- How do I handle Facebook access token expiry or revoked permissions?
- The package stores no state beyond the configured page or app access token, and there is no built-in health signal. Token expiry, scope revocation, or a Page admin password change can silently break delivery. You need external monitoring, token refresh procedures, and alerting around failed sends.
- What are alternatives to laravel-notification-channels/facebook?
- If you need Facebook Messenger delivery, use the Messenger Send API directly or a package that explicitly targets that endpoint and pages_messaging. If you need app-to-user notifications, confirm whether Meta still allows your app type before choosing any package. Other laravel-notification-channels packages follow the same convention for Slack, Telegram, or Twilio but do not replace Facebook-specific policy work.
- Is laravel-notification-channels/facebook actively maintained and safe for production?
- Version 0.3.0 is the first release since 0.2.1 in February 2022 and added Laravel 9 support plus message-builder conveniences. It brought new contributors, but the dependent count is still approximately zero and there is no evidence of renewed Graph API commitment. Treat it as a small, low-footprint bridge and validate API viability, Laravel compatibility, and credential monitoring before production use.
Weaver
How can I help you explore Laravel packages today?