Weave Code
Webex Laravel Package
laravel-notification-channels/webex
A Laravel notification channel for Cisco Webex Teams (formerly Spark). Send notification messages to Webex rooms from your Laravel app using the familiar Notification API, with a simple channel class and configurable Webex bot/access token.
A Laravel Notification Channel for Webex.
Frequently asked questions about Webex
- How do I install laravel-notification-channels/webex?
- Install it with Composer using composer require laravel-notification-channels/webex. Laravel's package auto-discovery registers the service provider, so no manual provider entry is normally needed. After that, publish or add the Webex configuration block and supply your bot token or webhook URL. The whole setup is a matter of minutes rather than a project.
- Which Laravel versions does this Webex notification channel support?
- Version 2.0.0 was released specifically to add Laravel 11 support, and its release notes mention nothing else. That framing usually means the illuminate/* constraint in composer.json was narrowed, so applications on Laravel 9 or 10 are likely pinned to v1.0.1. Check the actual composer.json diff before planning an upgrade, because a major version bump in this package family is often a dependency-constraint artifact rather than an API change.
- How do I configure the Webex bot token for this package?
- Add a services.webex entry to config/services.php containing your credentials, and keep the token itself in your .env file rather than in source control. The channel supports bot/access token authentication as well as incoming webhook delivery, depending on which mode your Webex space uses. Creating the bot and adding it to the target room is a Cisco-side administrative step that must be done before any message will deliver.
- How do I send a Webex notification from a Laravel app?
- Add a toWebex() method to your notification class and include 'Webex' in the via() array, then call $user->notify(new YourNotification()). The notifiable model should implement routeNotificationForWebex() to return the target room or webhook details. This keeps Webex delivery alongside your existing mail, Slack, or SMS channels with no change to your domain logic.
- Can I send a Webex notification on-demand without a notifiable model?
- Yes, use Laravel's on-demand notification support with Notification::route('Webex', $webexTarget)->notify(new YourNotification()). That is handy for one-off alerts from scheduled jobs or console commands where no Eloquent model is involved. The routing value must match whatever the channel expects for a room or webhook, so verify the format against the package source.
- What is the difference between v1.0.1 and v2.0.0 of laravel-notification-channels/webex?
- The only documented change in v2.0.0 is support for Laravel 11. In this package family, that typically means the framework constraint was tightened, which forces a semver-major release even when runtime behaviour is unchanged. Before upgrading, confirm whether WebexMessage methods, config keys, or the channel identifier string changed, and whether both bot token and incoming webhook auth modes still work.
- Does this package support Adaptive Cards, attachments, or only plain text?
- The package is a thin notification channel for pushing message content into a Webex space, and the release notes do not document Adaptive Card or attachment support. If your payloads depend on rich cards, buttons, or file uploads, inspect the message class source or open an issue before committing. Otherwise plan on plain text or markdown content only.
- Is laravel-notification-channels/webex safe to use in production?
- The code footprint is small and predictable, but this is a community-maintained package with a low release cadence, a limited contributor base, and no first-party Cisco backing. That maintenance risk, rather than code quality, is the main long-term concern. Pin the version you validate, wrap the channel behind your own notification classes, and monitor the repository for issue and PR response activity.
- How do I test Webex notifications without hitting the real Webex API?
- Use Laravel's Notification::fake() in your tests and assert that the expected notification was sent to the expected notifiable, which avoids any outbound HTTP call. For channel-level tests, mock the underlying HTTP client rather than relying on the package for a fake transport. The repository does not appear to ship a documented test matrix, so verify compatibility with your Laravel version yourself.
- What are the alternatives if this package does not fit my needs?
- You can call the Webex REST API directly with Laravel's HTTP client, which gives full control over cards, attachments, and room management. Community Slack and Microsoft Teams notification channels often have more users and battle-testing if your destination is flexible. If you need bidirectional Webex integration or inbound event handling, this package is not the right tool and a direct integration or dedicated SDK is a better fit.
Weaver
How can I help you explore Laravel packages today?