Notification Channels: Email, Teams, and Webhooks

Alert rules are only as effective as the delivery mechanism behind them. An alert that fires but goes unnoticed is functionally the same as no alert at all. For many IT teams and MSPs, email alone is not sufficient for reliable alert delivery. Inboxes are crowded, notifications get buried, and critical alerts compete with routine messages for attention. Govex addresses this by supporting three distinct notification channels, so you can route alerts to wherever your team is most likely to see and act on them.

The first channel type is SMTP email, which remains the right choice for many workflows. Email notifications include a formatted summary of the triggered alert, the affected tenant, the number of matching devices or records, and a direct link back to the Govex dashboard for further investigation. Email works well for stakeholders who are not in Teams channels or for compliance-oriented notifications where an email trail is preferred. Govex supports configurable SMTP settings, so you can use your organization's existing mail infrastructure or a dedicated transactional email service.

Microsoft Teams integration uses incoming webhooks to post alerts directly into a Teams channel. Each notification is delivered as an adaptive card that includes the alert name, severity, a summary of the triggered condition, and the count of affected resources. Adaptive cards are structured and visually distinct from regular chat messages, which means they stand out in a busy channel. For MSPs whose operations teams live in Teams throughout the day, this channel type ensures that alerts are visible immediately without requiring anyone to check a separate tool or inbox.

The third channel type is generic webhooks, which open up integration possibilities beyond email and Teams. A generic webhook sends a JSON payload to any HTTP endpoint you specify when an alert fires. This makes it straightforward to connect Govex alerts to ticketing systems like ServiceNow or Jira, automation platforms like Power Automate or Zapier, or custom internal tools. The webhook payload includes all relevant alert metadata, so the receiving system has enough context to create a ticket, trigger a workflow, or log the event without additional API calls back to Govex.

A single alert rule can notify multiple channels simultaneously. For example, you might configure a compliance drift alert to post in a Teams channel for immediate visibility while also sending an email to the client's IT contact and firing a webhook to create a ticket in your PSA tool. Every channel supports a test feature that sends a sample notification so you can verify connectivity and formatting before relying on it for production alerts. Channels are configured from the Settings page in the Govex dashboard, and once created, they are available for selection in any alert rule across all tenants.