How to automate Slack alerts your team will not mute
An alert channel dies when it is noisy. How to automate Slack alerts that fire only on something new and above a line you set, at hours people work, in the right channel.
Part of the guide Location intelligence automation
To automate Slack alerts that stay useful, decide the one event worth interrupting someone for, set a line it must cross, make sure each event is only ever posted once, and send it to the channel of the people who act on it, only during the hours they work. Everything that does not meet that bar goes into a daily digest instead of an alert.
Most alert channels fail the same way: the first week is exciting, the second week is busy, and by the third week everyone has muted the channel. This article is for operations, sales and support leads who want alerts in Slack that people still read in month three. It covers what to alert on, how to set thresholds, how to stop repeats, a worked example and the mistakes that turn alerts into noise. The workflow automation guide covers the wider subject.
Alert, digest or nothing
Before building anything, sort what you might send into three piles.
- An alert is something one person should act on within hours: a road closure on a depot's exit road, a branch whose rating fell below a line, a key account hiring for a role you supply.
- A digest is useful but not urgent: new businesses in a city, rivals' new branches, this week's job postings. One message a day or a week, with the full list.
- Nothing is anything nobody would act on. If you cannot name who acts and what they do, do not send it.
The rule of thumb: if an alert fires more than a few times a day in one channel, part of it belongs in the digest.
Three settings that keep alerts quiet
A line to cross
An alert should fire on a condition, not on every item. A Filter block keeps only items that match one rule: a fit score of 80 or more, a rating under 4, rain over 10 mm, a road speed under a number. Put two filters in a row when an item must match both. Pick the line from what you would act on, then check a week of results to see how often it would have fired.
Only once per event
A flow that runs every hour finds the same road closure every hour until it clears. Without a memory, Slack gets the same post twelve times. The Only new block lets through only items the flow has not found before, so each closure, opening or posting is posted once. Put it right after the block that finds things.
Hours people work
A Schedule that runs every 15 minutes can be limited to certain days and to a window, such as 07:00 to 19:00, Monday to Friday, in your team's time zone. Outside those hours nothing runs, so nothing is posted at 3 a.m. When the window opens, the first run picks up what appeared overnight, and Only new still holds back anything already sent.
A worked example
This example is made up. A recruitment agency in Madrid places warehouse staff. Its consultants want to hear the same morning when a company starts hiring warehouse workers, but they were drowning in a feed of every posting.
- A Schedule runs every day at 07:30, Madrid time.
- Job postings finds warehouse jobs posted in Madrid in the last 24 hours.
- Remove duplicates keeps one posting per company, then Only new drops companies the flow has posted about before.
- An xMap LLM block scores each company from 0 to 100 as a client for the agency, with one sentence on why.
- Sort and limit keeps the ten highest scores, and the Slack step posts them to the recruiting channel.
That is the core of the template Daily hiring signals in Slack. The consultants get one message at 07:30 with ten companies, best first, each name linked. On a quiet day the list is short, which is itself worth knowing.
One message a run, or one per item
The Slack step can post once per run, with all the items in one message, or once per item. For alerts that someone acts on one by one, such as a rating that dropped at a named branch, one post per item lets people reply in that item's thread. For lists, one message is kinder to the channel. If you leave the message empty, the flow writes it for you: once per run, the flow's name, the date, the count and a list where each name links to its map, with the results attached as a CSV; once per item, one linked line.
To send the urgent part and the rest to different places, put a Branch before the end: items that match go one way, the rest another. The template New businesses routed by size sends established businesses to a key account team's Slack channel and the rest to a sheet.
Mistakes that get a channel muted
- No memory. Without Only new, frequent runs repeat themselves. This is the single biggest cause of muted channels.
- A line nobody chose. Alerting on every item just in case trains people to ignore the channel.
- One channel for everyone. The depot manager does not need sales leads. Send each alert to the channel of the people who act on it.
- Alerts at night. Limit frequent schedules to working hours, so the morning starts with what came in overnight, once.
- No owner. Every alert type should have a person who acts on it. If nobody does, demote it to the digest.
To set the Slack step up, sign in with Slack once and pick the channel; see xMap Flows in Slack. For a branch whose rating drops, Alert when a branch's rating drops is a ready-made start.
Questions
How do I stop the same alert being posted twice?
Put Only new right after the block that finds things. It lets through only items the flow has not found before, so each event is posted once.
Can alerts only go out during working hours?
Yes. A Schedule that runs every 5, 15 or 30 minutes or every hour can be limited to some days and to a window between two times, in your time zone.
Do I have to write the Slack message?
No. Leave it empty and the flow writes one: the flow's name, the date, a linked list and a CSV of the results for one message a run, or one linked line per item.
Can urgent items go to Slack and the rest by email?
Yes. A Branch splits the items by a rule, and each side ends in its own step, such as Slack for one and Email for the other.
Templates that do this
Read next
More on business and places data · Every article · Templates