Notifications
Brokerr can send a Discord webhook after a run reaches a terminal state. Open Settings → Notifications, add a webhook, choose its scope, and use Test before relying on it for operational alerts.
Scope and outcomes
Section titled “Scope and outcomes”A webhook can receive all runs or only runs for one profile. You can enable notifications independently for successful, failed, and canceled outcomes. Success includes completed, preview, partial, and mixed results.
Optional message sections include:
- summary and run mode;
- start/finish timestamps;
- changes, applied, unmatched, skipped, ignored, and error totals;
- up to ten unmatched titles;
- up to ten sanitized errors.
Webhook URLs are encrypted in SQLite and are never returned to the browser. HTTP telemetry redacts the notification endpoint. A delivery failure is logged but does not turn an otherwise successful synchronization into a failed run.
Discord is a notification provider, not a source or target. Additional transports can implement the separate notification provider contract without adding media capabilities.