Weave Code
Pushwoosh Laravel Package
laravel-notification-channels/pushwoosh
Send push notifications through Pushwoosh directly from your Laravel app using the native notification system. This channel lets you deliver messages to iOS and Android devices via Laravel notifications, keeping your code clean and consistent with other channels.
Pushwoosh notification channel for Laravel
Frequently asked questions about Pushwoosh
- How do I install the Pushwoosh notification channel in Laravel?
- Install it with Composer using composer require laravel-notification-channels/pushwoosh, then add your Pushwoosh credentials to the package configuration. Add the channel to the via() method of the notification classes that should send push messages. The package is MIT licensed and integrates with Laravel's existing notification system.
- Does this package support Laravel 13?
- Yes. Version 4.0.0 adds Laravel 13 support, which is the main change described in the release. Because v4.0.0 is a new major release, verify the exact Laravel and PHP constraints in composer.json and the CI matrix before upgrading. Teams on older Laravel versions should stay on 3.6.0 unless they have tested v4.0.0.
- What changed in v4.0.0 and is it a breaking change?
- The release is described as adding Laravel 13 support, and it is a semver-major jump from 3.6.0. That usually means older Laravel or PHP versions were dropped, but the release notes do not document API, config, payload, or namespace changes. Treat it as potentially breaking and review the diff and Composer constraints before upgrading.
- Can I upgrade from 3.6.0 to 4.0.0 safely?
- There is no documented upgrade path in the provided release information, so test the upgrade in a branch first. If you are not on Laravel 13, staying pinned to 3.6.0 is the lower-risk option unless you need the newer constraints. Check for config or payload changes and run your notification tests against a non-production Pushwoosh app.
- Where do I configure Pushwoosh credentials?
- You configure Pushwoosh credentials such as the application code and API token in the package configuration, then use those credentials when the channel sends a notification. The exact config file and key names depend on the installed version, so confirm them against the package source or README. Do not commit production credentials; use environment variables and Laravel's config caching.
- How do I send a push notification with Laravel notifications?
- Create a notification class, add the Pushwoosh channel to its via() method, and return a message payload from the appropriate method. Laravel's notification system then handles delivery through the channel while your application code stays consistent with other channels. Keep the channel behind an internal notification interface so a future provider swap is contained.
- Does it support targeted pushes, data payloads, badges, and deep links?
- The package overview describes basic push delivery to iOS and Android through Pushwoosh, but it does not document advanced feature coverage. Targeted pushes, data payloads, badges, deep links, delivery receipts, and multi-app configuration should be verified against the package code and your Pushwoosh account before adoption. If you need those capabilities, build a small spike that exercises each one.
- How does the package handle device tokens and invalid tokens?
- This is a notification delivery adapter, so device token registration, refresh, invalidation, and cleanup are generally handled by your mobile app and Pushwoosh rather than by the Laravel package. Confirm whether the package exposes any token management helpers in the version you install. Plan token lifecycle handling separately from notification sending.
- How should I test Pushwoosh notifications in Laravel?
- Use Laravel's Notification::fake() to assert that notifications are sent without hitting the Pushwoosh API, and add a separate integration test against a non-production Pushwoosh application for real delivery. Because the package has minimal community validation and zero dependents, test the exact version you pin. Also test queue retries, timeouts, and failed-job behavior.
- Is this package actively maintained and what is the fallback for production?
- The maintenance signal improved with v4.0.0 adding Laravel 13 support, but the release is new, thinly documented, and came through a single pull request from a first-time contributor. The package has a single-maintainer risk profile and little external production evidence. Pin the version, monitor releases, and keep a fallback such as a fork, a direct Pushwoosh API client, or an alternate push provider.
Weaver
How can I help you explore Laravel packages today?