Alerts in Discord

18.6. Alerts in Discord — Sending Alerts via Discord

Discord is one of the standard delivery targets for every cron job

As stated throughout chapter 18, every monitoring job supports delivering results to Telegram, Discord, Slack, Signal, or a local file — Discord is especially suitable for teams, because a public channel in a server lets many people follow the same alert stream.

Configuring delivery to Discord

/cron add "every 6h" "Check repo X: new issues, newly merged PRs, new releases. If nothing new, [SILENT]." --deliver discord --name "Repo watcher"

Specific permission requirements — the common cause of silent delivery failures

Each messaging platform needs the correct permissions to receive messages — for Discord, the bot must have permission to send messages in the exact target channel; if it does not, delivery fails silently with no clear error displayed immediately.

You can send to multiple targets at once

--deliver telegram,discord

A single job can deliver results to multiple platforms at once via a comma-separated list — useful when you need both the team channel (Discord) and a personal alert (Telegram) for the same event.

Notes

• If an alert does not arrive in Discord even though the job reports success, check the bot’s permissions in the target channel immediately before doubting the prompt logic — this is the most common cause of silent delivery failure.
• With the default header/footer wrapping around cron responses (cron.wrap_response: true), some Discord integrations may render it poorly — turn this option off in the config if the formatting breaks.
• Use clear job names (--name "Repo watcher") when sending many kinds of alerts into the same Discord channel — it helps distinguish the origin of an alert when many jobs dump into one channel.