The RSS Feed block monitors RSS and Atom feeds – when new items are published, your workflow triggers automatically.
Configuration
- Add RSS Feed Block - Drag the RSS Feed block to start your workflow
- Enter Feed URL - Paste the URL of any RSS or Atom feed
- Deploy - Deploy your workflow to activate polling
Once deployed, the feed is checked every minute for new items.
Output Fields
| Field | Type | Description |
|---|---|---|
title | string | Item title |
link | string | Item link |
pubDate | string | Publication date |
item | object | Raw item with all fields |
feed | object | Raw feed metadata |
Access mapped fields directly (<rss.title>) or use the raw objects for any field (<rss.item.author>, <rss.feed.language>).
Use Cases
- Content monitoring - Track blogs, news sites, or competitor updates
- Podcast automation - Trigger workflows when new episodes drop
- Release tracking - Monitor GitHub releases, changelogs, or product updates
- Social aggregation - Collect content from platforms that expose RSS feeds
RSS triggers only fire for items published after you save the trigger. Existing feed items are not processed.
Common Questions
The feed is polled every minute. On each poll, the service fetches the feed, compares items against the last checked timestamp and a list of previously seen GUIDs, and triggers your workflow only for genuinely new items.
The service tracks up to 100 recent item GUIDs and the last checked timestamp. An item is considered new only if its GUID has not been seen before and its publication date is after the last checked timestamp. Additionally, an idempotency layer prevents duplicate workflow runs for the same item.
Yes. Each polling cycle processes a maximum of 25 new items, sorted by publication date (newest first). If a feed publishes more than 25 items between polls, only the 25 most recent are processed.
Each triggered run receives: title, link, and pubDate as top-level convenience fields, plus a full item object containing all fields (including guid, summary, content, contentSnippet, author, categories, enclosure, and isoDate), a feed object with the feed's title, link, and description, and a timestamp of when the event was processed.
A failed fetch increments the webhook's consecutive failure counter. After 100 consecutive failures, the RSS trigger is automatically disabled. On any successful poll, the counter resets to zero.
Yes. The underlying parser (rss-parser) supports both RSS and Atom feed formats. You can use the URL of either format in the Feed URL field.