Skip to content
Sendora Cloud
Create account
2026-05-29 · Docs

Notifications module renamed Ops Alerts — copy now matches what the code does

  • Audit caught a code-vs-copy lie: marketing described the Notifications module as a Knock-style channel-agnostic notify() with preference center + per-channel fallback chains. The actual module ships Slack + HTTPS webhook routing for platform events (rule match → dispatch → retry → log). Different product.
  • Renamed to **Ops Alerts** across the marketing page, dashboard sidebar, and module registry. New category: Operate (was Engage).
  • The multi-channel fan-out story (Email + Push + SMS from one trigger) lives in Automation workflows, where the code actually does it — `step-executor.ts` calls each sender's service directly. The Knock comparison now points at Automation with honest gaps called out (no single-call `notify()`, no built-in preference center widget, per-module frequency caps instead of unified).
  • No backend change required — the existing channel API + retry worker are exactly the Slack/webhook router the new copy describes.