# RSS & Atom Feed to JSON (`nuhemugames/rss-atom-to-json`) Actor

Turn any RSS, Atom or RDF feed into clean, normalized JSON articles: ISO 8601 dates, plain-text and HTML content, authors, categories and podcast enclosures. Multiple feeds per run, broken feeds reported instead of crashing.

- **URL**: https://apify.com/nuhemugames/rss-atom-to-json.md
- **Developed by:** [kuon](https://apify.com/nuhemugames) (community)
- **Categories:** News, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## RSS & Atom Feed to JSON

Turn any RSS, Atom or RDF feed into clean, normalized JSON: one dataset item
per article with **ISO 8601 dates, plain-text and HTML content, parsed author
names, categories and podcast enclosures** — the same field names no matter
which feed format the source uses. Multiple feeds per run; broken feeds are
reported as failed items instead of crashing the batch. No credentials needed.

### What it does

Give it a list of feed URLs. For each article you get one dataset item with:

- `title`, `url`, `id` — GUID (RSS) / id (Atom), falling back to the article URL
- `published`, `updated` — normalized to UTC ISO 8601 (`2026-08-17T09:30:00Z`), any input format
- `author` — parsed to a human name (RSS `email (Name)` convention handled)
- `summaryText`, `contentText` — HTML stripped to clean plain text (scripts/styles removed)
- `contentHtml` — the original (sanitized) HTML content, when you want the markup
- `categories` — tag/category terms as a string array
- `enclosures` — podcast audio / media attachments as `{url, type, lengthBytes}`
- `feedUrl`, `feedTitle`, `feedType` (rss20/atom10/…), `language` — the source feed

Feeds that fail to download or parse produce a single item with
`status: "failed"` and a clear `error` message, so batch jobs always finish.

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `feedUrls` | array | — | Feed URLs (redirects followed) |
| `maxItemsPerFeed` | integer | `0` (all) | Keep only the first N articles per feed |
| `includeContentHtml` | boolean | `true` | Include `contentHtml` alongside `contentText` |
| `timeoutSecs` | integer | `30` | Download timeout per feed |
| `maxFileSizeMb` | integer | `10` | Larger feeds are skipped with a failed item |

### Example output (abridged)

```json
{
    "feedUrl": "https://fruit.example.com/feed.xml",
    "feedTitle": "Fruit Weekly",
    "feedType": "rss20",
    "status": "success",
    "id": "fruit-weekly-001",
    "url": "https://fruit.example.com/posts/apples",
    "title": "Apple shipments & prices rise",
    "author": "Ann Orchard",
    "published": "2026-08-10T08:30:00Z",
    "summaryText": "Apple volumes grew 12% this week.",
    "contentText": "Apple report\nApple volumes grew 12% this week.\nFuji up\nGala flat",
    "contentHtml": "<h2>Apple report</h2><p>Apple volumes grew <b>12%</b> this week.</p>",
    "categories": ["apples", "markets"],
    "enclosures": [],
    "language": "en-us"
}
```

### Typical uses

- News monitoring and research pipelines (feeds → LLM/RAG-ready text)
- Aggregating many blogs/podcasts into one normalized dataset
- Feeding no-code tools (Zapier/Make via Apify integrations) with clean article JSON

### Limitations

- Content comes from the feed itself — articles are not fetched from their web
  pages (feeds that only carry teasers yield teaser-length `contentText`)
- Password-protected or non-public feeds are not supported

### Development (local)

```bash
cd actors/rss-atom-to-json
uv venv --python 3.13 .venv && uv pip install -p .venv/bin/python -r requirements.txt

.venv/bin/python tests/run_local_test.py           # end-to-end test (apify run equivalent), exit 0 = ALL PASS
../../node_modules/.bin/apify run                  # real apify CLI local run (input: storage/key_value_stores/default/INPUT.json)
```

Test fixtures are `tests/fixtures/sample_rss.xml` / `sample_atom.xml` / `not_a_feed.html`;
expected results live in `tests/expected_output.json`. Publishing → `../../docs/publishing.md`.

# Actor input Schema

## `feedUrls` (type: `array`):

URLs of the RSS, Atom or RDF feeds to parse (one per line). Redirects are followed.

## `maxItemsPerFeed` (type: `integer`):

Keep only the first N articles of each feed (feed order). 0 means all.

## `includeContentHtml` (type: `boolean`):

Include the article's original HTML content (`contentHtml`) in addition to the plain-text `contentText`.

## `timeoutSecs` (type: `integer`):

Timeout for downloading each feed.

## `maxFileSizeMb` (type: `integer`):

Feeds larger than this are skipped with a failed item.

## Actor input object example

```json
{
  "feedUrls": [
    "https://news.ycombinator.com/rss"
  ],
  "maxItemsPerFeed": 0,
  "includeContentHtml": true,
  "timeoutSecs": 30,
  "maxFileSizeMb": 10
}
```

# Actor output Schema

## `articles` (type: `string`):

All dataset items (one per article): title, url, ISO 8601 dates, author, plain-text and HTML content, categories, enclosures.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "feedUrls": [
        "https://news.ycombinator.com/rss"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("nuhemugames/rss-atom-to-json").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "feedUrls": ["https://news.ycombinator.com/rss"] }

# Run the Actor and wait for it to finish
run = client.actor("nuhemugames/rss-atom-to-json").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "feedUrls": [
    "https://news.ycombinator.com/rss"
  ]
}' |
apify call nuhemugames/rss-atom-to-json --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nuhemugames/rss-atom-to-json"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/usMQaDDOdUaHnjojd/builds/DMjseNLAJjGbGWJui/openapi.json