Everyday productivity
Name a channel and a few words. Every morning Aestus reads the channel's last day and tells you each message that used one, with a link to it.
Everyday
Some channels are too busy to read and too important to ignore. A deal channel talks about everything, and you only need to know when someone mentions pricing. Today that means scrolling every morning, or a keyword alert that fires on every word that happens to contain yours.
This use case reads the channel for you. Name the channel and a few words. Every morning at 9:00 Aestus reads the channel's last day of messages, and the software finds each message that used one of your words, as a whole word, in any case. Bots, joins and topic changes are not counted.
For each message it found, you get one line: what the message is about, the sentence that used your word copied exactly, and a link that opens the message in Slack. The line is checked against the message before you see it, and a line whose quote is not in the message is refused.
On a quiet day nobody is told. The run still records what it read — the channel, how many messages people wrote, per hour, and that none used your words — so silence is a result you can check, not a guess. It reads history on a schedule, so it needs no Slack listening, and it posts nothing anywhere.
The artifact this use case produces, in the product view you would read it in.
Example — fictional team and data. Not a live run or customer result.
Worked example
documentProduced by: Run EXAMPLE-WS-01 · 41 messages read · 2 flagged · nothing posted · demo values
Each step is one node in the workflow graph the interpreter runs. Nothing here is a prompt chain hidden in a route handler.
Workflow steps
Pick a channel and up to ten words or short phrases, like "pricing" or "renewal date". Drop can set it up from one sentence: "tell me when anyone in #deal-northwind mentions pricing".
At 9:00 it reads the channel's last 24 hours through your organization's Slack connection. It reads history, so it needs no Slack listening.
Words are matched as whole words, in any case, by code: "price" does not match "priceless". Bots, joins and topic changes are not counted.
One line per message: what it is about, the sentence that used your word copied exactly, and a link to the message. Each line is checked against the message before you see it.
When nothing came up, nobody is told. The run still records what it read: the channel, how many messages people wrote, per hour, and that none used your words.
The same job, on either side.
By hand
Scrolling a busy channel every morning for one topic.
On Aestus
One list of the messages that used your words.
By hand
A keyword alert that fires on "priceless" and "pricey".
On Aestus
Whole words and phrases, matched by code.
By hand
Missing the one message that mattered in a hundred.
On Aestus
Every message that used a word, each with its link.
By hand
Asking an admin to switch on Slack listening.
On Aestus
It reads history on a schedule, so no listening is needed.
By hand
"Did anyone mention it yesterday?"
On Aestus
Each run records how many messages it read, even on a quiet day.
By hand
A summary that paraphrases what someone said.
On Aestus
The sentence is copied exactly, and a line whose quote is not in the message is refused.
Every run is auditable after the fact, which is what makes handing the job over survivable.
Cost, tokens, duration and a failure code if it failed, on the same ledger as every other run in the workspace.
The channel, the window, how many messages people wrote, per hour, and how many used a watched word — on every run, the quiet ones too.
It reads Slack and tells you. It posts nothing to Slack or email, so there is nothing to approve.
Only the tools this workflow actually uses. Each one has a setup guide.
No. It reads the channel's history on a schedule through your organization's Slack connection. Listening, which reacts to each message as it arrives, is a different permission and is not used.
Only when your organization's Slack connection lists that private channel as allowed. Otherwise the run stops and says why, rather than reading it or reporting nothing.
No. The step that reads the messages holds no tool at all, so an instruction in a message has nothing to act with. It is described like any other message.
Nobody is told. The run still records what it read, so you can see it checked: the channel, the number of messages, per hour, and that none used your words.
Sources