Slack

Alerts in the channel your team already has open.

Connect a Slack incoming webhook once and any notify step in any flow can post to it. Most teams start here, and most teams stay here, because the alert lands where the conversation about it is going to happen anyway.

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 Slack is good for.

Everyone sees it

A channel alert reaches the whole team at once, which is what you want for awareness even when only one person will act.

The context stays together

The alert and the conversation about it end up in the same place, so nobody has to reconstruct what happened from three tools.

Good for the first tier

Post to Slack immediately, then escalate to something louder if the outage is still going a few minutes later.

Separate channels by severity

Point routine notices at a general channel and real outages at a dedicated incident channel, decided per flow.

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 Slack to Hesklo?

Create an incoming webhook in Slack for the channel you want, then add a Slack connection in the monitor editor sidebar and paste the URL. Use Send test to confirm it works. After that any notify step in any flow can point at it.

Can I send different alerts to different Slack channels?

Yes. Create one connection per channel, each with its own incoming webhook URL and a name that tells them apart. A flow can then route routine notices to one channel and genuine outages to another.

Will a flapping service spam my channel?

No. Every notify step has a flap cooldown, fifteen minutes by default, so a monitor bouncing down and up will not re-send inside that window. Steps also fire once per incident by default rather than on every check.

Can I customise the message?

Yes. The notify step lets you write the message, with placeholders such as flow, state, detail and duration so the alert carries real context rather than just a monitor name.