What we do with it on our projects
We do not set Slack up, that is rarely our subject. We wire into it, and it is often the most profitable move in an automation project: making visible what until then happened in a log nobody opened.
The principle that decides everything
An alert you ignore serves no purpose, and it teaches you to ignore the next ones. So we send few, and only those needing human action. The rest goes into a consultable log, not into a notification.
What deserves an alert
An automation that fails and touches a client or an invoice. A quote request arriving from the site. A site that stops responding. A deadline approaching with nobody having acted. Those are events where somebody has to decide.
What does not
Jobs that succeed. Routine reports, which go into one grouped daily message rather than in real time. And anything calling for no action, which has no place in a channel.
Separating the channels
Automated flows in their own channels, never in those where the team talks. Without that separation, the alerts drown the conversations and end up muted, which cancels the whole benefit.
