Microsoft Teams alert channel
PulseStack is a native Microsoft Teams alert channel. Every failure and recovery arrives as a formatted card in the channel your team already lives in, so incidents get seen and actioned without anyone opening a dashboard.
Native Teams channel via incoming webhook. Works on every paid plan. 14-day trial, no card on Free.
Monitor down
api.acme.co returned HTTP 503
Recovered
api.acme.co is back to HTTP 200 after 4m 12s
8
native alert channels
8
monitor types to Teams
30s
fastest check interval
2
events: failure and recovery
Email alerts get buried and dashboards only help the person looking at them. Microsoft Teams is where most organisations coordinate day to day, so that is exactly where an outage should surface. PulseStack posts a clear, structured card the moment a monitor breaches its threshold, and posts again the instant it recovers.
The whole channel sees the same card at once. No forwarding, no chasing, no waiting for someone to refresh a dashboard.
Monitor name, status code, check locations, failure count and timing are all in the card, so triage starts immediately.
Consecutive-failure thresholds mean a single flaky check never spams the channel. You decide how sure PulseStack must be.
The whole setup uses a standard Teams incoming webhook and takes a couple of minutes. No custom app, no code.
In the Teams channel you want alerts in, open Connectors, choose Incoming Webhook, give it a name such as PulseStack, and copy the generated URL.
Open Alert Channels, pick Microsoft Teams, paste the webhook URL and give it a clear label so you know which Teams channel it targets.
Attach the Teams channel to any of your monitors and set the consecutive-failure threshold that decides when a card should be sent.
Fire a test alert to confirm the card lands in the right channel. From then on failures and recoveries post automatically.
PulseStack cards are built to answer the first questions of any incident before anyone has to ask them. Each alert is self-contained.
{
"@type": "MessageCard",
"@context": "https://schema.org/extensions",
"themeColor": "F87171",
"summary": "Acme API is DOWN",
"title": "Monitor down: Acme API",
"sections": [{
"activityTitle": "api.acme.co returned HTTP 503",
"facts": [
{ "name": "Monitor", "value": "Acme API / HTTP" },
{ "name": "Locations", "value": "London, Frankfurt, Virginia" },
{ "name": "Failed checks", "value": "3 consecutive" },
{ "name": "Since", "value": "09:41 BST" }
]
}],
"potentialAction": [{
"@type": "OpenUri",
"name": "View incident",
"targets": [
{ "os": "default", "uri": "https://app.pulsestack.io/i/8f2a" }
]
}]
}Microsoft Teams is one of eight channels built into PulseStack. Mix and match them per monitor. Zapier and Google Chat are not native but connect through the Webhook channel.
SMS and voice are an add-on available on the Team and Enterprise plans.
Any check that can fail can post to your Teams channel. Build the coverage you need across web, network and infrastructure.
Status codes, response time and content checks on any URL.
Confirm a page contains, or is missing, specific text.
Reachability checks against any host and network path.
Verify a specific TCP port is open and accepting connections.
Multi-step requests with headers, body and JSON assertions.
Watch cron jobs and workers that must check in on schedule.
Track records and catch unexpected DNS changes or hijacks.
Advance warning before a domain registration lapses.
Route production HTTP and API monitors to the on-call channel with a low failure threshold so incidents surface fast and get owned.
TCP Ping, Port and DNS monitors post to the infra channel, catching reachability and record changes before customers notice.
SSL and Domain Expiry warnings land in Teams weeks ahead, giving admins time to renew without a last-minute scramble.
Heartbeat monitors watch cron jobs and workers, alerting the channel the moment a scheduled task fails to check in.
One Teams channel per client keeps every account's alerts separated and easy to hand to the right responder.
Keyword monitors flag broken pages or missing text, so the team hears about a botched deploy in the same channel they plan in.
The Microsoft Teams channel unlocks from the very first paid tier. Pick the plan that matches how many monitors you run.
£0
5 monitors, HTTP only, no chat channels
£15/mo
10 monitors, all types and channels
£39/mo
50 monitors, SSL and DNS insights
£79/mo
100 monitors, server diagnostics, 3 seats
£149/mo
200 monitors, 30s checks, 5 seats
Every paid plan includes a 14-day trial. Free requires no card.
Yes. Microsoft Teams is one of PulseStack's eight native alert channels, alongside Email, SMS, Slack, Discord, PagerDuty, Telegram and Webhooks. You connect it with a Teams incoming webhook, so there is no separate app to install.
Each alert is posted to your chosen Teams channel as a MessageCard through the channel's incoming webhook. The card shows the affected monitor and whether the event is a failure or a recovery, so the right people see it where they already work.
Create an incoming webhook on the Teams channel you want alerts in, copy the webhook URL, then add a Microsoft Teams alert in PulseStack and paste the URL. Choose whether to notify on failure, recovery or both, and you are live.
Alerts fire on failure and again on recovery. To cut noise, PulseStack only sends after a configurable number of consecutive failed checks, so a single blip will not wake the whole channel.
All of them. Every PulseStack monitor can route to Teams, covering the six core types - HTTP, Keyword, TCP Ping, Port, API and Heartbeat - plus DNS and Domain Expiry monitors.
Yes. Add a separate Microsoft Teams alert for each channel's incoming webhook, then assign the monitors you want to each one. Infrastructure alerts can go to your ops channel while marketing sites post elsewhere.
Set up the native Teams channel in minutes and let every failure and recovery post straight to the channel your team already watches.