RSS News Digest Agent
Reads your feeds every morning and posts one Slack digest grouped by theme, each story a headline, a link, and one line saying what happened.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Morning tick, Tuesday 07:30
The 07:30 tick fires. Overnight the eight feeds returned 61 new items. Three cover the same EU battery subsidy decision, from Reuters, Sifted, and a trade blog. Two are funding rounds, a Nairobi logistics startup at 14 million dollars and a Rotterdam port software company at 3.2 million euros. The rest are product announcements, two conference agendas, and an obituary.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect RSS
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Feeds list
The feeds you want read every morning, one per line, as feed addresses or plain site addresses the agent can find the feed for. Give each a short label so the digest names sources the way your team already does.
Digest style
How the digest should read: how many stories you want, which themes matter to you, how long a line should be, whether you want plain summaries or your own angle, and what is never worth including.
Choose which agent runs it
NoClick's built-in models work out of the box — or bring Claude Code, Codex, and other coding agents on your own subscription.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
About this agent
Everyone means to read their industry feeds and nobody does, so the same news reaches the team three days late as a forwarded link. This agent parses your feeds every morning, groups the stories that matter under themes, and posts one Slack message with a headline, a link, and one line on each. Dead feeds are named at the bottom instead of quietly disappearing, which is how most homemade digests rot without anyone noticing.
What people use it for
- One morning read for the team - Everyone sees the same short digest at half past seven instead of eight people skimming eight sites and all missing the same story.
- Competitor and regulator news together - Add their blogs and the regulator's feed to the list and their announcements arrive in the same message as the trade press, with no extra work.
- Feeds that die get noticed - A moved publication or a broken feed is named in the last line the morning it breaks, so your digest never quietly shrinks while looking healthy.
- Raw material for your newsletter - Content and marketing teams start from a grouped, linked set of overnight stories rather than an empty document and thirty open tabs.
Before you fork
What do I need connected before this runs?
A Slack workspace and the channel you want the digest in, plus your list of feeds. Public feeds need no credentials at all. If you only have site addresses, the agent finds the feed for each one on the first run and uses it from then on.
Will it summarise things it did not read?
No. Its instructions are explicit that a take states what the item says and stops there, and that a headline-only feed is reported as headline only rather than guessed at. Opinions appear only when you ask for them in the digest style, and they are marked as yours.
How many feeds can it handle, and what does it cost?
One agent run each morning, so about thirty a month. Fifteen or twenty feeds is comfortable. Past that the run takes longer and the digest gets harder to read, which is usually a sign to split it into two digests on different schedules.
Run it with your coding agent
More agents like this
Put RSS News Digest Agent to work
Free to start. Guided setup, a test run against staged conversations, and it's live.