Weave Code
Slack Bundle Laravel Package
quitoque/slack-bundle
Symfony bundle that simplifies sending Slack notifications and messages from PHP applications, with configurable integration for Slack clients, webhooks, and channel alerts so teams can add messaging to Symfony projects quickly.
This bundle provides integration with the Slack API library, allowing you to interact with the Slack API from within your Symfony projects
Frequently asked questions about Slack Bundle
- Is quitoque/slack-bundle a Laravel package?
- No. It is a Symfony bundle, registered through config/bundles.php or AppKernel.php and configured via a Symfony configuration tree, with no Laravel service provider, facade, or publishable config. The package description in some briefs mislabels it as Laravel, so confirm your target framework before planning any integration work. If you are on Laravel, treat this as a third-party Symfony dependency rather than a native package.
- How do I install quitoque/slack-bundle in a Symfony application?
- Install it with Composer, register the bundle in config/bundles.php, and add your Slack credentials and client options to a file under config/packages/. Before merging, verify that its composer.json constraints for PHP, Symfony, and the underlying Slack client resolve against your current stack. Because the package has no dependents or reference implementations, test the resolution on a scratch branch first.
- Does quitoque/slack-bundle work with Laravel?
- Not natively. You would either pull Symfony bundle machinery into a Laravel app with little benefit, or bypass the bundle and bind the underlying Slack client manually, at which point the package adds almost nothing. The cleaner path is to use Laravel's built-in Slack notification channel or Slack's official PHP SDK behind a small internal adapter such as SlackNotifier.
- How do I configure Slack credentials and channels for this bundle?
- Configuration goes through the bundle's Symfony config tree, typically covering the bot token, default channel, and client options. Keep tokens and signing secrets in environment variables rather than committed YAML, and check whether your Symfony environment compiles configuration into a container cache that could retain secrets on disk. Review cache permissions and deployment artifacts before going to production.
- Which Slack client library and API version does quitoque/slack-bundle wrap?
- The bundle is a thin dependency-injection wrapper around a Slack API client, so the real capability lives in that underlying library. Inspect composer.json and the lock file to identify the exact client and pinned version, then confirm it supports the calls you need, such as chat.postMessage with Block Kit payloads. A pinned, stale client is the main way this package silently falls behind Slack platform changes.
- What PHP and Symfony versions does quitoque/slack-bundle support?
- That is determined entirely by the constraints declared in its composer.json, which you should read before adoption. With zero stars, zero dependents, and no downstream bug reports, there is no ecosystem evidence that those constraints resolve on a current PHP or Symfony release. Run a Composer resolution test against your versions and treat an unknown result as a planning risk.
- Is quitoque/slack-bundle actively maintained?
- There is no meaningful community signal around the package, which is a strong proxy for it being unmaintained. Assume no security patches, no tracking of Slack API deprecations, and no PHP or Symfony version bumps unless you do them yourself. If you adopt it, assign an internal owner for the fork and agree a patch SLA up front.
- How do I send a Slack alert from a Symfony controller or event listener?
- Inject the service exposed by the bundle through the dependency-injection container and call it from your controller, service, or event listener. To keep Slack-specific logic out of business code, hide the bundle behind your own interface, for example a SlackNotifier with a single notify method. That way controllers and listeners depend on your abstraction rather than on an abandoned third-party bundle.
- How should I test Slack notifications without calling the real Slack API?
- Put your own interface in front of the bundle, then mock or fake that interface in unit and functional tests so no network calls occur. Prototype one real call path end-to-end against a sandbox Slack workspace before committing to the dependency. Avoid asserting against the bundle's internals, since you may need to replace it with the SDK or a fork later.
- What are the alternatives to quitoque/slack-bundle for Slack notifications in PHP?
- On Symfony, the framework's Notifier component with its Slack transport is the maintained option. On Laravel, use the built-in Slack notification channel, and in either case Slack's official PHP SDK or a direct signed webhook call covers simple outbound messages. Whichever you choose, wrap it in a small adapter so call sites stay unchanged if the dependency shifts.
Weaver
How can I help you explore Laravel packages today?