Just Dashboard Notifications
Deliver deployment results and alerts through chat, email, signed webhooks, and GitHub commit status.
Open Deployments → Notifications to manage notification channels. The page draws every deployment wired to the channels it reports to, then lists the Channels beside Recent messages. A channel can announce when a deployment run starts, succeeds, fails, or is cancelled; failures include a verified rollback to the previous release. The same channels also carry the alerts you set up elsewhere in the dashboard.
| Channel | What you supply |
|---|---|
| Discord | A channel webhook URL |
| Slack | An incoming webhook URL |
| Telegram | A bot token and chat id |
| SMTP host and port, security (STARTTLS, TLS, or None), sender, and recipients | |
| Signed webhook | An HTTP(S) endpoint; the dashboard gives you a shared signing secret |
Set up a channel
- Select Add channel, choose a type, and enter its destination and credentials.
- Under Events, choose the run events it should receive. A new channel selects Succeeded and Failed; add Started or Cancelled if you need them. A channel with all four reads as Every event.
- Under Delivery, leave Deliver as soon as it is saved on, or turn it off to keep the channel paused.
- Save the channel, then choose Send test from its menu. The channel shows whether the receiver accepted it.
If a message does not arrive, open the channel's Delivery history. It lists each attempt with its event, run, status, and how the receiver answered, such as refused, server error, or unreachable. Pause channel stops deliveries without deleting the configuration; Resume channel starts them again. Edit channel and Remove channel are in the same menu.
Channel credentials are sealed by the dashboard and masked when listed; the dashboard never shows them again, so enter them anew to change them. Copy a new signed webhook's secret immediately, and verify X-JD-Signature-256 in the receiver before acting on a message. Failed deliveries are retried; they do not change the deployment run's result. Every account can read the channels and their history, but only administrators can create or change them.
Alerts that use these channels
Alert rules choose their channels themselves, whatever events the channel selects:
- Traffic alerts for a project, under its Settings → Automation.
- Alerts on the Proxy & TLS overview, for failed certificate renewals, expiring or mismatched certificates, and TLS grade.
- Alerts on a database, for a server that stops answering, disk, connections, replication lag, and missed backups. See Databases.
A rule's firing and recovery messages appear in the channel's history beside deployment events.
GitHub commit status and pull requests
For GitHub repositories, a project can also report pending and final release status on its commit. Turn on Report each release as a GitHub commit status under Project → Settings → General → Automatic deployment. A connected GitHub App can also keep one pull-request comment updated for each preview. See Automation and previews.