Weave Code
Laravel Mailcoach Sendinblue Feedback Laravel Package
spatie/laravel-mailcoach-sendinblue-feedback
Addon for spatie/laravel-mailcoach that processes Sendinblue campaign feedback (bounces, complaints, etc.) so Mailcoach can automatically handle delivery events and keep subscriber status and stats in sync.
[READ ONLY] Handle feedback given by Sendinblue
Frequently asked questions about Laravel Mailcoach Sendinblue Feedback
- How do I integrate Sendinblue feedback into an existing Laravel Mailcoach setup?
- First, ensure you have `spatie/laravel-mailcoach` installed (v2.x+). Then install this package via Composer and publish its config using `php artisan vendor:publish`. Register the webhook route in `routes/web.php` and configure Sendinblue’s dashboard to send feedback to this endpoint. Run migrations to ensure Mailcoach’s database schema is up to date.
- What Laravel versions does this package support?
- This package is officially tested with Laravel 8, 9, and 10. If you’re using an older version (e.g., Laravel 7), check Mailcoach’s compatibility matrix, as dependencies may require adjustments. PHP 8.0+ is required.
- Can I use this package without spatie/laravel-mailcoach?
- No, this package is a Mailcoach add-on and requires `spatie/laravel-mailcoach` as a dependency. If you’re not already using Mailcoach, evaluate the effort to migrate your email campaigns to it first, as this package extends its core functionality.
- How does the package handle Sendinblue webhook failures or retries?
- The package relies on Sendinblue’s webhook delivery, which isn’t guaranteed. There’s no built-in retry logic or dead-letter queue, so consider implementing a fallback (e.g., polling Sendinblue’s API periodically) or using Laravel queues to process feedback asynchronously for resilience.
- Will this package work with high-volume email campaigns?
- For high-volume campaigns, the webhook endpoint could become a bottleneck. Optimize by using Laravel queues (e.g., Redis or database queues) to process feedback asynchronously. Batch processing or caching feedback before database writes may also help.
- How do I configure Sendinblue’s API credentials securely?
- Store your Sendinblue API key and webhook secret in Laravel’s `.env` file (e.g., `SENDINBLUE_API_KEY`). The package expects these to be available in the config published via `vendor:publish`. Never hardcode credentials in your application.
- What types of feedback does this package process from Sendinblue?
- The package processes standard Sendinblue campaign feedback, including opens, clicks, bounces, spam reports, and unsubscribes. These are stored in Mailcoach’s database for analytics, reporting, or further processing via Mailcoach’s events.
- Are there alternatives to this package for Sendinblue feedback in Laravel?
- If you’re not using Mailcoach, alternatives include manually polling Sendinblue’s API or using third-party services like Zapier to sync feedback to your Laravel app. However, this package is the most seamless solution if you’re already invested in Mailcoach.
- How can I test this package locally before deploying to production?
- Mock Sendinblue webhooks locally using tools like Laravel’s `Http::fake()` or Postman to simulate feedback payloads. Verify the package processes events correctly by checking Mailcoach’s database or listening to its `FeedbackProcessed` event. Test edge cases like duplicate feedback or malformed payloads.
- What happens if Sendinblue’s webhook payload is malformed or invalid?
- The package lacks explicit validation for malformed payloads, which could lead to errors. Handle this by adding middleware to your webhook route to validate payloads before processing or log invalid requests for debugging. Consider rate-limiting the endpoint to prevent abuse.
Weaver
How can I help you explore Laravel packages today?