System Alerts

Overview

System alerts notify you when a webhook connection starts having errors. Instead of checking the event log manually, you set a threshold and Commander tells you when something needs attention.

Enabling Alerts

1. Open your webhook connection
2. Go to Settings
3. Find the Error Alerts toggle
4. Switch it on

When enabled, additional configuration options appear below the toggle.

Configuring the Threshold

Set how many errors trigger an alert. Choose from:

Threshold	When You'll Be Notified
After 1 error in an hour	Immediately on any failure
After 3 errors in an hour	When a pattern of failures starts (default)
After 5 errors in an hour	Only when errors are frequent
After 10 errors in an hour	Only during significant outages

Choose a lower threshold for critical webhooks (payments, orders) and a higher threshold for high-volume webhooks where occasional errors are expected.

Notification Channels

Choose how you want to be notified. You can enable multiple channels:

In-App Notification

A notification appears in Commander's notification bell. This is the simplest option — you'll see it next time you're in Commander.

Email

Sends an alert email to the address you specify. When you enable this channel, an email input field appears where you enter the destination address.

Chat Message

Sends a message to your connected chat. Useful if your team monitors a shared channel.

Configuration Summary

Setting	Field	Options
Enable	Error Alerts toggle	On / Off
Threshold	Dropdown	1, 3, 5, or 10 errors per hour
In-app	Checkbox	Notification bell
Email	Checkbox + email input	Sends to specified address
Chat	Checkbox	Message in connected chat

When Alerts Fire

An alert fires when the number of errors in a rolling one-hour window exceeds your threshold. For example, with a threshold of 3:

• Error at 2:00 PM — count: 1 (no alert)
• Error at 2:15 PM — count: 2 (no alert)
• Error at 2:30 PM — count: 3 (alert sent)

The count resets after the hour window passes.

Tips

• Start with the default threshold of 3 — it catches real problems without false alarms
• Use email for webhooks you need to know about even when you're not in Commander
• Enable in-app at minimum so you always have a record of alerts
• For high-volume webhooks (100+ events/hour), consider a higher threshold to avoid alert fatigue
• Check the health stats to understand your connection's baseline error rate before setting a threshold