How to Automate Slack

Slack is where the company keeps its attention

Slack is a messaging app that turned into something else along the way: the place a company keeps its attention. Decisions get made in a thread before they are written down anywhere official. The person who needs to know something asks in a channel rather than opening the system that holds the answer. New staff learn how the business actually works by scrolling.

Most companies run a few dozen channels and about four that matter. The one where orders come in. The one where things break. The one where the numbers get posted every morning. Those few are checked constantly, by people who are supposed to be doing something else.

That is both the value and the cost. Everything important passes through Slack, which is what makes it worth automating. Everything unimportant passes through too, which is why half the workspace has notifications off.

Someone is quietly paid to watch the dashboards

In most teams one person has become the human integration layer, without anyone deciding they should be.

They open the payment dashboard each morning and post yesterday's total. They check whether the overnight job finished and tell the channel either way. They copy the day's bookings across because the booking system has no Slack app. When somebody asks whether an order shipped, they open another tab and look.

None of that is in their job description. It is what happens when the tool everyone watches knows nothing about the tools that hold the facts. The channel is full of people and short of data.

Slack

Morning numbers Yesterday's takings, failures and bookings read from the systems that hold them and posted before the team logs on.

The usual questions, answered Whether it shipped, whether it cleared, whether the status changed, checked and posted without anyone opening a tab.

Exceptions only The three lines that fell below reorder, not the two hundred that did not. Quiet channels are the ones people still read.

Workflow Builder only reacts to what happens inside Slack

Slack automates a fair amount on its own, and for what it covers it is good.

Workflow Builder runs a sequence when someone joins a channel, reacts with an emoji, submits a form or clicks a button. Reminders repeat on a schedule. Scheduled send posts a message you already wrote at a time you pick. Hundreds of products publish a Slack app that pushes their own events into a channel.

Every one of those is triggered by something that happened in Slack, or pushed in by a vendor who decided to build the integration. That is the ceiling. A workflow cannot go and look at anything. It posts what it is handed.

So the gap is every tool that never built a Slack app: the supplier portal, the council website, the twenty-year-old booking system, the bank. Those hold the answers people ask for in channels all day, and Slack has no way to reach them.

The channel can report before anyone asks

Change what is able to reach the channel and the whole thing inverts. Instead of people asking the channel questions, the channel starts answering them first.

Yesterday's takings, posted at seven, read from the till system that only ever shows them on a dashboard. The overnight payment failures, listed by customer, out of a portal with no export. The three stock lines that dropped below reorder, checked across every supplier you buy from. The bookings that came in during the night from a system that never built an integration.

The same goes for the questions people ask over and over. Whether a shipment moved. Whether a permit changed status. Whether a listing is still on the first page. Whether a competitor put their price up again. Each of those is somebody opening a tab, looking, and typing what they saw.

One thing worth building in from the start: a channel that posts everything gets muted inside a week, and a muted channel is worse than no channel. The version that survives posts what changed and stays quiet otherwise. Report the exception, not the heartbeat.

Nobody has to be watching at six in the morning

The till system will not post its own number into a channel, and the number is wanted before the doors open. Reading it off a screen at that hour is work, but it is not the kind that justifies a phone by the bed.

WebRun is an AI agent that works a real Chrome browser, signed in as you. It opens the portal or the dashboard, reads what is on the screen, and posts the result into the channel you choose. Because it works the browser rather than an API, it reaches the tools that never built a Slack app, which is most of them.

It runs on your schedule in your own private environment, and you can watch a run and stop it. Anything that would reach a customer drafts and waits for you.

The workflows below are already built, and each one names the apps it touches.