Discord Notifications

Using Discord’s Webhook, you can send monitor incident notifications to a Discord channel as Embed messages.

1. Open the server integration settings

   In the target server settings, open Integrations > Webhooks. You need permission to manage Webhooks.

2. Create a Webhook

   Select Create Webhook.

3. Choose the destination

   Choose the channel where Discord should post and set a recognizable name (for example, Manako).

4. Copy the Webhook URL

   Click “Copy Webhook URL” on the webhook you created.

1. In the dashboard, open Settings > Integrations, then select Configure for Discord
2. Enter a recognizable Name
3. Paste the URL into Discord Webhook URL
4. Select Add

Notifications are sent to Discord as Embed messages, color-coded by event type.

Item	Content
Color	Red (#ef4444)
Title	Monitor Down
Description	{Monitor Name} is down
Fields	Monitor: {Monitor Name}, URL: {Monitored URL}, Incident ID

Item	Content
Color	Green (#22c55e)
Title	Monitor Recovered
Description	{Monitor Name} is back up
Fields	Monitor: {Monitor Name}, Incident ID

Maintenance start and end events are also sent as Embeds. The start Embed includes the affected monitors and scheduled end time.

• The URL is rejected during setup: It must use HTTPS on discord.com or discordapp.com, and its path must begin with /api/webhooks/.
• No message is sent: Confirm that the Webhook was not deleted or regenerated and can still post to the target channel.
• A test arrives but normal notifications do not: When a monitor has channel links, only active linked channels are used. If links exist but all are disabled, Manako does not fall back to team-wide channels.
• Notifications stop during rapid state changes: After more than three state changes for the same monitor within 10 minutes, the flap guard suppresses subsequent notifications.
• Notifications appear duplicated: A sent record for the same incident, channel, and event type skips a retry. Creation and recovery are separate events, and failed or pending records are retried.

Test sends a real Discord Embed and has a 60-second cooldown after success. A failure on one channel does not stop the remaining channels.

The flap guard and incident-level sent check apply to incident notifications. Maintenance notifications bypass both controls and go to active, verified team channels.