Automate a weekly competitor news digest from their public feeds

Checking competitor blogs and news by hand every week gets skipped. A scheduled agent reads the public feeds you list, drafts a short digest of what changed, and its department head reviews it before you approve.

What you’ll set up

Connections

Works from public sources: Competitor blog RSS or Atom feeds, Competitor news and press pages

Inputs

Competitor names · Required

List, no default

Feed or news page addresses · Required

List, no default

Ready by · Required

Time, default 07:00

Brief · Required

Text, prefilled and editable during setup.

Runs

Runs every Monday at 08:00

Done by Market researcher

Email to new contacts, and follow-ups nobody has answered, waits for your approval by default. Replies in threads a contact has answered, and email to your own team, can send automatically depending on your settings.

Set up this job

You approve every report · Free to start

How it runs

One agent does the work. Its department head reviews it, then you approve.

  1. 1Market researcher

    Runs every Monday at 08:00 and prepares the report from your connected sources.

  2. 2CMO · Review

    The department head reviews the report before it reaches you.

  3. 3You

    Email to new contacts, and follow-ups nobody has answered, waits for your approval by default. Replies in threads a contact has answered, and email to your own team, can send automatically depending on your settings.

What you get

Sample, not live dataSample competitor digest (Sample, not live data)

Sample, not live data. Companies and posts are invented.

Competitor digest, week of 9 March (sample)

Example Co (2 items)

  • Announced a team plan with shared workspaces. Link: example.test/blog/teams
  • Published a customer story on faster onboarding. Link: example.test/blog/story

Sample Labs (no new items; feed read OK)

Needs your approval before it is sent.

What the job reads

You list competitors and the public feed or page address for each one. Many blogs and news pages publish an RSS or Atom feed. In RSS 2.0 each item carries a title, a link, a description and an optional publication date. In Atom each entry has an id, a title and an updated time, which marks a change the publisher considers significant. The agent uses those fields to see what is new since the last run. It reads public pages alone. It does not log in anywhere.

How the scheduled job works

Each week the scheduled agent fetches every feed you listed, keeps items dated since the previous run, and groups them by competitor. For each item it writes one plain line: what was published and why it might matter to you, with the link beside it. It separates product announcements from general news and says so when a feed is empty or could not be read, so a quiet week is not mistaken for a broken one. If a feed has no dates, it says that dating is uncertain instead of guessing.

Review and approval

Before the digest reaches you, the department head agent checks it: does every line link to a real item, is anything described that the item does not say, and are the dates right. You then approve, edit or skip the digest, and nothing is sent to your team until you do. The digest is labelled as AI-written and works from what the feeds publish, so it can miss changes a competitor never announces.

Using the digest

Start with the product announcements, then the news lines. A competitor that posts several items on one theme in a week is worth a closer look at the original pages. Keep the list short, five to ten sources, so the digest stays readable. The sources are set in the schedule fields when you add the job, so review that list now and then as your competitors change.

Questions

Start with one report

Set up this job

You approve every report · Free to start