Notification targets
A target is a named group of delivery channels. Notification rules point at targets, not at channels, so you can change where a team is reached without touching your rules.
Signup creates one for you, named after the local part of your address, cut at the first +, and holding an email channel addressed to it.
You need the operator or owner role.
Channels
Section titled “Channels”Each channel is one of four types.
| Type | What you provide | Where it comes from |
|---|---|---|
| Up to 20 addresses | Press Enter or comma between them | |
| Slack | An incoming webhook URL on hooks.slack.com |
Slack app settings, Incoming Webhooks |
| Microsoft Teams | A Workflows URL on api.powerplatform.com or logic.azure.com, or their US Government equivalents on api.powerplatform.us and logic.azure.us |
The Workflows app. Microsoft’s old Incoming Webhook connector is retired |
| Discord | A webhook URL on discord.com |
Server Settings → Integrations → Webhooks → Copy Webhook URL |
NoCert checks the host before saving, so a URL from the wrong place is refused rather than silently failing later.
Teams is the one that catches people out. Classic connector URLs on *.webhook.office.com are rejected, because Microsoft retired them. Create a flow in the Workflows app and use the URL it gives you.
Add a target
Section titled “Add a target”Open Notification Targets and create one. Name it after who reads it, Platform on-call rather than Slack, since the whole point is that the channel can change later.
Add the channels, then use the test button on each webhook channel. A test posts a sample message straight to that channel, which is the only way to find out you pasted a webhook for the wrong room. Email channels have no test button.
Point a rule at the target from Notification rules.
A target that a rule points at cannot be deleted, escalation targets included. Repoint the rule first.
Channel health
Section titled “Channel health”Each channel carries the outcome of its last real delivery, so you can tell a channel that has never been used from one that is failing.
| State | Meaning |
|---|---|
| Production delivering | The last real alert went through. |
| Production failing | The last real alert failed. |
| No production alerts | Nothing but tests has gone through this channel. Test sends deliberately leave the state alone. |
| Disabled | The channel is switched off and replaces its health state entirely. |
The targets list rolls those up per target, so a target whose channels disagree shows Partially delivering.
A failing channel does not block the others on the same target. Nor is a failed alert retried: the certificate that triggered it comes back on its normal cadence, which can be a week away.
Anyone who can read a target can read its webhooks
Section titled “Anyone who can read a target can read its webhooks”Webhook URLs are shown in full when you reopen a target, and a webhook URL is a credential: whoever holds it can post into that channel.
Every operator in your organization can read them. If that matters to you, keep the sensitive channels on their own target and think of the URL as shared with your operators.
Rotate a webhook from the provider’s side, then paste the new URL here. NoCert has no way to invalidate one for you.