Weave Code
Google Chat Laravel Package
laravel-notification-channels/google-chat
Send Laravel notifications to Google Chat with this dedicated channel. Post messages to Google Chat spaces via incoming webhooks using a simple, familiar notification API—no custom HTTP code required.
Google Chat Notification Channel for Laravel (fka. Hangouts Chat)
Frequently asked questions about Google Chat
- How do I send a Laravel notification to Google Chat?
- Add the Google Chat channel to your notification's via() method, implement toGoogleChat() to return a message built with the package's fluent builder, and return the webhook URL from routeNotificationForGoogleChat() on the notifiable model. Laravel's notification system then handles delivery, queueing, and events. No custom HTTP code is needed in your app.
- How do I install the Google Chat notification channel?
- Run composer require laravel-notification-channels/google-chat. Then add the package's channel class to via() and define the builder and routing methods. The package is a thin adapter over Laravel notifications, so no service provider configuration is typically required.
- Is laravel-notification-channels/google-chat compatible with Laravel 11?
- v4.0.0 drops Laravel 9, 10, and 11, so it is not installable on Laravel 11 if the inferred constraints hold. Confirm the exact composer.json constraints before planning the work. Teams staying on Laravel 11 must pin 3.3.x or write a first-party channel.
- What are the PHP and Laravel requirements for v4.0.0?
- The v4.0.0 release notes indicate PHP 8.3+ and Laravel 12+ by dropping PHP 8.1/8.2 and Laravel 9/10/11 and adding PHP 8.4/8.5 and Laravel 13. The assessment flags these as inferred, so verify composer.json rather than assuming. The release is breaking because it moves the prerequisite, not because the integration API changes.
- How do I configure the Google Chat webhook URL for a notifiable model?
- Implement routeNotificationForGoogleChat() on the notifiable model and return the incoming-webhook URL for the target Google Chat space. The channel resolves the URL through that method, keeping credentials out of the notification class where possible. Treat the URL as a secret because it can post to the space.
- Can I send notifications to multiple Google Chat spaces?
- Per-notifiable routing means different models can return different webhook URLs from routeNotificationForGoogleChat(). Sending one notification to several spaces is not confirmed in the assessment; verify whether the builder accepts multiple URLs or send separate notifications. A small wrapper can fan out to multiple spaces if needed.
- Does the channel throw exceptions on Google Chat API errors?
- The provided assessment says non-2xx handling remains unverified, so do not assume exceptions are thrown for 4xx, 429, or 5xx responses. Check the channel source and tests for throw-versus-swallow behavior and whether NotificationFailed is dispatched. Add monitoring around queued notifications if silent failures are unacceptable.
- How do I test Google Chat notifications without hitting a real webhook?
- Use Notification::fake() to assert the notification was sent on the Google Chat channel without making HTTP calls. Whether the package itself exposes a fakeable HTTP helper is not confirmed; inspect its tests and source. If it uses Laravel's HTTP client, Http::fake() may also intercept the webhook request.
- Is this package actively maintained and safe for production?
- The v4.0.0 major is a positive maintenance signal: a maintainer cut a deliberate release tracking newer PHP and Laravel versions. However, adoption is low at roughly 59 stars and zero dependents, and 3.3.x support status is unclear. Production also carries unverified Google card-schema drift, Workspace admin webhook policies, and webhook URLs leaking into logs.
- What are the alternatives if I cannot upgrade to v4.0.0?
- If you are on Laravel 11 or PHP 8.2, v4.0.0 is not installable and the fallback is pinning 3.3.x, which may be out of support. If you are on Laravel 12+ and can absorb future majors, v4.0.0 is the cleaner choice once you verify the constraints. Writing a first-party channel is about a day of work and removes the version treadmill.
Weaver
How can I help you explore Laravel packages today?