Microsoft Teams alerts from AlertHub (Incoming Webhooks)

If the company already standardized on Microsoft Teams, Slack-shaped tools never get opened. The usual fix is a Power Automate flow per SaaS, or an Incoming Webhook pasted into every vendor.

AlertHub sits in the middle. Sources (Stripe, Shopify, GitHub Actions, email, n8n) POST once. Teams receives a Message Card with project, level, title, and description. AlertHub detects the Teams webhook URL automatically.

How Teams delivery works

You add an Incoming Webhook connector on the target channel.
You paste the URL in AlertHub Connections → Webhooks.
Warning/critical alerts become cards (themeColor red for critical, orange for warning).
Info stays in the dashboard so #ops is not a firehose.

Microsoft has moved some tenants from classic Connectors toward Workflows. If Incoming Webhook is hidden, create a Workflow that accepts an HTTP POST and still paste that URL only if it expects a JSON body AlertHub can send — the documented path remains the Incoming Webhook connector described in our Teams docs.

Setup (once)

Create a project at app.thealerthub.com.
In Teams, open the channel → … → Connectors → Incoming Webhook → name it AlertHub → Create → copy the URL.
In AlertHub, Connections → Webhooks → paste and save.

Then connect any source.

Alert 1: Payment and billing in a finance channel

Failed charges should not wait in Stripe email. Point native Stripe webhooks at AlertHub (failed payment guide) and let Teams be one destination next to Telegram for the on-call founder.

Alert 2: CI and deploys in `#engineering`

GitHub Actions failures and Vercel deploys already POST to api.thealerthub.com/sendAlert. Adding Teams is a URL in Connections — no workflow YAML change.

Alert 3: Same project, Slack + Teams during a migration

While a department still uses Slack, keep both destinations on the project. Remove Slack when the move is done. Sources never learned a Teams URL.

Ideas to squeeze more value

Channel per concern. Two AlertHub projects (or two Teams webhooks on two projects) beat one overloaded #general.
Do not put customer PII in titles. Teams is often more widely readable than a private Telegram chat.
WhatsApp for after-hours, Teams for business hours. Quotas apply to WhatsApp on Pro; Teams is a webhook destination.
Google Chat shops. Same pattern: Google Chat alerts.

FAQ

Is this Adaptive Cards or MessageCard?
AlertHub posts a MessageCard payload (@type: MessageCard) that Teams Incoming Webhooks render as a card.

Can members add the webhook?
Treat the URL like a secret. Project admins should paste it. Rotate it in Teams if it leaks; then update AlertHub once.

Will info-level cron heartbeats appear in Teams?
No. Raise them to warning only if someone must act.

Next steps

Follow the Microsoft Teams destination guide, send a test warning from the Ingestion API, and leave Slack connected until the team has moved.