Skip to content

Newsroom Wire Triage

Example prompt: "Every weekday at 7am, read the last 18 hours of items from the wire RSS feeds listed in the 'Wires' tab of our editorial Google Sheet. For each item, pull the headline and dek and match it against the beats and running stories in the 'Beats' and 'Tracking' tabs. Group items by beat and rate each one 'develop today', 'keep an eye on', or 'skip', with a one-line reason. For anything rated 'develop today', also note which of our existing pieces it connects to. Post the grouped digest in the #newsroom Slack channel by 7.45am, and write the full log to a new row-per-item tab called 'Wire Log YYYY-MM-DD' in the sheet."

The Problem

The morning wire scan is one of the oldest jobs in a newsroom and still one of the most tedious. An editor opens half a dozen wire feeds, Google Alerts, and aggregator pages, reads through a few hundred items, and mentally sorts the three or four that matter today from the rest. It has to happen before the morning meeting, and it's the kind of work that gets rushed or skipped on short-staffed mornings, which is exactly when a missed story hurts most.

How GloriaMundo Solves It

We build a scheduled workflow that does the first pass of wire triage and delivers a grouped digest before the morning meeting. A code step reads the configured list of wire RSS feeds from the editorial Google Sheet. A URL extract step fetches each feed and parses the items from the last 18 hours. An integration step pulls the current beats and the running stories the newsroom is tracking. An LLM step matches each item to a beat, rates it, and writes a one-line reason — connecting it to existing coverage where there's a clear link. A second integration step writes the full item-by-item log to a dated tab on the sheet. A final integration step posts the grouped digest to Slack. Glass Box preview lets you check the classifications and tweak the wire list or beats before the scheduled run becomes live.

Example Workflow Steps

  1. Trigger (scheduled): Every weekday at 7am.
  2. Step 1 (integration): Read the list of wire RSS feeds from the 'Wires' tab of the editorial Google Sheet.
  3. Step 2 (url_extract): Fetch each feed and parse items published in the last 18 hours.
  4. Step 3 (integration): Read current beats and running stories from the 'Beats' and 'Tracking' tabs.
  5. Step 4 (LLM): Classify each item by beat, rate 'develop today' / 'keep an eye on' / 'skip', and note any link to a running story.
  6. Step 5 (code): Sort and group the rated items by beat, keeping the 'develop today' items at the top.
  7. Step 6 (integration): Write the full log to a new 'Wire Log YYYY-MM-DD' tab.
  8. Step 7 (integration): Post the grouped digest to the newsroom Slack channel before 7.45am.

Integrations Used

  • Google Sheets — wire feed configuration, beats, running stories, and the dated wire log
  • Slack — the grouped digest in the newsroom channel
  • RSS / URL Extract — platform fetch of wire content for the overnight window

Who This Is For

News editors, desk leads, and producers at digital-first publications, trade outlets, and in-house newsrooms who run a morning meeting and need the wire scan done consistently and quickly before it starts.

Time & Cost Saved

A thorough morning wire scan takes 45-75 minutes when done properly, and that's before any editorial discussion. This workflow delivers the grouped digest to Slack by 7.45am so the editor walks into the morning meeting with a pre-sorted short list. That saves around an hour a day for the person who'd otherwise do the scan, and makes it practical to widen the wire list without adding work.