Discord integration

Send incident updates to Discord

Every incident action — opened, acknowledged, reassigned, severity changed, resolved — is delivered to your Discord channel as a durable, retried message that links straight back to the incident.

No credit card required for the trial · EUR subscriptions through Stripe

01 / Overview

One channel that mirrors the incident record

MonoDuty posts to an incoming webhook that you create in your Discord channel’s Integrations settings. Each incident action produces one message carrying the severity, title, current status, and the latest detail, rendered as a rich embed with status and severity fields.

Delivery is a persisted reservation, not a fire-and-forget HTTP call. Each message is written with an idempotency key inside the same transaction as the incident action, so a retry, a duplicate action, or a worker restart cannot post the same update twice.

02 / Operating value

Built for the channel people actually watch

Chat is where response happens. The integration is designed so the channel never disagrees with the incident record.

Exactly-once messages

Each incident action reserves one delivery under an idempotency key. Repeated processing reuses the reservation instead of posting again.

Evidence for every attempt

Attempts are recorded individually with their outcome, so a missing message can be traced to a specific failed attempt rather than guessed at.

Failures you can replay

A delivery that exhausts its retries is retained and can be requeued by an admin against an allowlisted reason code, leaving an audit trail.

Secrets kept as secrets

The webhook URL is encrypted at rest, never returned by the API, and only accepted when it matches this provider’s exact host allowlist.

03 / Workflow

Connect it in three steps

A workspace admin can complete this without leaving the dashboard.

  1. 01

    Create the webhook in Discord

    In your Discord channel’s Integrations settings, create an incoming webhook for the channel that should receive incidents and copy its URL.

  2. 02

    Add it in MonoDuty

    Open Organization → Integrations, choose the provider, and paste the URL. MonoDuty validates it against the provider host allowlist before storing it encrypted.

  3. 03

    Verify with a real incident

    Trigger a test incident and confirm the message, the deep link, and the delivery record. The integration can be disabled at any time without deleting its history.

04 / Plans

Included on Pro and Business

Discord delivery is part of the paid plans; the Free plan keeps email notifications and universal webhooks.

01

Free

Email notifications and universal inbound webhooks. Chat delivery is not included.

02

Pro — €9 per user/month

Slack, Discord, and Microsoft Teams delivery, alongside SMS, voice, escalation policies, audit log, and postmortems.

03

Business — €19 per user/month

Everything in Pro with higher limits, longer retention, and priority support.

Compare the complete plan matrix

05 / Questions

Common questions

01Can I acknowledge or resolve an incident from inside Discord?

No. The integration is one-way: MonoDuty delivers updates to Discord. Acknowledging and resolving happen in MonoDuty, in the API, or through the phone and SMS response paths. Every message links directly to the incident.

02Does this replace SMS or voice alerting?

No, and it should not. A chat message is not a wake-up. Chat keeps the responding team in sync; on-call escalation still routes through email, SMS, and voice with delivery receipts.

03Which Discord URLs are accepted?

Only HTTPS webhook URLs on discord.com or discordapp.com webhook paths. A URL with embedded credentials, a custom port, or a fragment is rejected.

04What happens if the channel is deleted or the webhook is revoked?

The attempts fail and are recorded with their outcome. The delivery is retained so an admin can repair the endpoint and requeue it, rather than silently losing the update.

05How many integrations can one workspace have?

One per provider, so a workspace can run Slack, Discord, and Microsoft Teams at the same time. Managing them requires a Billing Owner or Account Admin with a fresh step-up.

MonoDuty / Start

Put incidents in your Discord channel

Start a 14-day trial, connect a channel, and watch a real incident travel from detection to resolution without anyone refreshing a dashboard.