On a schedule
Post the most-reacted Slack messages of the week
Every Friday, the five messages with the most emoji reactions in a Slack channel are posted back to that channel with links.
- Runs
- On a schedule
- Apps
- Slack
- AI
- Not needed
- Access
- channels:history, groups:history, reactions:read, chat:write
Send this to your assistant
Create a ClickRuntime automation: every Friday at 4pm, find the 5 messages in #general from the past 7 days with the most emoji reactions and post them with author, reaction count and link.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A busy channel buries the announcements and wins that people cared about most. By Friday, half the team has not seen the message that got thirty reactions on Tuesday.
Every Friday this automation reads the past week of messages in a channel, ranks them by total emoji reactions and posts the top five back to the channel, each with the author, the top reactions, a short excerpt and a link to the original message.
Company-wide channels use it as a light weekly roundup, and community managers use it to see which posts landed with members.
What you get out of it
The week in five lines
People catching up on Friday see what mattered without scrolling a week of messages.
Reactions as the signal
Ranking is based on what people reacted to, not on who posted most.
Links back to the thread
Each entry links to the original message, so replies and context are one click away.
Bots left out
Automated posts are skipped, keeping the list to people's messages.
Standard scopes
It reads channel history with the scopes your Slack app already has for reading channels.
How it works
What happens, step by step
Every Friday the automation reads the past week of messages in the channel.
It adds up the emoji reactions on each message.
It picks the five with the most reactions, leaving out bot posts.
One post lists them with the author, the top reactions, a short excerpt and a link.
Before it runs live
- Connect Slack, then invite the app to the channel (type /invite @ClickRuntime there)
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Run it at a different time, more or less often, or only on weekdays
- Add an AI step, for example to summarize, sort or draft a reply
- Add another app, for example also send it to Google Sheets
- Combine it with other Slack steps into one automation
Under the hood
The code that runs this automation
import time
from clickruntime import on_trigger, credentials, http, notify
CHANNEL_ID = "C0123GENERAL"
CHANNEL = "#general"
TOP = 5
def slack(method, **params):
resp = http.get(f"https://slack.com/api/{method}", params=params,
headers={"Authorization": f"Bearer {credentials.connection('slack', 'work')}"})
data = resp.json()
if not data.get("ok"):
raise RuntimeError(data.get("error"))
return data
@on_trigger
def run(event):
oldest = str(time.time() - 7 * 86400)
msgs, cursor = [], None
while True:
page = slack("conversations.history", channel=CHANNEL_ID, oldest=oldest, limit=200, **({"cursor": cursor} if cursor else {}))
msgs += [m for m in page["messages"] if m.get("reactions") and not m.get("bot_id") and m.get("subtype") is None]
cursor = page.get("response_metadata", {}).get("next_cursor")
if not cursor:
break
msgs.sort(key=lambda m: -sum(r["count"] for r in m["reactions"]))
if not msgs:
return {"top": 0}
lines = []
for n, m in enumerate(msgs[:TOP], 1):
link = slack("chat.getPermalink", channel=CHANNEL_ID, message_ts=m["ts"])["permalink"]
rx = " · ".join(f":{r['name']}: {r['count']}" for r in sorted(m["reactions"], key=lambda r: -r["count"])[:2])
text = m.get("text", "").replace("\n", " ")
lines.append(f"{n}. <@{m['user']}> · {rx} — <{link}|\"{text[:80]}{'…' if len(text) > 80 else ''}\">")
notify.slack(f"Most-reacted this week in {CHANNEL}:\n" + "\n".join(lines), channel=CHANNEL)
return {"top": len(lines)}FAQ
Common questions
Which Slack scopes does it need?
Can it look across several channels?
Can it count only one emoji, like 🎉?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Know the moment your website goes down
Your team hears in Slack when the site stops responding or slows down, and again when it's back.
See how it worksPost a morning briefing to Slack
Your team starts the day with the weather, a reminder or anything else you'd like in #general.
See how it worksFind Slack channels nobody uses anymore
Once a month you get a list of channels that have gone quiet, so you can archive them.
See how it worksKeep exploring
Set up “Post the most-reacted Slack messages of the week” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.