Act faster with our new Slack integration
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
Octopus Deploy has added a native Slack integration with two usage modes: Subscriptions, which route event notifications (like deployment failures, variable changes, API expiries) to Slack channels alongside existing webhook and email options, and a new Send a Slack Message step that uses OAuth for simpler setup than community steps, letting teams post messages from any point in a deployment or runbook process, such as right before a manual intervention. The team is also gauging interest in a Microsoft Teams integration and adding webhook triggers for runbooks.
Table of contents
Subscriptions: our notification engineSlack steps made simpleLearn moreWhat’s next for notifications?Tags:Questions this post answers
How do I send Slack notifications for Octopus Deploy deployment failures?
Use the Subscriptions feature in Octopus Deploy, which now supports sending event notifications directly to a Slack channel, in addition to existing webhook and email options. Event filters let you scope notifications to specific projects, tags, or environments, so a channel like #deployment-failures only receives relevant alerts instead of everything. Teams tuning deployment alerting workflows can follow devops integration news like this on daily.dev.
How can I notify an approver in Slack when a deployment needs manual intervention in Octopus Deploy?
Add the built-in Send a Slack Message step immediately before a manual intervention step in the deployment or runbook process. It uses OAuth so setup only requires choosing a channel and message, and the message field supports Slack markdown plus Octopus variables like project, release number, environment, and a deployment link. Anyone streamlining approval handoffs in deployment pipelines can track tooling updates like this on daily.dev.