Configure Notification Channels for AI Alerts

Governance doesn't work if the right people don't hear about it. Keeptrusts notification channels deliver AI governance alerts — escalations, budget warnings, gateway issues, security events — to the tools your teams already use. Configure Slack, email, webhooks, PagerDuty, and Microsoft Teams in minutes.

Use this page when

• You need to connect Slack, email, webhooks, PagerDuty, or Microsoft Teams for AI governance alerts.
• You are configuring alert routing rules to direct different event types to different channels.
• You want to customize notification templates or enable digest mode for high-volume alerts.

Primary audience

• Primary: Technical Engineers and Operators configuring alerting infrastructure
• Secondary: Technical Leaders defining alert routing policies, Security Analysts integrating SIEM

What You'll Accomplish

• Connect notification channels for real-time AI governance alerts
• Route different alert types to different channels
• Customize notification templates for clarity and actionability
• Test channels before relying on them in production

Supported Channels

Channel	Best For
Slack	Team collaboration, escalation claims, real-time ops
Email	Compliance notifications, executive summaries, audit trails
Webhooks	Custom integrations, SIEM forwarding, automation triggers
PagerDuty	On-call incident escalation, SLA-critical alerts
Microsoft Teams	Organizations using the Microsoft ecosystem

Slack Integration

Setup

1. Navigate to Settings → Notifications → Add Channel
2. Select Slack
3. Click Connect to Slack — this initiates the OAuth flow
4. Select the workspace and channel to post to
5. Name the channel in Keeptrusts (e.g., "Slack #ai-alerts")
6. Click Save and Test

The test sends a sample notification to the channel. Verify it arrives before configuring alert routing.

Slack-Specific Features

• Actionable buttons — escalation notifications include Claim and View buttons that link directly to the console
• Thread replies — escalation resolution updates appear as thread replies to the original alert
• Channel override — routing rules can target different Slack channels for different alert types

# Example Slack channel configuration
notification_channel:
  type: slack
  name: "Slack #hipaa-escalations"
  workspace: "acme-corp"
  channel: "#hipaa-escalations"
  events:
    - escalation_created
    - escalation_sla_warning
    - escalation_resolved

Email Alerts

Setup

1. Navigate to Settings → Notifications → Add Channel
2. Select Email
3. Enter one or more recipient email addresses
4. Name the channel (e.g., "Finance team email")
5. Click Save and Test

Keeptrusts sends email notifications from a verified sender address. Check spam filters if test emails don't arrive.

Email Digest Mode

For high-volume alert types, enable digest mode to batch notifications:

• Immediate — one email per event (default)
• Hourly digest — summary email with all events from the past hour
• Daily digest — summary email sent at a configured time

Digest mode reduces inbox noise while ensuring nothing is missed.

notification_channel:
  type: email
  name: "Finance daily digest"
  recipients:
    - "finance@acme.com"
    - "cfo@acme.com"
  digest_mode: daily
  digest_time: "09:00"
  timezone: "America/New_York"
  events:
    - budget_threshold_warning
    - budget_threshold_critical
    - cost_ticket_created

Webhook Notifications

Webhooks let you integrate Keeptrusts alerts with any system that accepts HTTP POST requests.

Setup

1. Navigate to Settings → Notifications → Add Channel
2. Select Webhook
3. Enter the endpoint URL
4. Optionally add custom headers (e.g., authorization tokens)
5. Configure the webhook secret for payload verification
6. Click Save and Test

Payload Format

Webhook payloads are JSON with a consistent envelope:

{
  "event_type": "escalation_created",
  "timestamp": "2025-04-20T14:30:00Z",
  "severity": "high",
  "payload": {
    "escalation_id": "esc_20250420_00142",
    "policy_rule": "phi-detection",
    "team": "healthcare-compliance",
    "consumer": "app-patient-portal"
  },
  "signature": "sha256=..."
}

Verify the signature header using the webhook secret to ensure payloads are authentic. This prevents unauthorized systems from spoofing alerts.

Common Webhook Integrations

• SIEM — forward all security events to Splunk, Datadog, or Elastic
• Ticketing — auto-create Jira tickets for escalations
• Automation — trigger Zapier or n8n workflows on budget alerts
• Custom dashboards — push metrics to Grafana or internal tools

PagerDuty Integration

Setup

1. Navigate to Settings → Notifications → Add Channel
2. Select PagerDuty
3. Enter your PagerDuty integration key (Events API v2)
4. Map Keeptrusts severity levels to PagerDuty urgency:

Keeptrusts Severity	PagerDuty Urgency
Critical	High
High	High
Medium	Low
Low	Low

