Search by

nvl / mail-notification-bridge

nicolas_vls

Laravel consumer bridge for the Mail Notifications delivery API, Mailables, notifications, scoped history and signed callbacks.

v7.0.0 2026-11-03 15:10 UTC

This package is not auto-updated.

Last update: 2026-11-05 02:43:34 UTC


README

A Laravel consumer of the Mail Notifications HTTP API. Send host-rendered HTML/CSS or Mailables, use Laravel notifications, query client-scoped history and receive signed delivery callbacks.

Choose the package

Requirement Package Responsibilities in this application
Call a separately hosted mail service nvl/mail-notification-bridge Business authorization, content, recipient routing, API credentials, optional callback receipts
Run delivery inside this Laravel application nvl/mail-notifications Provider credentials, queues, attachments through nvl/media, delivery/event storage, sync and callback outbox

Choose the bridge for remote consumption. Choose the delivery engine for embedded delivery or building the service itself. Installing both is not required. The bridge depends on nvl/core, not the engine, Media, a broker or a template editor. It does not install a dashboard or provider webhook receiver. Laravel owns your views and templates; the service accepts prepared content.

Requires PHP 8.4+ and Laravel 13. Install from your configured NVL Composer repository:

composer require nvl/mail-notification-bridge:^7.0
php artisan vendor:publish --tag=nvl-mail-notification-bridge-config

Guides

Agent guidance

php artisan vendor:publish --tag=nvl-mail-notification-bridge-skills

This publishes the self-contained nvl-mail-notification-bridge skill into the host's .agents/skills. Read its SKILL.md before integrating. On upgrades, review local modifications before republishing with --force. Human guides generate the corresponding portable skill references; consumers do not need the suite checkout.

Verification

Package tests execute the documented bilingual Mailable and user/order/arbitrary-recipient recipes against a fake HTTP boundary. Separate clean-Laravel QA verifies Composer discovery, live local SMTP, attachments, client isolation and signed callbacks. These are local checks, not a claim that your production provider, queue, HTTPS endpoint or recovery setup has been verified.