Thanks TotalInformation.
I understand these things are not high on the agenda but also was not aware that RSS feeds are so difficult. I stumbled upon node-red only due to this old blog entry and to my ears, it just sounded easier and echoed exactly my concerns. Difference seems to be that he is a whiz and I am not. 
https://dannysu.com/2016/12/29/huginn-to-node-red/
I also contacted him as he seemed to have had success with his flow and was the developer of the feedparser node. No response though thus me being here. Node-red seems not made for mainstream, neither is Huginn but the agends at huginn work easier. A shame actually as I can easily see more people without programming skills being highly interested to use node-red. Especially with an installation as easy as with node-red!
As for the website monitor:
a) For now I have about 15 website monitors which I assume would translate into 15 monitoring nodes, all feeding into a flow where there’s is only one output-node.
b) I am looking for subsets on pages for triggers. To ID the relevant parts/ CSS subsets I use the Chrome Extension SelectorGadget. With that I monitor some pages each day and some once a week.
c) Metadata is not relevant for me as a trigger, only the published content. In the best case the content goes through a filter and if it passes keywords, triggers an action such as extracting the changed text from subset of the website.
How does that sound?
