Work goes outNotification
Slack
Tells the right channel when something needs a person — a breach about to happen, an approval waiting, a verification that came back negative. Not a firehose of every new finding.
What the connector does
- SLA warnings and breaches, closure approvals, and escalations
- Routed per team, so a channel hears about its own estate
- Queued and retried like every other outbound delivery
- Deliberately not: a message per ingested finding
Credential required
An incoming webhook URL for the channel you want. It is stored encrypted, because the URL is the credential.
What this connector is for
A notification that fires on everything is a notification everybody mutes, and a muted channel is worse than none — it looks like coverage. So this connector is scoped to the moments where a person has to do something: a deadline about to pass, an approval waiting on a name, a fix that did not verify.
What is delivered
SLA warnings before a breach and notices after one; closure proposals waiting for approval; escalations when a deadline passes without movement. Each message carries enough to decide whether to act now and a link for everything else — a Slack message is a prompt, not a report.
What is deliberately not delivered
A message per new finding. Ingest volume belongs in the queue and on the dashboard, and putting it in a channel is how the channel stops being read before the first real escalation arrives.
What you have to grant
An incoming webhook URL. It is treated as a secret rather than as configuration, because anybody holding it can post to the channel — so it is stored encrypted, alongside every other integration credential, and never returned by any endpoint after it is saved.