Skip to main content

Alert Connectors

Alert Connectors let you push platform alerts to external communication channels. When a quality check fails or a product alert fires, matching connectors automatically forward formatted messages to your Slack channels or Microsoft Teams.

Supported Platforms​

PlatformMessage FormatSetup Required
SlackBlock Kit messages with severity color barsIncoming Webhook URL
Microsoft TeamsAdaptive Cards with facts and action buttonsIncoming Webhook Connector

Getting Started​

1. Create a Webhook in Your Platform​

For Slack:

  1. Go to your Slack workspace's Apps settings.
  2. Search for and add Incoming Webhooks.
  3. Choose a channel and copy the webhook URL (starts with https://hooks.slack.com/services/...).

For Microsoft Teams:

  1. In your Teams channel, click the ⋯ menu → Connectors.
  2. Search for Incoming Webhook and click Configure.
  3. Give it a name and copy the webhook URL.

2. Add a Connector in Qarion​

  1. Navigate to Settings → Alert Connectors.
  2. Click Add Connector.
  3. Choose the platform (Slack or Teams).
  4. Paste your webhook URL.
  5. Select the severity levels you want to receive (e.g., High and Critical only).
  6. Click Create Connector.

3. Test the Connection​

Click the ⚡ Test button next to your connector. A sample alert message will be sent to your channel. If it arrives, you're all set.

Configuring Severity Filters​

Each connector has a severity filter that controls which alerts are forwarded:

SeverityColorRecommended Use
CriticalPurpleImmediate business impact, send to all channels
HighRedImportant failures, send to team channels
MediumOrangeReview-worthy issues, optional forwarding
LowBlueInformational, typically filtered out

By default, new connectors forward High and Critical alerts. You can adjust this at any time by editing the connector.

Managing Connectors​

Enabling and Disabling​

Use the toggle button next to each connector to temporarily disable it without deleting the configuration. Disabled connectors do not receive any alerts.

Editing​

Click the pencil icon to update the connector's name, webhook URL, or severity filters. The connector type (Slack/Teams) cannot be changed after creation — create a new connector instead.

Deleting​

Click the trash icon to permanently remove a connector. This action cannot be undone.

What Gets Forwarded​

Alert messages include:

  • Title and description of the alert
  • Severity level with color coding
  • Space name for context
  • Alert type (quality, product, smart)
  • Product name when applicable
  • View in Qarion button linking directly to the alert

Troubleshooting​

Test message not arriving​

  • Verify the webhook URL is correct and starts with https://.
  • Check that the webhook is still active in your Slack/Teams settings.
  • Ensure the target channel hasn't been archived or deleted.

Alerts not forwarding​

  • Confirm the connector is active (toggle is green).
  • Check the severity filter — the alert's severity must match one of the selected levels.
  • Verify the alert type matches the connector's type filter (if configured).

Webhook returns an error​

  • 403/401: The webhook token may have been revoked. Regenerate it in your platform.
  • 404: The webhook URL may be invalid or the channel was deleted.
  • Timeout: Network issues between Qarion and the external platform. Retry later.

Best Practices​

  • Separate channels by severity: Route critical alerts to a dedicated #incidents channel and lower severities to #data-quality.
  • Use descriptive names: Name connectors after their target channel (e.g., "Slack #data-alerts-prod") for easy identification.
  • Start with high/critical only: Avoid alert fatigue by forwarding only the most important alerts initially, then expand as needed.
  • Test after creating: Always use the test button to verify connectivity before relying on the connector.