Skip to content

Nightbell 3.16.0

Choose a tag to compare

@riveerxd riveerxd released this 07 Oct 20:24
· 68 commits to master since this release

Outages can now be posted to a team, not only to this phone. Nightbell sends them to Microsoft Teams, Slack, Discord, Google Chat, ntfy, Gotify, Telegram, or any address with a body you write yourself, straight from the phone with nothing in between.

Service What you paste
Microsoft Teams the URL from the channel's Workflows, "Send webhook alerts to a channel"
Slack, Mattermost, Rocket.Chat an incoming webhook URL
Discord a channel webhook URL
Google Chat a space webhook URL
ntfy the topic URL, on ntfy.sh or your own server
Gotify the server URL with ?token=
Telegram the bot token and a chat ID
Anything else your URL, method, headers and body, with {{placeholders}}

When something is sent: each webhook keeps the monitor's failure threshold, cooldown and repeat interval, so a flaky endpoint does not flood a channel. It ignores your quiet hours and mute unless you tell it to follow the phone. A pause from the dashboard stops every webhook, because a pause means the phone's own signal is not to be believed.

When the receiver is down: messages wait on the phone and are retried in the order they happened, from 30 seconds up to every half hour, for a day. A recovery never arrives before the outage it ends. Every request carries a delivery id that stays the same across retries, so a receiver can drop a repeat.

For your own receiver: a signing secret adds an HMAC-SHA256 signature over the timestamp and the body. The plain JSON body, the placeholders and the signature are documented in docs/reference.md.

Your addresses stay yours: a saved address is shown redacted, never goes into the diagnostic log, and is left out of a backup unless you switch on "Include tokens and webhook addresses".

Tested end to end against real ntfy and Gotify servers. The Teams, Slack, Discord, Google Chat and Telegram bodies follow each service's documented format but have not been sent to a live workspace yet. If one does not show up right, open an issue with what the test button answered.