Channels define where notifications are sent. Supported types:

• webhook — HTTP POST to any URL with optional custom headers and body template. Use in the body template for the alert message.
• slack — Post to a Slack Incoming Webhook URL.
• email — Send via SMTP. Supports STARTTLS. Credentials are stored in the database; use environment-level secrets management for production deployments.
• browser_push — Web Push notifications to browsers. Click Generate & Save Keys in the browser_push channel form to create VAPID keys stored in the database. Alternatively set SOBS_VAPID_PRIVATE_KEY as an environment variable (takes precedence). Use the Subscribe This Browser button to register the current browser automatically.

Rules define when to send notifications. Each rule has one or more conditions matched against recent signal averages from v_derived_signals_1m or recent tag assignments from sobs_record_tags. Use ANY (OR) or ALL (AND) logic to combine signal-only, tag-only, or mixed signal+tag conditions. A cooldown prevents re-firing until the configured interval has elapsed.

Triggering: Call POST /api/notifications/check periodically (e.g., every minute via cron) to evaluate all enabled rules and dispatch notifications.

Browser Push Key Management: Use the Generate & Save Keys button in the browser_push channel form to create a VAPID key pair and persist it in the database automatically. Use Regenerate to rotate keys (existing subscriptions must re-subscribe). Set SOBS_VAPID_PRIVATE_KEY in your environment to override the DB key (useful for production secret management).