Slack notifications
Coming with Hakopod Pro: send selected alarms, audit, deployment and service events to one Slack channel.
Slack notifications are coming with Hakopod Pro. They are not published or available to install yet. This guide describes the planned setup so teams can decide how they will connect Slack when the feature is released.
Choose the right Slack app flow#
Hakopod Cloud and self-hosted installations use different ownership models:
| Installation | Planned Slack setup |
|---|---|
| Hakopod Cloud | A workspace owner will authorize the Hakopod Cloud Slack app for that Cloud workspace. The app is not published in the Slack Marketplace today. |
| Self-hosted Hakopod | An installation administrator will create a Slack app in their own Slack workspace from the manifest shown in Settings, enter that app's credentials, and authorize it. |
The connection belongs to one Hakopod installation or Cloud workspace. It is not an application-level webhook and it does not give Hakopod a general-purpose Slack token.
What the connection will deliver#
The planned controls select a single Slack channel and the event types your team needs. The catalog will group them into alarms and audit records, deployment lifecycle changes, application changes, and service changes. That includes deployment queue, start, success, failure, cancellation and rollback requests; application creation, configuration, rename and deletion; and service configuration, readiness, failure, job and certificate events.
Each message will use a fixed event label and only the safe context needed to act: project and environment, the stable application identifier and name, service, deployment revision, and whether the event came from a recovery path. It will not include configuration bodies, secret values, logs or failure output.
Setup activity and test requests are not forwarded as audit events. Slack delivery is asynchronous: a queued test only confirms that Hakopod accepted the request. Check the delivery history and the chosen channel before treating a test as received.
Prepare a self-hosted workspace#
When the feature is released, open Settings → Integrations → Slack as an installation administrator with an active Pro entitlement. Copy the generated Slack app manifest, create the app in the Slack workspace your team controls, then provide its client ID and client secret to start Slack authorization.
The manifest will contain the exact callback URL for that installation. Do not reuse a callback URL, client secret, or app configuration from another installation. Hakopod will store Slack credentials server-side and will not return their secret values to the dashboard.
After authorization, choose a channel the app has joined, select the event types, review the changes, and save. Disconnecting stops future deliveries; it does not remove messages already posted in Slack.
Availability and access#
Slack notifications are a Pro capability in both Cloud and self-hosted deployments. A Cloud workspace owner or self-hosted installation administrator will manage the connection. Free installations can inspect the feature's availability but cannot configure delivery.
This documentation is a release-status notice, not a Marketplace listing or a promise of availability on a particular date. Follow the release notes for the published version that introduces the integration.