How to Build a Grok 5.1 News Monitoring Bot for Slack
You can turn Grok 5.1 into a scheduled Slack alert bot that pulls live news every 30 minutes, filters duplicates, and posts only what changed. The whole thing is about 80 lines of Python plus a cron job, and it costs a few dollars a month at typical volumes.
This is the automation I’d build for a team that tracks a niche — funding rounds, competitor releases, regulation changes.
Why Not Just Use an RSS Reader?
RSS gives you headlines with no synthesis. Grok 5.1 reads the articles, groups related coverage, and writes a two-sentence “what actually happened” summary with links. That’s the difference between 40 headlines and one useful paragraph.
It also handles topics that don’t have clean feeds, like “anything about our startup being mentioned on X.”
What Is the Architecture?
Four moving parts:
- Scheduler — cron or a serverless timer, every 30 minutes.
- Grok 5.1 API call — searches for the topic and returns a structured summary.
- Dedup store — a small JSON file or Redis set of seen URLs.
- Slack webhook — posts the new items as a formatted message.
How Do You Get Structured Output?
Ask Grok 5.1 for JSON. It follows schema instructions well, and JSON makes dedup trivial because each item carries a URL.
prompt = """Search for news about \"open-weight LLMs\" from the last 2 hours.
Return ONLY JSON: [{\"title\":...,\"url\":...,\"summary\":...,\"source_time\":...}]"""
resp = client.chat.completions.create(model="grok-5.1", messages=[{"role":"user","content":prompt}])
items = json.loads(resp.choices[0].message.content)Then filter: new = [i for i in items if i['url'] not in seen]. Skip the Slack post entirely when new is empty, so the channel stays quiet on slow days.
How Do You Keep Costs Down?
Two levers. First, run less often — every 30 minutes is enough for most topics; every 5 minutes doubles cost for marginal gain. Second, ask for summaries, not full articles. A typical run consumes about 8k input and 600 output tokens, roughly $0.03 at Grok 5.1’s $3 / $15 per-million rates, plus the search fee.
At 48 runs a day that’s about $1.60 daily — worth it for a team, wasteful for a solo user who could just check X twice a day.
What Breaks in Production?
Duplicate coverage with different URLs is the main one. The same story runs on five outlets; URL dedup misses all but one. Add a similarity check on titles (a cheap token-overlap score above 0.7 marks a dupe).
Second issue: rate limits during breaking news when everyone’s calling at once. Wrap the API call in a retry with backoff. Third, hallucinations about time — verify the source_time field is plausible before trusting “last 2 hours.”
Who Should Build This
Small teams monitoring a fast niche, investor-relations folks, and PR shops watching coverage. Skip it if you check news once a day — the setup isn’t worth it for that.
Quick Summary
- Grok 5.1 plus cron and a Slack webhook makes a cited news alert bot.
- Request JSON output so URLs can be used for de-duplication.
- A 30-minute cadence costs roughly $1.60/day at typical token volumes.
- Add title-similarity checks to catch the same story on different outlets.
- Honest tradeoff: wasted spend for anyone who checks news rarely.
