Microsoft Teams

Alerts in Teams, without leaving the Microsoft stack.

Connect an incoming webhook once and any notify step can post to that Teams channel. For organisations already standardised on Microsoft, this puts alerts where people are working rather than in yet another tool to check.

Set up once, use anywhere. The connection belongs to the account, so every monitor and every flow can point at it without a second setup.
Test before you trust it. Send test fires a real message, so a bad URL or token is found now rather than during an outage.
Encrypted at rest. Tokens and credentials you enter are encrypted at rest.

Start free All features

01 · Using it well

What Microsoft Teams is good for.

Already approved

In organisations where adding a new tool means a procurement conversation, routing to Teams avoids one entirely.

Reaches beyond engineering

Support and operations staff who live in Teams see the alert without needing access to your monitoring dashboard.

Channel per service

Separate connections for separate channels let you route each service to the group that owns it.

First tier of an escalation

Post to Teams immediately, wait, then page an individual if the outage is still running.

02 · Controls

How often it fires.

The connection decides where an alert goes. These settings decide how often it goes there.

Once per incident

The default. The step fires once and resets on recovery, so a long outage does not turn into a wall of messages.

Or on every check

Switch the step to fire on every matching check when you want a continuous signal instead of a single alert.

Flap cooldown

Fifteen minutes by default, so a monitor bouncing down and up will not re-send inside that window.

Message placeholders

Write the message with placeholders such as flow, state, detail and duration so the alert carries context.

Behind a schedule gate

Put the step behind set hours and days if it is informational, and leave the critical path ungated.

Repeat until resolved

Add a Repeat alert block before the step to keep sending on an interval while the monitor stays down.

Questions

Common questions

How do I connect Microsoft Teams to Hesklo?

Add an incoming webhook connector to the Teams channel you want alerts in, copy the URL, then create a Microsoft Teams connection in the monitor editor sidebar and paste it. Send test confirms delivery.

Can different services alert different Teams channels?

Yes. Create one connection per channel and pick the right one in each notify step. Because flows belong to individual monitors, each service can route to the team that owns it.

Does this need an admin to install anything?

It uses an incoming webhook on the channel rather than an installed application. Depending on your organisation's settings, creating that webhook may still require the appropriate permissions in Teams.

Can I control how often it posts?

Yes. Each notify step fires once per incident by default, has a flap cooldown of fifteen minutes, and can optionally be set to fire on every check instead.