RSS Trigger [GOT CREATED]

Feature Requests (done)
1

We need an RSS Trigger, e.g. for Crunchyroll news and so on

Rss new item trigger
2

Oh didn’t saw that I could use a rss reader 
 But anyway I think it would be better if it would be a trigger because then new users wouldn’t have any difficulties and can just use it simpler

2 curtidas
3

Agreed Zapier has an RSS trigger that executes whenever news comes in - this is much nicer than running on a cron schedule

EDIT: Looks like @Jon created a community node - awesome! I’m happy to be a guinea pig on this one.

Links:

1 curtida
4

I did indeed make one, I have been using it to keep an eye on some software update feeds and the wtf1.com news feed :slight_smile:

2 curtidas
5

Hi @Jon ,

I am using the n8n-nodes-rss-feed-trigger, everything works fine, but when I go to activate the workflow, I get the following error:

image
image331×143 5.36 KB

I am forgetting something?

Thanks in advance

Information on your n8n setup

  • n8n version: 0.214.0
  • Database you’re using (default: SQLite): SQLite
  • Running n8n with the execution process [own(default), main]: own
  • Running n8n via [Docker, npm, n8n.cloud, desktop app]: Docker
6

Hey @martinhache,

Can you try restarting your container and seeing if that helps?

2 curtidas
7

Thank you @Jon

Solved. That was it.

:wink:

1 curtida
8

Hey @jon, what do you mean by “restarting your container” ? I get the exact same error of @martinhache

9

Hey @comedepreville,

Welcome to the community :wave:t2:

Pretty much what it says, restart the container. This is assuming you are running in docker if you are using npm it would just be a case of restarting n8n.

10

Loud and clear. Thanks @Jon !

1 curtida
11

Hi @Jon,

Could it be that with the last update to 0.221.2 the n8n-nodes-rss-feed-trigger does not work correctly?

I have restarted the container and the parameter “pollTimes” does not appear in the node.

image
image391×248 7.54 KB

image
image331×143 5.36 KB

Thanks in advance

Information on your n8n setup

  • n8n version: 0.221.2
  • Database you’re using (default: SQLite): SQLite
  • Running n8n with the execution process [own(default), main]: own
  • Running n8n via [Docker, npm, n8n.cloud, desktop app]: Docker
12

Hey @martinhache,

There was a change in 221.0 that stopped the poll times from being displayed, This should be resolved in the next release.

1 curtida
13

Perfect!

Thank you @Jon

14

like @Jon said, I restarted my container, after the installation of the plugin, and after the creation of the node but still have a problem when I try to activate the workflow

My setup is

  • n8n Version 0.221.2
  • RSS Feed Trigger v0.1.3

Workflow could not be activated:

  • There was a problem activating the workflow: “Could not get parameter “pollTimes”!”

it that package still maintained?

15

Hey @JOduMonT,

The fix is in 0.222.0 of n8n so you would need to do an update. As far as I know the package is still maintained, I have not made any updates for a while to is as it doesn’t need any. It looks like the message in your screenshot is an npm error and not related to the package.

1 curtida
16

Sorry I mixed up version semantic for once.

1 curtida
17

Thank you @Jon. This is awesome! Self hosting and using your rss trigger has saved me $$$.

1 curtida
18

That is always good to hear and welcome to the community :raised_hands:

19

Hi there, I am using the self-hosted version n8n 1.0.5 and the same issue happens again

Workflow could not be activated: There was a problem activating the workflow: “Could not get parameter “pollTimes”!”

What should i do?

here is the code i copied from n8n;

{
“meta”: {
“instanceId”: “MASKED ID”
},
“nodes”: [
{
“parameters”: {
“feedUrl”: “Torrent Invites - #1 To Buy, Trade, Sell Or Find Free Tracker Invites!”
},
“id”: “MASKED ID”,
“name”: “RSS Feed Trigger”,
“type”: “n8n-nodes-rss-feed-trigger.rssFeedTrigger”,
“typeVersion”: 1,
“position”: [
840,
580
]
},
{
“parameters”: {
“chatId”: “@MASKED ID”,
“text”: “={{ $json.pubDate }}\n{{ $json[‘content:encodedSnippet’] }}”,
“additionalFields”: {}
},
“id”: “MASKED ID”,
“name”: “Telegram”,
“type”: “n8n-nodes-base.telegram”,
“typeVersion”: 1,
“position”: [
1040,
580
],
“credentials”: {
“telegramApi”: {
“id”: “MASKED ID”,
“name”: “Telegram account”
}
}
}
],
“connections”: {
“RSS Feed Trigger”: {
“main”: [
[
{
“node”: “Telegram”,
“type”: “main”,
“index”: 0
}
]
]
}
}
}

20

Hey @tobywong080,

Try restarting your n8n instance again, I had to do it with my instance before it appeared again.

2 curtidas