RSS feed
Start a workflow when a new entry appears in an RSS or Atom feed.
The RSS trigger block starts a workflow for each new entry of an RSS or Atom feed. It is a polling trigger: Scrydon fetches the feed on a schedule, so you build no loop of your own and the trigger has no inbound URL for anyone to call.
Configuration
| Field | Required | Notes |
|---|---|---|
| Feed URL | yes | An http or https URL of an RSS 2.0, RSS 1.0 or Atom feed. |
| Poll Interval | no | Every 5 minutes, 15 minutes (default), 30 minutes, hour, 6 hours or day. |
| Title Filter | no | Only entries whose title contains this text, ignoring case, start a run. |
The feed is fetched with a 30 second time limit, and a response larger than 5 MiB is refused. Error messages name the feed by its address without the query string, so a feed URL that carries a token does not leak it into the run log.
What the trigger emits
Reference the fields from downstream blocks as <rss1.title>, <rss1.link>, and
so on, where rss1 is the name of the trigger block.
| Field | Content |
|---|---|
title | The entry title. |
link | The entry's own page. |
description | The summary or description. |
content | The full content, when the feed provides it. |
author | The entry author. |
guid | The entry's unique id. When the feed gives none, its link. |
published | An ISO-8601 timestamp, empty when the feed gives no valid date. |
categories | An array of the entry's category tags. |
feedTitle | The title of the feed. |
feedUrl | The URL of the feed. |
What counts as new
- The first poll starts nothing. It records the entries the feed lists at that moment, so adding a feed with a long history does not start a run for every old entry. Only entries that appear afterwards start a run.
- An entry is recognised by its
guid. An entry whose guid has been seen is never delivered again, even if the feed edits its title or moves it. An entry with no guid and no link cannot be recognised and is ignored. - New entries run oldest first, in the order they were published, when several arrive between two polls.
- Scrydon remembers the newest 1000 entries. A feed that lists more than 1000 entries is read up to its newest 1000; older ones never start a run. Entries that left the feed stay remembered until 1000 newer ones push them out, so one empty or truncated answer from the server (a maintenance page, a CDN hiccup) does not make the old entries come back as new.
- Changing the Feed URL starts over. The memory belongs to one feed. After you edit the URL the next check is a first poll for the new feed: it records its entries and starts no run, instead of treating all of them as new. Entries that were published during the switch are not delivered.
- The Title Filter only decides which new entries start a run. An entry the filter skips is still remembered, so changing the filter later does not replay it.
Timing
Scrydon checks for due triggers every five minutes, so the poll interval is the shortest time between two fetches and a new entry can wait up to one check longer than the interval you chose.
Polling triggers only run in a promoted environment. In Development the trigger saves and validates, but never ticks. Promote the workflow to Staging or Production to see it fire, and use Test on the trigger to exercise the downstream blocks while you build.
When the feed fails
A poll fails when the feed does not answer in time, answers with an HTTP error, is larger than 5 MiB, or is not an RSS or Atom document. Like every polling trigger, an RSS trigger whose polls fail 10 times in a row is switched off automatically; one successful poll resets the count. Fix the cause (the URL, or the feed itself), then save or redeploy the workflow so the trigger is registered again.
Troubleshooting
| Symptom | Cause |
|---|---|
| Nothing fires, no errors | The workflow is in Development, or no new entry has appeared since the first poll. |
| The first entries never started a run | By design: the first poll only records what the feed lists. |
is not an RSS or Atom feed | The URL answers with a web page, not a feed. Open the URL in a browser and look for the feed's own link. |
did not answer within 30 seconds | The feed server is slow or unreachable from Scrydon. |
is larger than 5242880 bytes | The feed is over 5 MiB. Use a shorter feed from the same publisher, such as a category feed. |
| The trigger stopped after repeated failures | Ten consecutive polls failed and the trigger was switched off. Fix the feed, then save or redeploy the workflow. |