Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Laravel Mandrillhooks Laravel Package

eventhomes/laravel-mandrillhooks

Laravel package for handling Mandrill webhooks. Receive and process Mandrill events such as bounces, opens, clicks, and spam reports in your Laravel app, with ready-to-use routes, controllers, and event handling.

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • Feature delivery: Use it to ship a Mandrill webhook endpoint faster for bounce, rejection, spam, unsubscribe, and related transactional-email events. This supports suppression-list hygiene, delivery-failure alerts, and customer-support workflows.
  • Roadmap: Treat it as an enabler for email deliverability observability, not a strategic platform. It is most useful for an MVP or a narrowly scoped Laravel application already sending through Mandrill.
  • Build vs. buy: Lean toward adopt/fork, not deep integration. The package is a thin controller layer; if requirements grow beyond basic event capture, building a small internal handler may be cheaper than depending on a low-adoption package last released in 2020.
  • Use cases: Laravel + Mandrill transactional email, bounce/reject handling, basic event logging, support-ticket enrichment, and early warning for deliverability problems.
  • Product risk: Low stars, stale release cadence, and narrow scope mean it should not sit on a critical path without an internal owner, compatibility check, and fallback plan.

When to Consider This Package

  • Consider it when: You are on Laravel, already use Mandrill, need a simple webhook receiver quickly, and can pin/fork the dependency. The MIT license makes a fork or internal copy practical.
  • Validate first: Compatibility with your Laravel/PHP version, webhook authentication/signature handling, idempotency, retry behavior, queueing, and test coverage. Assume the package is a starting point, not a complete production event pipeline.
  • Look elsewhere when: You need multi-provider email event handling, high-volume event processing, strong compliance/audit requirements, active vendor maintenance, or a non-Laravel stack. Also look elsewhere if your team cannot own a fork or if Mandrill webhook security and reliability requirements exceed a thin base controller.

How to Pitch It (Stakeholders)

  • Executives: This is a low-cost accelerator for email deliverability feedback. It can reduce time-to-market for bounce/rejection handling and lower support risk, but it is not strategic IP. Approve a small pilot only with an owner and a fork/maintenance plan.
  • Engineering: It provides a simple Mandrill webhook base controller for Laravel. Use it as a reference or pinned dependency, then add authentication, idempotency, queued processing, logging, and tests. Budget a short spike to confirm compatibility with the current framework and PHP versions.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
shitoudev/permissionmanager
johannesclimacus/laravel-tui
hocvt/seotools
vitalybaev/sypexgeo
amphibee/themosis-ignition
gito-me/fast-excel
frankyso/laravel-ipaymu
geolize-studio/laravel-chile
boomerangui/chat
jinas/dhivatar
store-doc/laravel-storage-driver
plus-it/laravel-translation-manager
diephp/perhaps
diephp/telegraph
osmaviation/spreadsheet
microsoft/fluentui-system-icons
mmccook/php-json-canonicalization-scheme
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console