Teams alerts: post Pingsured alerts to a Teams channel
Pingsured can post an alert to a Microsoft Teams channel or chat when a ping starts failing, when it recovers and when its certificate is replaced. It is a webhook that speaks Teams: you give Pingsured the URL of a Teams workflow, and every alert arrives as a card in that channel or chat. Teams alerts are available on the same plans as webhooks, every paid plan. An account owner or manager sets them up, either for one ping or as the default for every ping in the account.
What you need
- A Microsoft 365 account that may create workflows in Teams. Your administrator can switch the Workflows app off.
- The channel or chat the alerts should go to. One workflow posts to one of them; to alert a second, create a second workflow.
Create the workflow in Teams
Microsoft retired the old connector-based "Incoming Webhook" in Teams in May 2026. A webhook in Teams is now a workflow, and that is what Pingsured posts to.
- In Teams open the Workflows app and choose the template Post to a channel when a webhook request is received, or the one for a chat.
- Name it, for example Pingsured, and pick the team and channel, or the chat, it should post to.
- When it is created, copy the webhook URL it shows. It is long and ends in a signature,
sig=….
Microsoft changes the names of its menus and templates now and then. What Pingsured needs is the URL of a workflow that starts when a webhook request is received.
Treat the URL as a secret: whoever has it can post to that channel. Pingsured shows it in full only to owners and managers. A workflow belongs to the person who created it, and stops working if they leave the company and nobody else owns it, so add a co-owner to it.
Add it in Pingsured
- For every ping, open Settings → Notifications, go to Integrations under Default notifications and choose the Teams card.
- For one ping, open the ping, go to its Notifications section, choose Add subscription and pick Teams.
Paste the webhook URL, all of it, signature included. Pingsured accepts only the addresses Teams workflows have (they end in .logic.azure.com or .api.powerplatform.com), so a URL from another service, or one cut off before its signature, is refused when you save it. Then choose the triggers. The recommended set is First error and First ok, with Certificate changed if you check certificates: you hear when something breaks and when it is fixed.
Choose Send test next to the channel to post a message marked as a test. It is the quickest way to find out that the URL and the channel are right before an alert depends on them.
What a message looks like
- A card with a headline made of the ping's name and a dot that shows its state: red when it is failing, yellow when it is degraded, green when it has recovered.
- The reason, when there is one: the HTTP status, the error, or why a content check failed.
- Where it was seen: either the location, such as
From de, or, for a ping checked from several, which of them are failing, such asFailing from de, sg (2 of 3 locations). - A button, View ping in Pingsured, that opens the ping.
A certificate change reads Certificate changed on the ping, or Unexpected certificate on it when something about the change is not what a renewal looks like, with the reasons beneath.
The language of the messages
Messages are written in the account's notification language, which an owner sets under Settings → Account. The messages come in English, German, Spanish, French and Italian. Until it is set they are in English. The same setting is the fallback language for alert emails to members who have not chosen one of their own. The reason line is shown as the checked service reported it, in whatever language that was.
When messages are sent
A Teams channel follows the same rules as every other alert channel: which changes, how many failures first, how often and from where are described in the notifications page. A change of status is always sent at once, and repeat alerts for the same ping and channel are held back for 15 minutes.
If a message does not arrive
Teams normally acknowledges a request before the workflow has run, so Pingsured shows a delivery as sent once Teams has accepted it. A workflow that fails after that, because it was switched off, its owner left or the channel was deleted, shows in the workflow's run history in the Workflows app and not in Pingsured.
When Teams cannot be reached, holds the request back (it allows only a few a second) or answers with an error that may pass, the delivery is retried, 5 attempts in all, 30 seconds, 5 minutes, 30 minutes and 2 hours apart. Any other answer is final, and Pingsured shows what Teams said when you hover over the status badge next to the channel in Settings → Notifications. The fix is usually a new workflow: create one in Teams, add it in Pingsured and remove the old one.
Limits
- Teams channels count with webhooks toward the same limits: 50 account-wide and 20 on one ping.
- Messages are posted by the Workflows app, not under a name and icon of your choosing. Mentions, direct messages and threads are not available yet.