Feed & Newsletter Monitor avatar

Feed & Newsletter Monitor

Pricing

$0.98 / 1,000 post scrapeds

Go to Apify Store
Feed & Newsletter Monitor

Feed & Newsletter Monitor

Monitors any RSS/Atom feed, JSON Feed, or Substack publication archive and returns structured post rows with title, URL, publish date, summary, tags, word count, and paywall status.

Pricing

$0.98 / 1,000 post scrapeds

Rating

0.0

(0)

Developer

Mark

Mark

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Categories

Share

Pulls posts from any RSS/Atom feed, any JSON Feed, or a Substack publication's /api/v1/archive endpoint, and returns one clean row per post — title, URL, publish date, full text summary, tags, word count, and whether the post is paywalled.

Input

FieldTypeRequiredDescription
urlstringyesRSS/Atom feed URL, JSON Feed URL, or Substack archive URL (https://<publication>/api/v1/archive?sort=new&limit=N).
maxItemsintegernoMax posts to return (default 20).

The actor auto-detects the response shape: < → RSS/Atom XML, [/{ → Substack archive array or JSON Feed object.

Returns (one row per post)

{
"feedTitle": "Astral Codex Ten",
"postTitle": "Nicholas Decker In Hell",
"url": "https://www.astralcodexten.com/p/nicholas-decker-in-hell",
"publishedAt": "2026-09-01T07:37:05.059Z",
"summary": "I. Econblogger Nicholas Decker is not a fan of AI 2040: ...",
"tags": [],
"wordCount": 3148,
"paywalled": false,
"cursor": "2026-09-01T07:37:05.059Z"
}

cursor is the post's publish date (falls back to its URL) — save the newest value between runs to only process posts published since then.

No personal data is collected: author names/emails are dropped even when the source feed carries a dc:creator byline.

Pricing

$0.00098 per post returned. No run-start fee — pay only for posts you get, whether the run returns 1 or 1,000.

Limits / known gaps

  • Paywall detection only works for Substack's archive API (audience field). RSS/Atom feeds carry no paywall signal, so paywalled is always false there even if the full post is gated on the site.
  • tags is populated from Substack's postTags or Atom/RSS <category> elements; many feeds don't tag posts at all, in which case it's [].
  • JSON Feed support covers the standard items[] shape; nonstandard/custom JSON APIs may not map cleanly onto the row fields above.