Discord Stonker Bot

Turn the alerts Discord Stonker Bot sends, such as a lost connection to Discord or a job that gave up, into ntfy notifications with the app's name before each title.

Input Handling

The interpreter reads the JSON alert that Discord Stonker Bot posts to a destination whose service is ntfy-reverse-proxy. Every field below is required, and fields that aren't listed are ignored.

The notification uses title, message, priority, and tags. The event, occurredAt, and details fields must be present, but they don't appear in it.

Supported Events

Discord Stonker Bot sends these alerts, each with a fixed priority and tags:

Test notification is what Send test sends, so a destination can't choose it as an event.

Context Setup

1. Add an HTTP context — Run nrp, choose Manage Contexts > Add, pick HTTP, and choose Discord Stonker Bot as the Interpreter.
2. Deploy — Choose Deploy, then copy the context's URL and token from the Context reference list it prints.
3. Add a destination — On Discord Stonker Bot's Notifications page, select Add notification, choose ntfy-reverse-proxy as the Service, and paste the URL into Context URL. Paste the token into Context token if the context has one, enter a Name, and select Add notification to save it.
4. Send a test — Select Send test on the destination, and check that [Discord Stonker Bot] Test notification arrives on the context's topic.

Under Context URL, the dialog reminds you with Set the context's interpreter to discord-stonker-bot.

{
  "id": "discord-stonker-bot-example",
  "name": "Discord Stonker Bot",
  "type": "http",
  "interpreter": "discord-stonker-bot",
  "topic": "discord-bot",
  "mode": "send-once",
  "show_visitor_info": false,
  "primary_server": "primary",
  "servers": ["primary"],
  "token": "replace_with_auth_token"
}

With this context, Discord Stonker Bot posts its alerts to https://discord-stonker-bot-example.ntfy.example.com.

Notification Output

• Title: [Discord Stonker Bot] and the alert's title (e.g., [Discord Stonker Bot] Bot disconnected).
• Body: The alert's message, with HTML tags removed as for every interpreter (see HTML Stripping).
• Priority: The alert's priority, unchanged. Discord Stonker Bot sends 4 for high-priority events and 3 for the rest.
• Tags: discord-stonker-bot first, then the alert's tags (e.g., discord-stonker-bot, warning).

The interpreter sets no icon, actions, or Markdown.

Example

Discord Stonker Bot posts this alert when it has been off Discord for a minute:

{
  "app": "discord-stonker-bot",
  "details": {
    "downSince": "2026-10-26T12:00:00.000Z"
  },
  "event": "bot-disconnected",
  "message": "The bot lost its connection to Discord and hasn't reconnected after a minute. Features that need Discord are paused until it does.",
  "occurredAt": "2026-10-26T12:01:00.000Z",
  "priority": 4,
  "tags": ["warning"],
  "title": "Bot disconnected",
  "version": 1
}

The proxy publishes it to ntfy with these ntfy headers and body:

X-Title: [Discord Stonker Bot] Bot disconnected
X-Priority: 4
X-Tags: discord-stonker-bot,warning

The bot lost its connection to Discord and hasn't reconnected after a minute. Features that need Discord are paused until it does.

ntfy shows the warning tag as an emoji and lists discord-stonker-bot below the notification.

Wrong App Error

A context reads alerts from one app, so a payload whose app names a different app fails instead of arriving under the wrong name. When that app has a built-in interpreter, the proxy answers with HTTP 422 and names the interpreter to use:

{
  "status": "error",
  "message": "This context reads Discord Stonker Bot alerts, but the payload came from outpost. Set the context's interpreter to outpost."
}

If app contains an unknown producer key, the error instead says the app is unsupported and lists the supported interpreter keys. It never recommends configuring the unknown value.

• Fix — Set the context's interpreter to the key the message names, or point that app at a context that uses its own interpreter.
• Send test — The sending app reports that the test couldn't be sent, with HTTP 422 and up to 120 characters of this message as the reason.
• Error topic — If the context has an error_topic and error_events includes interpretation (or is omitted), the proxy also sends an Interpretation Error with error-debug.json to that topic.
• Other payloads — A non-empty body that isn't JSON, or JSON that isn't an alert (such as one without title, or with a version other than 1), also fails with HTTP 422 before the app is checked.