- I’m attempting to recreate something I’ve managed to do with both Zapier & IFTTT in n8n.
This being read one or more RSS feeds and post to a(Google Chat) channel.
The example Split In Batches | Docs seems to be only half of the solution as it doesn’t show where to send the data that you have split…
Can anyone point me at how to make that happen?
- I’ve worked out the json for sending to the Google Chat webhook to that below, but the http request node is a bit cryptic on how to send the nested arrays.So how do I make that happen?..
---- The variables are those listed in the IFTTT RSS parser (although that’s a bit hit and miss), and this does work if I send it from a shell using curl
"subtitle": "EntryAuthor - EntryPublished",
Welcome to the community!
I have modified the Example Workflow and added the HTTP Request node to the workflow.
If you run this workflow you will notice that we are getting output for each article.
Hope this helps.
Yes it is helpful thanks
So this gives me a set of fields from the RSS:
but how do I feed that into the json I posted earlier?
(as in the value for EntryContent/EntryTitle/etc)
I’ve signed up with pipedream.com to determine what is actually being sent.
Actually, I appear to have figured out how to set the parameters.
So I’m seeing the correct json at the pipedream end.
Next to look up how to not flood gchat with the same messages! (I’ve seen it somewhere)
Actually, there are 2 things:
- how do I rate limit the http requests to the destination? (so that google doesn’t block me)
- how do I not send the same RSS articles more than once? (adding a mongodb/database node or something??)
So this seems to work and has the card formatting as I’m expecting it.
Obviously, replace the destination webhook with the one you get from the gchat interface.
The httprequest might be trying to send 2 lots of data though, so I’m not sure if this is 100%working.But then I’ve only been trying it out for 3 days.
so the issue I’m having is that one of the feeds has more html in the contentSnippet parameter, with extra double-quotes which confuse the parser.
but it works great for the first feed