Weave Code
Facebook Poster Laravel Package
laravel-notification-channels/facebook-poster
Send Laravel notifications to Facebook Pages with this dedicated notification channel. Quickly publish posts, links, and media to a page via the Facebook Graph API, integrating Facebook publishing directly into your app's existing notification workflow.
Use notification to create posts on Facebook
Frequently asked questions about Facebook Poster
- What Laravel and PHP versions does laravel-notification-channels/facebook-poster support?
- Release 6.2.0 requires Laravel 11 or 12 and PHP 8.2 or newer; Laravel 10 and PHP 8.1 support was dropped in that release. Check the composer.json require block for the exact matrix before installing. If your app is still pinned to Laravel 10, stay on an earlier major or schedule the framework upgrade first, because adopting this is a sequencing decision rather than a plain composer require.
- How do I install facebook-poster in a Laravel app?
- Install it with composer require laravel-notification-channels/facebook-poster, then add your Page access token under the services config (for example services.facebook) in config/services.php. There are no migrations, schema changes, or UI involved. Laravel's package auto-discovery registers the service provider for you.
- How do I get a Facebook Page access token for this channel?
- Create a Meta/Facebook App, connect your Page, and generate a long-lived Page access token with the pages_manage_posts permission via the Graph API Explorer or your app's login flow. Store the token in your .env and secret storage, never in the repository, and make sure it can be rotated without a deploy. Anything beyond basic posting typically requires Meta app review, which usually belongs to whoever owns the Page rather than engineering.
- How do I send a Facebook post from a Laravel notification?
- Add FacebookPosterChannel::class to your notification's via() method, then implement toFacebookPage() returning a FacebookPosterMessage built with text, link, or image content. Route the notification to a notifiable that exposes the Page routing method the channel expects. The channel translates that message into a single Graph API call against the one configured Page, keeping Facebook publishing out of your domain code.
- Can I post images and links with this channel, or is it text only?
- FacebookPosterMessage supports text, links, and images, so basic posting, link shares, and media are covered. Image posting goes through the Graph API photo upload rather than the feed endpoint, so verify each format against the builder API at the version you install. If your content plan is heavily media-driven, test all formats on a staging Page before committing.
- Should Facebook notifications be queued, and what happens on Graph API rate limits?
- Implement ShouldQueue on the notification so publishing runs as a background job instead of inside the request cycle. On rate-limit or permission errors the Graph API returns an error and the channel throws, which lets Laravel's queue retries and backoff engage and your alerting fire. Do not swallow those exceptions, because silent non-publishing is a product failure, not merely an engineering one.
- How does the package handle Facebook Graph API versioning and deprecations?
- The package targets a specific Graph API version, and Meta versions and deprecates endpoints on its own cadence, so a Graph API change can break posting with no change on your side. Watch the repository's release notes when Meta announces a version sunset and treat Graph API updates as a scheduled maintenance item. Pinning the package version and keeping a fallback publish path limits the blast radius.
- What are the risks of depending on a small, single-maintainer notification channel?
- This package has a small user base, no commercial support path, and realistic single-maintainer risk. It is a reasonable convenience integration for outbound Page posts but should never become a revenue-critical publishing pipeline without a fallback. Keep a manual post or direct Graph API call path so you can still publish if the package is abandoned mid-quarter.
- Can I post to multiple Facebook Pages with this channel?
- The channel is scoped to a single configured Page per services entry, which is the documented default. Posting to several Pages means separate config entries and notifications, or a custom channel built on the same Graph API calls. Treat it as plumbing for one Page rather than stretching it into a multi-tenant publishing platform.
- What alternatives exist to laravel-notification-channels/facebook-poster?
- You can call the Facebook Graph API directly with Laravel's HTTP client, which removes the dependency but means you own the message-to-payload mapping and error handling. General social publishing services and SaaS schedulers cover multi-network posting if you need more than a single Page. Use this package when notification-driven Facebook Page posting is genuinely all you need.
Weaver
How can I help you explore Laravel packages today?