Discord Notifications

Discord notifications are delivered as color-coded embeds via a Discord channel webhook. Red for critical, orange for warnings, blue for info — at a glance you can tell which posts deserve attention.

Prerequisites

• A Discord server (Guild) where you have Manage Webhooks permission
• The text channel you want notifications posted to

Step 1 — Create the Discord webhook

1. In Discord, open the destination channel.
2. Click the gear icon next to the channel name → Edit Channel.
3. In the left sidebar, choose Integrations.
4. Click Webhooks → New Webhook.
5. Give it a name (e.g., Reoclo) and optionally a custom avatar — these appear as the message author in posts.
6. Click Copy Webhook URL. It looks like https://discord.com/api/webhooks/123456789012345678/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.
7. Click Save Changes.

Caution

The webhook URL is the channel’s secret — anyone with it can post in the channel. Don’t commit it to git.

Step 2 — Create the channel in Reoclo

Dashboard

1. Open Settings → Notification Channels.
2. Click Add Channel → Discord.
3. Give it a name (e.g., #engineering-deploys).
4. Paste the webhook URL into Webhook URL.
5. Click Send Test — a [TEST] embed should appear in Discord within a second.
6. Pick which events this channel receives.
7. Save.

CLI

reoclo channels create discord \
  --name "engineering-deploys" \
  --secret "https://discord.com/api/webhooks/.../..." \
  --events deploy_succeeded,deploy_failed

Or via YAML:

kind: discord
name: engineering-deploys
config: {}
secret: ${env:DISCORD_WEBHOOK_URL}
events:
  deploy_succeeded: true
  deploy_failed: true

DISCORD_WEBHOOK_URL="https://discord.com/api/webhooks/..." \
  reoclo channels create discord --from-file discord-deploys.yaml

Message format

Each notification posts as a single embed with the event summary as the title and the event body as the description. The embed color reflects severity:

Severity	Color	Hex
critical	Red	#FF0000
warn	Orange	#FFA500
info	Blue	#0080FF
none	Gray	#808080

Reoclo treats HTTP 200 and 204 as success.

Troubleshooting

Symptom	Cause	Fix
404 Unknown Webhook	Webhook was deleted in Discord	Create a new webhook and update the channel secret
401 Unauthorized	URL was rotated or truncated when copying	Re-copy the webhook URL from Discord (be sure you got the full token after the ID)
429 Too Many Requests	Discord rate limit hit (5 req/2s per webhook)	Reoclo retries with backoff — for high-volume use, split events across multiple webhooks
Test passes, real events silent	Event toggles disabled	Open the channel and enable the events you want
Embed shows but no color	Severity is null (not from an alert)	Expected for non-alert events; the default gray means “informational”

Routing tips

• Use channel topics for routing. One Discord channel per concern (deploys, monitoring, incidents) keeps signal high.
• Mention roles in the channel description — Reoclo doesn’t insert mentions itself; configure your Discord channel to ping the right role on @here if you need attention.
• Webhooks are bound to one channel. To post to a different channel, create a new webhook there.

Next Steps

• Set up Slack or Microsoft Teams if your team works across multiple chat platforms
• Wire events from Monitoring & Uptime into your Discord channel