The Qovery Slack app sends real-time deployment alerts to the Slack channels of your choice. Install it in two clicks and set it up in less than a minute.
Qovery now sends deployment alerts to Slack, and setting it up takes less than a minute. Click Connect Slack in your organization settings, approve the app in Slack, and create an alert rule. From then on, your team is notified in the channel you choose when a deployment fails, keeps failing, or recovers. Each alert links to the logs and the console, so you can start fixing from the message.
What you get
Each alert rule decides three things: which deployments to watch, which Slack channel gets the alert, and which alerts to send.
You can scope a rule by project, environment or environment type. For example, production failures can go to #prod-alerts while staging stays quiet. Any public channel in your workspace shows up in the channel list. For a private channel, invite the Qovery bot first.
A rule can send three alerts:
Deployment failed: the first failure of a deployment.
Failure loop: the same environment failed 5, 10, 20 or 50 times in a row. CI and schedulers can retry a broken deployment over and over without anyone noticing.
Recovered: a reply in the thread once the environment deploys successfully again.
The default message is designed to be read at a glance. One line tells you which environment failed and its type, the project, the services that failed, and who triggered the deployment.
You can also write your own failure message, with variables such as {{environment_name}}, {{project_name}}, {{failed_services}} and {{triggered_by}}.
Each alert comes with buttons to act on it without leaving Slack: Open in console, View logs, Mute 24h for a noisy environment, and Alert settings to adjust the rule. Follow-up failures and the recovery message are posted as replies in the thread of the first alert, so one incident stays one conversation instead of flooding the channel.
Get started
Installing the app takes two clicks, and the whole setup takes less than a minute:
In the Qovery console, go to Organization settings → Notifications → Slack and click Connect Slack. Approve the Qovery app in your Slack workspace.
Add an alert rule: pick a channel, give the rule a name, and narrow it down by project, environment or environment type.
Choose your alerts (Deployment failed, Failure loop, Recovered) and, if you like, customize the failure message.
Save. The next failure in that scope lands in your channel.
Tip: start with one rule for your production environments only. That's where a silent failure costs the most, and it keeps the channel quiet while your team gets used to it.
Already using a Slack webhook? It keeps working alongside the Slack app.
Deployment alerts where your team already works
Connect your Slack workspace from your organization settings and get your first alert rule running in less than a minute.
This first version covers deployment failures. New notification types will use the same Slack app, so you won't have anything to reinstall. Coming next:
Clusters: a cluster deployment that failed, or a maintenance in progress.
Domains: a TLS certificate that expired or is about to.
Applications: a service that deploys fine, then keeps crashing.
Integrations: a Git token that expired while services still depend on it.
All of it managed from a single Notifications page in your organization settings.
Connect your workspace today and tell us which alert you want next.
Théo is a senior product designer at Qovery. He shapes the visual and interaction design of the Qovery Console, with a focus on clarity, consistency, and developer-friendly UX.
Next step
Deployment alerts where your team already works
Connect your Slack workspace from your organization settings and get your first alert rule running in less than a minute.