notification-center.php config file controls every aspect of how notifications are delivered — which channels are available, how each notification type is routed and retried, and which third-party services are connected.
Publishing the config file
Run the install command to publish the config file to your application’sconfig/ directory:
notification-center.php into config/ and prompts you to star the repository on GitHub.
If you need to re-publish the config file after an upgrade, use
php artisan vendor:publish --tag=notification-center-config --force.Config sections
The published config file contains four top-level sections:messages
Maps channel identifier strings (e.g.
email, sms) to their notification class implementations.strategies
Defines delivery behavior for each of the five notification types: queue, channels, retries, timeouts, and time windows.
Holds the Twilio Content Template SID used when sending WhatsApp messages.
google_analytics
Your GA4 Measurement ID. When set, the
gtag.js script is included in rendered notifications.Full config example
The following is the complete default config file as published:config/notification-center.php
Environment variables
Two values are read from your.env file:
| Variable | Section | Description |
|---|---|---|
TWILIO_WHATSAPP_CONTENT_SID | whatsapp_content_sid | Twilio Content Template SID for WhatsApp messages. Required if the whatsapp channel is used in any strategy. |
GOOGLE_ANALYTICS_ID | google_analytics_id | GA4 Measurement ID (e.g. G-XXXXXXXXXX). When set, gtag.js is injected into rendered notification views. |
.env file as needed:
.env
Explore each section
Delivery strategies
Configure queues, channel ordering, retries, and timeouts for each notification type.
Deliverability
Fine-tune time windows, retry schedules, and channel escalation for reliable delivery.
Channel configuration
Register notification classes for each delivery channel and understand external service requirements.