Documentation

Alerts

AdminUpdated Sep 20, 2026

Alerts

Get notified when important events happen in your server — nukes, raids, mass deletions, or bot token churn.

Overview

Alerts notify you when something unusual or dangerous happens in your Discord server. You can receive alerts via email, Discord DM, Discord channel message, or webhook. Alerts can also trigger automatic protective actions.

Alert Types

| Alert | Triggered When | Available Actions |
|---|---|---|
| Anti-Nuke | Someone deletes channels/roles/bans in bulk within a short window | Kick or ban the responsible user, restore deleted items from backup |
| Anti-Raid | A large number of new members join within a short window | Pause verification, enable strict mode, kick unverified joiners |
| Mass Ban | More than N members are banned in a short period | Log and notify |
| Mass Kick | More than N members are kicked in a short period | Log and notify |
| Mass Channel Delete | More than N channels deleted in a short period | Restore from backup, kick responsible user |
| Mass Role Delete | More than N roles deleted in a short period | Restore from backup |
| Token Churn | A significant percentage of stored OAuth2 tokens expire or are revoked | Notify with count and estimated pullable members remaining |
| Backup Failure | A scheduled backup fails | Notify with error details |
| Member Milestone | Server reaches a member count milestone (e.g., every 1,000 members) | Notify only |

Configuring Alerts

  1. Go to server settings → Alerts tab.

  2. Toggle each alert type on or off.

  3. Set thresholds where applicable (e.g., "trigger anti-nuke if more than 3 channels are deleted within 60 seconds").

  4. Configure notification channels:

  • Email — Sent to your Restore Hub account email

  • Discord DM — DM to your Discord user ID (requires having verified through your own bot)

  • Discord Channel — Posted to a server log channel via the bot

  • Webhook — HTTP POST to any URL with a JSON payload

Anti-Nuke Thresholds

Configure how sensitive each nuke detector is:

| Detector | Default Threshold | Window |
|---|---|---|
| Channel deletes | 3 in | 30 seconds |
| Role deletes | 3 in | 30 seconds |
| Mass bans | 5 in | 60 seconds |
| Mass kicks | 10 in | 60 seconds |
| Emoji deletes | 10 in | 60 seconds |

Lower thresholds = more sensitive = more false positives. Adjust based on how active your admin team is.

Automatic Protective Actions

For Anti-Nuke and Anti-Raid alerts, you can configure automatic responses:

| Action | Description |
|---|---|
| Kick responsible user | Immediately kicks the user who triggered the event |
| Ban responsible user | Immediately bans the user who triggered the event |
| Lock down server | Sets all public channels to read-only for members |
| Pause verification | Temporarily stops new members from verifying |
| Restore from backup | Automatically restores the most recent backup (channel/role deletes only) |

Warning: Automatic actions run immediately without confirmation. Test your thresholds carefully before enabling automated banning. A mis-configured threshold could ban a legitimate admin.

Webhook Payload

When an alert fires to a webhook URL, the payload looks like:

{
  "type": "ANTI_NUKE",
  "serverId": "123456789",
  "serverName": "My Server",
  "triggeredAt": "2025-01-15T10:30:00Z",
  "details": {
    "action": "CHANNEL_DELETE",
    "count": 5,
    "responsibleUserId": "987654321",
    "responsibleUsername": "badactor#0001"
  }
}
Was this page helpful?