Calling a role

An alert nobody sees doesn’t help. That’s why a webhook can call a role, but the role is chosen by the person who sets up the webhook in the app, never by the payload.

How to set it up

Under Integrations, in Who to call when an alert fires, pick a role. The default is “No one”. Whoever sets it up has to be allowed to mention that role: the same rule as typing @role in chat.

When it calls

The role is called only when both of these are true:

1. The message is new, not an update to an existing card.
2. The card’s state is alert.

So an incident calls once, when it fires. Updates to the same card (another firing, “warning”, “resolved”) don’t call again. If the alert comes back after being resolved, that’s a new message and it calls again: see Card and key.

The card shows who was called, and the role stays the same across updates.

Muting a channel and each person’s notification preferences still apply: whoever muted it isn’t bothered.

What a payload can’t do

No body can ping people. @everyone, @here, <@id>, <@&id> and GGspeak’s mention tokens (like <@aqui>) are escaped and become plain text before they’re stored, in every format.

If the link leaks

A leaked link can’t ping the whole community: at worst it calls the webhook’s one role, and the send rate caps the damage (Limits). New link cuts access immediately.