Discord

Monitoring alerts, straight into Discord.

Connect a Discord webhook once and any notify step can post to that channel. Popular with smaller teams and communities running their own infrastructure, where Discord is already the place everyone is.

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

Where the team already is

If your team coordinates in Discord, an alert there is seen faster than one in a tool nobody has open.

No cost to add

A channel webhook takes a minute to create and costs nothing, which makes it an easy first destination.

Good for community projects

Open source and community-run infrastructure often has Discord as its only shared space, and this fits that directly.

Pairs with something louder

Use Discord for awareness and add SMS or a phone call for the alerts that genuinely need to wake someone.

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

Create a webhook in the Discord channel settings, copy the URL, then add a Discord connection in the monitor editor sidebar and paste it in. Send test confirms it works before you depend on it.

Can I use more than one Discord channel?

Yes. Create a separate connection for each channel, each with its own webhook URL, and give them names that make the difference obvious when you pick one in a notify step.

Does it post as a bot?

It posts through the channel webhook you created, so the message appears from that webhook rather than from a bot account you have to invite and manage.

How do I stop a noisy monitor filling the channel?

Notify steps fire once per incident by default and have a flap cooldown of fifteen minutes. You can also raise the confirm down after setting on the monitor so brief failures never create an incident at all.