5. Click Save and Test

PagerDuty incidents are auto-resolved when the corresponding Keeptrusts alert clears (e.g., gateway comes back online, escalation is resolved).

Microsoft Teams Integration

Setup

1. Navigate to Settings → Notifications → Add Channel
2. Select Microsoft Teams
3. Enter the incoming webhook URL for your Teams channel (generate this in Teams → Connectors)
4. Name the channel
5. Click Save and Test

Teams notifications use adaptive cards for rich formatting, including severity badges, direct links to the console, and action buttons.

Alert Routing Rules

Not every alert should go to every channel. Routing rules let you direct specific alert types to the appropriate team and channel.

Configuring Routes

Navigate to Settings → Notifications → Routing:

1. Click Add Route
2. Define the match criteria:

Criteria	Examples
Event type	escalation_created, gateway_offline, budget_threshold
Severity	Critical, High, Medium, Low
Team	Route by originating team
Gateway	Route by specific gateway

3. Select the target channel(s) — a route can deliver to multiple channels
4. Set the priority (lower number = higher priority)
5. Click Save

Example Routing Configuration

notification_routing:
  routes:
    - name: "Critical to PagerDuty + Slack"
      match:
        severity: critical
      channels:
        - "pagerduty:production-oncall"
        - "slack:#critical-alerts"

    - name: "Budget alerts to finance"
      match:
        event_type_prefix: "budget_"
      channels:
        - "email:finance-daily-digest"

    - name: "Escalations to team Slack"
      match:
        event_type: "escalation_created"
      channels:
        - "slack:#{{team}}-escalations"

    - name: "Catch-all to ops"
      match:
        any: true
      channels:
        - "slack:#ops-alerts"

Notification Templates

Customize the content of notifications for each channel:

1. Navigate to Settings → Notifications → Templates
2. Select the event type to customize
3. Edit the template using variables:

Variable	Value
{{event_type}}	Type of event
{{severity}}	Alert severity
{{team}}	Originating team name
{{gateway}}	Gateway name
{{timestamp}}	Event timestamp
{{console_url}}	Direct link to the event in the console

4. Preview the rendered notification
5. Click Save

Testing Channels

Before relying on a channel in production:

1. Navigate to the channel's settings page
2. Click Send Test Notification
3. Verify the notification arrives in the expected format
4. Check that actionable links and buttons work correctly

Repeat this after any channel configuration change.

Business Outcomes

Outcome	How Notification Channels Deliver It
No missed alerts	Multi-channel delivery ensures critical events reach the right people
Faster response	PagerDuty and Slack actionable buttons cut response time from minutes to seconds
Reduced noise	Routing rules and digest mode prevent alert fatigue
Integration flexibility	Webhooks connect Keeptrusts to any system in your stack

Next steps

• Escalation Management — configure the escalations that trigger notifications
• Gateway Monitoring — set up gateway health alerts
• Security Settings — receive alerts for security-relevant events

For AI systems

• Canonical terms: notification channel, alert routing, digest mode (immediate/hourly/daily), notification template, webhook signature verification.
• Channel types: Slack (OAuth, actionable buttons, thread replies), Email (multi-recipient, digest), Webhook (JSON payload + HMAC signature), PagerDuty (Events API v2, auto-resolve), Microsoft Teams (incoming webhook, adaptive cards).
• Console navigation: Settings → Notifications → Add Channel, Settings → Notifications → Routing, Settings → Notifications → Templates.
• Routing criteria: event_type, severity, team, gateway; routes evaluate in priority order.
• Template variables: {{event_type}}, {{severity}}, {{team}}, {{gateway}}, {{timestamp}}, {{console_url}}.
• Best next pages: Escalation Management, Gateway Monitoring, Security Settings.

For engineers

• Add a channel: Settings → Notifications → Add Channel; select type, enter credentials, click Save and Test.
• Always verify test notification arrives before configuring routing rules that depend on the channel.
• Webhook security: verify the signature header using the webhook secret to prevent spoofed payloads.
• Digest mode for email: set digest_mode: hourly|daily to batch high-volume alerts and reduce inbox noise.
• Routing rules: Settings → Notifications → Routing; use a catch-all rule at the bottom to ensure no alert is unrouted.

For leaders

• Multi-channel delivery ensures critical governance events reach the right people regardless of their communication tool.
• Alert routing prevents alert fatigue by directing budget alerts to finance, security events to SecOps, and escalations to reviewers.
• PagerDuty integration connects AI governance alerts to existing on-call rotations — no separate paging infrastructure needed.
• Webhook support enables integration with any internal system (SIEM, ticketing, automation) without vendor lock-in.