One Gate for all your Notifications

Send events to notification channels

Immediately routes matching events to your configured notification channels like Slack, Discord, Email, or Webhooks. You can send to multiple channels at once.

Limit event frequency over time

Controls how many events can be processed within a specific time window. For example, allow maximum 3 events per 5 minutes to prevent notification spam.

Block events from being sent

Completely blocks matching events from being processed or routed. Useful during maintenance windows or to silence known issues temporarily.

Re-route events after a time delay

Waits for a specified time period before routing events to different channels. Perfect for escalating unresolved issues to higher priority channels or on-call teams.

Modify event data before routing

Changes event properties before they're sent to notification channels. You can override severity levels or add custom tags to enrich event metadata.

Combine multiple actions per rule

Mix and match actions in a single rule. For example: throttle, transform severity to "critical", then route to PagerDuty and Slack - all in one workflow.

Rule: $.environment == "production"

Action: Route production errors to Email + Slack, staging to Discord, dev to Slack #engineering. Change routing instantly without code deploys.

Rule: $.project == "sensor-api"

Action: Throttle to max 3 alerts per 5 minutes. Prevent Slack flooding from chatty services while preserving critical signals. Reduce alert volume by 80%.

Rule: $.type == "database.connection_failed"

Action: Mute known issues during planned downtime. Toggle rules on/off instantly via UI - no code changes. Resume alerts when maintenance completes.

Rule: $.level == "critical"

Action: Escalate via webhook after 15 minutes if Slack alert unacknowledged. Automatic escalation chains ensure critical issues reach on-call engineers.

Rule: $.type == "payment.failed"

Action: Transform to redact credit card numbers, mask PII, or override severity levels before routing. Enrich events with custom tags without changing app code.

Rule: $.metadata.customer_tier == "enterprise"

Action: Transform to add priority tag → Route to Slack + Email → Escalate to PagerDuty after 5min. Combine actions for complex workflows.