Simple overview: This story automatically receives any updates posted to specific/specified RSS feeds for any updates to those feeds. Once an update is triggered, it will receive the feed, parse the feed for relevant data and collect snippet information. The story will then proceed to send that snippet data to my choice (in this case community social text channel), which would include date of update in the RSS feed, the date it was sent to my channel, the title of the update, a snippet of the update content, and a link to the full posting.
This Tines automation project was one of the first couple of projects I had worked on in Tines (combined with the IoT project). When first learning how to use Tines, I was essentially self-teaching myself and knew that I was going to be needing to access and use APIs (Application Programming Interface) and other HTTP/webhook requests. The best way I thought to do this was just create a basic HTTP request to RSS/XML/JSON feeds, in my case, these would be to server status RSS feeds for updates/notifications of service/server issues to whatever service in question.
Was pretty simple to get a basic story running, and after an hour or so of trial error and tinkering, was able to get a clean story setup that would automatically pull any updates posted to RSS feeds, parse the data to my specific use, and then send that data to my preferred receiver (in this case, community text channel). Other receiving options could be email, social channels, text message, or any other service that has an API receiving endpoint for custom integrations.
This Tines story utilized these concepts: