Weave Code
Linked In Notifier Laravel Package
symfony/linked-in-notifier
Provides LinkedIn integration for Symfony Notifier, letting your app send notifications through LinkedIn. Configure it with a DSN like linkedin://ACCESS_TOKEN:USER_ID@default, where the token is your LinkedIn access token and the user ID identifies the recipient.
LinkedIn Notifier provides LinkedIn integration for the Symfony Notifier component, letting you deliver notifications to a LinkedIn user through a dedicated transport. Configure it with a DSN such as linkedin://ACCESS_TOKEN:USER_ID@default, where the access token authenticates your application and the user ID identifies the recipient.
- Native Symfony Notifier transport integration
- Authentication via access token and target user ID
- Simple DSN-based configuration through environment variables
- Compatible with standard
Notificationclasses and the NotifierTransportinterface - Maintained in the main Symfony monorepo
Frequently asked questions about Linked In Notifier
- Can I use Symfony’s LinkedIn Notifier in Laravel without major refactoring?
- No, this package is tightly coupled to Symfony’s Notifier component, requiring significant abstraction to work in Laravel. You’d need to create adapters for Symfony’s TransportInterface, HttpClient, and Messenger to align with Laravel’s NotificationChannel, Guzzle, and Queues. Expect 2–4 weeks of development for a basic integration.
- What Laravel versions support this package, given its PHP 8.4 requirement?
- The package requires PHP 8.4+, but Laravel’s LTS versions (e.g., 10.x, 11.x) typically support PHP 8.1–8.3. You’d need to either upgrade Laravel to a non-LTS version or fork the package to drop PHP 8.4 dependencies, which introduces maintenance risks.
- How do I securely store and rotate LinkedIn tokens in Laravel?
- The package expects tokens in a DSN (e.g., `linkedin://ACCESS_TOKEN:USER_ID@default`), but Laravel requires secure storage in `.env` or a secrets manager like Hashicorp Vault. You’ll need to implement token rotation logic separately, as the package doesn’t handle this.
- Does this package support LinkedIn webhooks for inbound events like profile views?
- No, this package is designed for outbound notifications only (e.g., sending messages). LinkedIn webhooks (e.g., handling profile views or job applications) require a separate solution like `spatie/laravel-webhooks` or custom OAuth integration with LinkedIn’s API.
- What’s the fallback if LinkedIn’s API changes and this package becomes unsupported?
- The package is stagnant (last release in 2026) with no active maintenance. Your fallback options include forking the repo, migrating to a Laravel-native solution like `spatie/linkedin`, or building a custom LinkedIn notification channel from scratch using Guzzle and Laravel’s Notification system.
- How do I handle rate limits or failed notifications in Laravel?
- Symfony’s HttpClient includes built-in retry logic, but Laravel’s Guzzle or Http facade requires custom middleware (e.g., `RetryMiddleware`) for rate limit handling. You’ll need to configure retries, timeouts, and exponential backoff manually in your Laravel application.
- Are there Laravel-specific alternatives to this package?
- Yes, consider `spatie/linkedin` for broader LinkedIn API access (including webhooks) or build a custom notification channel using Laravel’s `Notification` facade and Guzzle. These avoid Symfony’s dependency overhead and align better with Laravel’s ecosystem.
- How do I test LinkedIn notifications in a Laravel environment?
- Test by mocking the Symfony TransportInterface or using Laravel’s `NotificationFake` for unit tests. For integration tests, use a sandbox LinkedIn account with a test token and verify notifications via LinkedIn’s API logs or a mock HTTP client like `mockery`.
- Will this package work with Laravel’s queue system for async notifications?
- Indirectly, but you’ll need to adapt Symfony’s Messenger to Laravel’s `dispatch()` or `dispatchSync()`. The package’s async notifications would map to Laravel’s queue system, but you’ll lose Symfony’s built-in message handling features like retry queues or dead-letter queues.
- What’s the effort to integrate this into a production Laravel app?
- High. Beyond the 2–4 weeks for abstraction, account for token security, rate limiting, and potential PHP version conflicts. Production concerns like monitoring failed notifications, logging, and compliance with LinkedIn’s API terms will require additional custom logic.
Weaver
How can I help you explore Laravel packages today?