Source connector

RSS connector

RSS integration for databases, warehouses and BI tools

Syndicated feed items from publishers and blogs. Datrise captures RSS entities such as feed items, titles, links, publication dates, authors and categories, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The RSS 2.0 (RSS Advisory Board specification) authenticates with no auth, incremental runs key on guid (paired with pubDate).

Of the 6 objects, 6 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `rss_feed_items`) with a schema derived from the RSS API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the RSS pipeline page, and join the waitlist to get the RSS connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What RSS data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
feed items	rss_feed_items	Upsert by primary key, incremental on updated-at
titles	rss_titles	Upsert by primary key, incremental on updated-at
links	rss_links	Upsert by primary key, incremental on updated-at
publication dates	rss_publication_dates	Upsert by primary key, incremental on updated-at
authors	rss_authors	Upsert by primary key, incremental on updated-at
categories	rss_categories	Upsert by primary key, incremental on updated-at

RSS API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	RSS 2.0 (RSS Advisory Board specification)
Authentication	no auth — RSS feeds are plain HTTP GET resources with no authentication layer defined by the spec; a minority of private feeds add a URL token or Basic Auth entirely outside the RSS spec itself.
Pagination	none — The spec defines no pagination; a feed returns whatever set of `<item>` elements the publisher currently includes (commonly just the most recent items), with no `next`/offset mechanism.
Rate limit	Not published
Incremental cursor	guid (paired with pubDate) — The spec defines no incremental query mechanism; consumers detect new items by diffing `<guid>` values seen since the last poll, and by convention most aggregators poll about once per hour regardless of the optional `<ttl>` channel hint.
Webhooks	No
Bulk export	No
Deletes detectable	No — the spec has no deletion signal; an item that stops appearing in the feed (typically because the publisher only keeps a rolling window of recent items) simply disappears with no tombstone or removal event

Official API reference

What bites when replicating RSS

Only `title` or `description` is required on an `<item>` — neither `guid` nor `pubDate` is guaranteed, so a connector relying on `guid` for dedup or `pubDate` for ordering must handle feeds that omit either.
The `guid` element's `isPermaLink` attribute defaults to `true`, so a bare `<guid>1234</guid>` with no attribute is assumed to be a clickable URL unless the publisher explicitly sets `isPermaLink="false"`; treating every guid as an opaque ID silently breaks that default.
Feeds are commonly truncated to a rolling window of the most recent items by the publisher; once an item ages out of that window it vanishes from the feed with no delete signal, so anything not captured during that window is permanently missed.
The `<ttl>` polling-interval hint has 'sparse' aggregator support per the RSS Best Practices Profile, and the spec defines no HTTP conditional-GET (ETag/If-Modified-Since) behavior, leaving polling cadence entirely up to the consumer.

Compare this against every other documented API

Popular destinations for RSS

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

RSS connector FAQ

What RSS data does the connector extract?: 6 objects: feed items, titles, links, publication dates, authors and categories. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the RSS integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load RSS data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each RSS → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your RSS pipeline with guided onboarding

Join the waitlist to get priority access for RSS integrations with guided setup, schema-aware mapping, and production-grade incremental sync.