Notifications and webhooks
The notification feed, desktop alerts, and Discord, Slack or generic webhook messages.
Updated Oct 30, 2026
Notifications
A bell icon in the title bar opens a popover with the same feed; "See all" opens the full Notifications page below, which has two tabs, Feed and Alerts. The Feed lists events for the currently selected server as they happen. Each entry has a timestamp, the server name, and a message. Events are categorized by type with a colored icon:
- Join (green): a player connected
- Leave (grey): a player disconnected
- Advancement (amber): a player earned an achievement
- Restart (grey): the server restarted
- Error (red): an error was logged
- Crash (red): the server stopped unexpectedly
- Automation (green): an automation rule fired and this was its result
You can filter by type using the tab bar, or clear all notifications for the current server. Notifications are session-scoped; they clear when Coalstack closes. Notifications appear regardless of which page you're on.
The Alerts tab is where you choose what leaves the feed. Desktop notifications (on by default) show a native pop-up for the events you pick, such as server crashes and failed backups, while Coalstack is in the background; a "Send a test notification" button confirms they work. The same tab holds the per-server webhook notifications.
Settings → General includes a toggle to hide the feedback toast that appears on startup. When it is on, the toast stays hidden on every future launch.
Webhook Notifications
Coalstack can send notifications to Discord, Slack, or any endpoint that accepts a JSON webhook POST. The webhook is per-server: paste the URL into the Webhook Notifications section of Notifications → Alerts, pick the matching format (Discord/Slack/Generic), and Coalstack posts messages there automatically. This needs Coalstack Plus.
The app sends notifications for: the server coming online ("Server is online"), a player joining or leaving, and the server stopping unexpectedly (possible crash). A "Send Test Message" button confirms the webhook is working. Webhook URLs are stored in the server's config file; they're not high-value secrets (they can only post messages to one channel), so they don't go through the OS keystore.