Feed Digest Monitor - RSS, Atom, GitHub, Status Pages
Pricing
from $0.50 / 1,000 new items
Feed Digest Monitor - RSS, Atom, GitHub, Status Pages
Poll RSS/Atom feeds, GitHub releases, and statuspage.io status pages, and get ONLY the items that are new since your last run. The missing dedup layer for feed monitoring: schedule it and receive a clean change digest instead of the same items again and again.
Pricing
from $0.50 / 1,000 new items
Rating
0.0
(0)
Developer
Jimmy A
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
8 hours ago
Last modified
Categories
Share
Feed Digest Monitor - RSS, Atom, GitHub Releases, Status Pages
Poll your feeds and get only what's new since last time. RSS and Atom feeds, GitHub release feeds (just owner/repo), and statuspage.io status pages - deduplicated against everything previous runs have seen. Schedule it and receive a clean change digest instead of the same 50 items every hour.
Why this instead of an RSS reader actor
Readers return the current feed contents every run. This actor remembers. The output of a scheduled run is the delta: new posts, new releases, new incidents, status changes. That is what you actually want to pipe into Slack, email, a database, or an AI agent.
Feeds it understands
| Spec | Treated as |
|---|---|
https://example.com/feed.xml | RSS or Atom (auto-detected) |
apify/crawlee | GitHub releases feed for that repo |
https://www.githubstatus.com | statuspage.io: incidents, degraded components, status changes |
Input
{"feeds": ["hnrss.org/frontpage", "apify/crawlee", "https://www.githubstatus.com"],"onlyNew": true}
Output
One record per new item, plus a run digest:
{"feed": "github:apify/crawlee","feedKind": "github","feedTitle": "Release notes from crawlee","id": "tag:github.com,2008:Repository/...","title": "v3.17.0","link": "https://github.com/apify/crawlee/releases/tag/v3.17.0","publishedAt": "2026-06-02T...","isNew": true}
{ "type": "digest", "feeds": [{ "feed": "github:apify/crawlee", "items": 10, "new": 1 }] }
First run for a feed outputs everything and saves the baseline; deltas start with run two. Use digestGroup to track the same feeds on independent schedules.
Use cases
- Dependency watch: new releases of the libraries you run, nothing else
- Status monitoring: get an item only when a vendor's status page changes
- Content monitoring: new posts from blogs, news, podcasts, job boards with feeds
- AI agents: "what changed across my stack today" as one standby call
API / Standby mode
GET /?feed=apify/crawlee&onlyNew=true
Returns total, new count, and the new items synchronously.
Pricing
| Event | Price |
|---|---|
| Actor start | $0.0001 |
| Per feed polled | $0.001 |
| Per new item | $0.0005 |
| Run digest | $0.01 |
| API call (standby) | $0.01 |
Hourly monitoring of 10 feeds costs about $8/month, and most polls return zero new items, costing almost nothing beyond the poll.
FAQ
Status page shows nothing - broken? No: all-operational status pages produce zero items by design. You get items when incidents open, update, resolve, or components degrade.
How much history does it remember? The last 5,000 item IDs per feed - far more than any feed window.
Podcast/YouTube feeds?
Any valid RSS/Atom works, including YouTube channel feeds (https://www.youtube.com/feeds/videos.xml?channel_id=...).