Discord

Create an incoming webhook for each Discord channel or use case that needs separate subscriptions. Discord gives each webhook an ID and token in a URL shaped like https://discord.com/api/webhooks/<id>/<token>. Store those two parts separately in Towbar’s protected YAML file; the token is not shown in the dashboard.

/etc/towbar/towbar.yml

notifications:
  enabled: true
  providers:
    discord:
      - webhookId: "123456789012345678"
        webhookToken: "<webhook-token>"
      - webhookId: "234567890123456789"
        webhookToken: "<second-token>"
  routes: []

Run sudo towbar config validate and sudo towbar restart. Open Manage → Notifications → Discord. Towbar shows one row per webhook ID. Choose Deployments, Backup & Restore, and Alerts & Incidents independently for each row. New webhooks start with no subscriptions, so select a category before expecting operational events.

Verify and maintain

Use Test to send a sample notification after confirmation. Check the intended Discord channel and the delivery result. If delivery fails, check that the webhook still exists, its ID and token remain paired, and the target channel permits webhook posts. Adding or removing a pair requires editing YAML, validating, and restarting Towbar. Rotate an exposed webhook in Discord and update its token in Towbar; preserve the ID only when Discord preserves it. Additional Discord destinations for one app or resource can be declared in its manifest. Do not put webhook tokens in that manifest.

Discord webhook IDs and category subscriptions in Towbar.

Each configured Discord webhook ID has its own category subscriptions.

Overview

Source control

Container registries

Backup providers

External secrets

Platform services

Notifications

Verify and maintain

​Verify and maintain

Verify and maintain