Skip to content
live2025

NewsFlow

Tech news, fetched, categorised and summarised without me.

n8nGemini APILLM APIsVercel

Staying current

  • Dozens of sources, heavy overlap
  • Most items irrelevant to any one reader
  • Headlines written to be clicked
  • ~30 minutes a day of skimming
  • Most of it discarded

Now

  • One dashboard, categorised
  • Summary first, link only if it earns one
  • Runs on a schedule, unattended
  • Read in the time the skimming took

Three stages, no human in any of them

runs itselfneeds a person
  1. 01

    Fetch

    n8n, on a schedule, with retries

  2. 02

    Categorise

    browsable, not a chronological firehose

  3. 03

    Summarise

    Gemini condenses each item

  4. 04

    Dashboard

    the day's news, compressed

A pipeline problem wearing a reading-habit costume. The summary is the product — the link is there if the summary earns a click.

Why a workflow layer, not a cron job and a script

Sources change constantly
Adding or re-weighting one shouldn't be a deploy.
Failure is normal
Feeds go down and APIs rate-limit. Retry and error handling are built in, not reimplemented.
It stays legible
The pipeline reads as a diagram, which matters when you come back to it in three months.

Live at news-flow-liard.vercel.app.