Know what they shipped before your client asks.
It reads their blog every day, summarises what is new, and flags anything that lands in your category.
4 steps · runs on a schedule · added to your workspace as a draft
Overnight
Their blog, yesterday. Their blog, today.
The difference between the two is the only part worth your morning.
01 · Their blog, as it stood yesterday.
02 · Overnight, two posts that weren't there.
03 · Each is read, so you don't have to.
04 · Only one lands in your category. That one is flagged.
05 · And every day adds to the record of how often they ship.
rival-a.com/blogyesterdaytoday · 09:00 UTC
The 2026 guide to answer engine optimizationnew
We're hiring a head of partnershipsnew
- Q3 product update
- How we think about onboarding
- Customer story: a regional bank
- Five reporting mistakes
Read and summarised
A 3,000-word pillar aimed at the exact questions you track.
in your category
Read and summarised
A hiring post. No overlap with your topics.
logged for cadence
Their publishing cadence · last 14 days6 posts
In, and out
You give it a competitor's blog URL. This is what comes back.
- Shape
- 4 steps
- Scheduled
- run mode
- 1
- click to add
- 01New post“The 2026 guide to answer engine optimization” — lands squarely in your category.in your category
- 02New postA hiring announcement. Logged for cadence, not flagged.
Illustrative output.
Runs daily, unprompted
Summarised, so you do not read their blog to find out
Flags only what lands in your category
Builds a record of their publishing cadence
What it does
Pre-built, then yours to customize.
Add it to your workspace in one click. Sensible defaults and example inputs are already filled in.
Reads from · writes to
- Any public blog
The template, step for step
- Trigger
- HTTP request
- LLM call
- Notify
Ships with the schedule 0 9 * * * — daily, 09:00 UTC. It is added as a Draft; the schedule starts once you set it Active.
The steps
What happens on every run.
- scrape_competitor_blog
- summarize_new_posts
- flag_relevant_to_you
- save_watch_log
4 steps · Runs on a schedule0 / 4
Run history keeps each step's output and runtime, and the input of every step that completed.
Before & after
The time this gives back.
The templates that publish put a Human review step before the CMS step, and nothing ever posts to Reddit for you. Review is a step, not a lock: a workflow you build or edit can publish or message a channel without one, so add it wherever you want the sign-off.
Doing it by hand
~5.8 hrs
Daily competitor blog watcher
~20 min
Doing it by handyour team
- Checking their blog~15m / day
- Reading the new posts~25m / day
- Telling the team~10m / day
Per week, by hand~5.8 hrs
Daily competitor blog watcherLive
- Agent scrapes and summarisesdaily
- Agent flags what mattersauto
- You read the flagged items~4m / day
Scheduled agent~20 min
FAQ
Questions, answered.
Run one instance per competitor. Each keeps its own watch log, which makes the cadence comparison useful rather than a single merged feed.
You define it when you add the agent. The Filter step uses that definition, so a competitor posting about hiring does not reach you while one posting about your category does.
No. It reads the blog over HTTP, so it works on sites that never exposed a feed.
Free to start
Add this agentto your workspace.
Start free. Customize the steps, run it on demand or on a schedule, and approve anything that ships.