RSS Feed Aggregator — Feedly Alternative

Aggregate RSS, Atom, and JSON feeds into a clean article dataset. Discover advertised feeds from supplied websites, filter keywords, tag sources, and remove duplicates for research and recurring news workflows. For news researchers, each dataset record is one normalized feed article with its source tags and available publication details.

Workflow: put the results to work

Provide trusted feed URLs or websites that advertise a feed. Set inclusion and exclusion terms to match the research brief, then review source-tagged articles before passing them to an alert or summary workflow. Account folders and saved-reading features stay in your chosen reader.

Best fit and focused standalone workflow

Choose this Actor for news monitoring, competitive intelligence, industry research, and agent workflows that need a bounded export from trusted public feed sources. start with public feeds, collect a clean dataset, then pass the source-tagged output to your own spreadsheet, database, alert, or analysis workflow. Feedly-style account organization, saved reading, and private newsletter delivery remain separate workflows, while this Actor keeps the public-feed collection step portable and transparent.

What you get

One dataset item represents one retained article. Fields remain consistent across RSS, Atom, and JSON Feed sources.

Field	Meaning
title, url, summary, content	Cleaned article metadata and feed-provided text
sourceName, sourceTags, feedUrl, sourceUrl	Provenance and source grouping
publishedAt, updatedAt, author, categories	Feed-provided editorial metadata, nullable where absent
matchedKeywords	Requested include terms that matched the entry
feedType, collectedAt	Detected format and collection timestamp

Input

Give each source a public feed URL or a website homepage. Website URLs are examined for an advertised alternate feed link, and the run summary records the resolved feed URL and source diagnostics so you can confirm provenance for each collection.

{
  "sources": [
    {
      "url": "https://hnrss.org/frontpage",
      "name": "Hacker News",
      "tags": ["technology", "startups"]
    },
    {
      "url": "https://www.theverge.com/rss/index.xml",
      "tags": ["technology"]
    }
  ],
  "includeKeywords": ["AI", "open source"],
  "excludeKeywords": ["sponsored"],
  "publishedWithinHours": 168,
  "maxItems": 100,
  "sortOrder": "newest",
  "deduplicateBy": "url"
}

maxItems is a whole-run cap, not a per-source limit. The Actor checks this cap before each write, so it also bounds the main per-article event charge.

Example output

{
  "id": "https://example.com/research/article",
  "title": "A research headline",
  "url": "https://example.com/research/article",
  "sourceName": "Example Research",
  "sourceTags": ["technology"],
  "author": "Example Author",
  "categories": ["Research"],
  "summary": "A feed-provided summary.",
  "content": null,
  "publishedAt": "<ISO 8601 publication timestamp>",
  "updatedAt": null,
  "matchedKeywords": ["AI"],
  "feedUrl": "https://example.com/feed.xml",
  "sourceUrl": "https://example.com",
  "feedType": "rss",
  "collectedAt": "<ISO 8601 collection timestamp>"
}

Outcome records

Every terminal path writes OUTPUT and RUN_SUMMARY.

• COMPLETE: all readable sources were processed and retained items were written.
• PARTIAL: useful items were written and the summary records the portion of source coverage completed.
• VALID_EMPTY: readable feeds had no items matching the filters.
• INVALID_INPUT: source URLs or limits can be corrected by the caller.
• UPSTREAM_FAILED: the summary records source-level connectivity or feed-format diagnostics before the run ends.

API

Use the khadinakbar/feedly-alternative Actor endpoint with your own Apify API token.

curl -X POST "https://api.apify.com/v2/acts/khadinakbar~feedly-alternative/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"sources":[{"url":"https://hnrss.org/frontpage","tags":["technology"]}],"maxItems":25}'

Prompt card for an agent

As an AI agent, collect up to 50 recent articles from these trusted public RSS feeds. Keep items mentioning AI or cybersecurity, use URL deduplication, and return title, URL, source tags, published time, summary, matched keywords, source URL provenance, collection time, outcome, and dataset readback guidance within the stated cost cap.

Workflow scenario: from feeds to a daily brief

A research lead starts with five trusted industry feeds, adds a source tag for each publisher, and sets a 24-hour window. The Actor then combines the entries, applies the team’s include terms, and exports the newest source-tagged dataset items. Next, the lead groups articles by sourceTags, checks matchedKeywords and publishedAt, and passes the resulting list into a daily brief or alert workflow. Scheduling the same saved input creates consistent snapshots that make source changes easy to analyze over time.

Best results and practical guidance

• Prefer direct RSS, Atom, or JSON Feed URLs when known. Website discovery follows declared feed links and records the selected feedUrl.
• Tag sources by subject, customer, competitor, or region so a downstream workflow can group them without re-parsing feeds.
• Use includeKeywords for a narrow alert feed and use an empty list for archival or broad monitoring.
• Schedule a saved task for recurring snapshots. The output keeps each run’s source-level provenance and applies deduplication within that collection.

Builder's note

I designed this Actor around the cleanest reliable contract I found in feed monitoring: public syndication feeds already supply structured updates, so collection should preserve source metadata and make filter and cost boundaries visible. The design keeps one record per feed entry, names the resolved feed URL, and places source diagnostics in RUN_SUMMARY, which makes an automation easier to inspect and compose.

Legal and responsible use

Collect only public sources you are authorized to monitor and follow each publisher’s terms, copyright rules, and robots directives. Article text comes from the feed payload, preserving a clear boundary between syndicated content and publisher pages.

Pricing and run costs

This Actor uses Pay per event plus Apify platform usage. The Pricing tab lists the current event rates and billing terms.

Event	Billing unit	When it applies
apify-actor-start	Actor Start	Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
article-collected	Article collected	One normalized public-feed article successfully saved to the dataset.

Run cost combines the charged events and Apify platform usage. Review the run charge limit and requested result count before starting.

Independent alternative

This Actor provides the specific workflow described above. It is not affiliated with or endorsed by Feedly; the named product and its trademarks belong to their respective owners.

Connect an AI agent

Use the Apify MCP configurator to choose an available client connection. Inspect this Actor’s current input schema and required credentials before running it.