Alert Connectors

Alert connectors let you route Qarion notifications to your team's existing communication channels — Slack, Microsoft Teams, or email — so critical events reach the right people without requiring them to check the Qarion UI.

Supported Channels

Channel	Message Format	Configuration
Slack	Block Kit messages	Webhook URL
Microsoft Teams	Adaptive Cards	Webhook URL
Email	HTML templates	SMTP or SendGrid

Setting Up a Connector

1. Navigate to Settings → Alert Connectors in your space
2. Click Add Connector
3. Select the channel type (Slack, Teams, or Email)
4. Provide the required configuration:
   • Slack — Paste the incoming webhook URL from your Slack app
   • Teams — Paste the incoming webhook URL from your Teams channel
   • Email — Configure SMTP settings or SendGrid API key
5. Configure routing rules to determine which alerts go to this channel

Routing Rules

Each connector supports routing rules that filter which alerts are forwarded:

• Severity — Only send Critical alerts, or include Warning and Info
• Space — Scope to specific spaces or all spaces
• Alert Type — Quality failures, anomaly detections, governance events

For example, you might route only Critical quality failures to a #data-alerts Slack channel, while sending all governance events to a team email distribution list.

Message Formatting

Qarion formats messages natively for each channel:

• Slack — Rich Block Kit messages with severity badges, product links, and action buttons
• Teams — Adaptive Cards with similar rich formatting
• Email — HTML email templates with embedded links back to Qarion

Instance-Level Configuration

For multi-instance deployments, alert connectors can be configured at the instance level, allowing each tenant to have their own notification channels.

tip

Test your connector after setup by triggering a manual test alert from the connector configuration page.