**From River4 to Instapaper, via IFTTT** [home](..) _posted 2015-11-09_ Over a year ago, I wrote about [customizing a River4 page to send links to Instapaper](http://blog.jeffreykishner.com/2014/08/14/customizeYourRiver4HomePageToSendLinksToInstapaper.html). Since then, Dave Winer has [updated River4](https://github.com/scripting/river4) so that the home page of the server will host a river (as opposed to the `index` file that lives, for example, in an Amazon bucket). I've since been reading my river on [my Heroku installation](http://jkriver4.herokuapp.com). Unfortunately, I don't want to mess with the git code for the river because every time I pull updates I don't want to have to merge code. (I don't know how!) So what I usually do when I want to save an article in the river to Instapaper is option-click on the link and then hit Control-S to save to Instapaper (courtesy of the Safari extension). Recently, someone wrote a [callback to send a river to Pinboard](http://river4.smallpict.com/2015/11/08/usingRiver4ToFlowNewsItemsToPinboard.html), and although I don't need that functionality, it got me thinking about how to simplify my process. The server river page has "share to Radio3" buttons (). Currently, Radio3 can share a link to Twitter, Facebook, Slack, and WordPress. However, it is not necessary to send a link to any of these services; Radio3 can just be used as a linkblog, and it has an RSS feed. So I set up an [IFTTT](https://ifttt.com/) recipe to add new articles to Instapaper from my Radio3 linkblog feed. Now, to send a link to Instapaper, I just click on the , tab three times and hit the Submit button on Radio3, and voila, after the recipe runs the link will show up in my Instapaper. (This is not actually any less work than my previous workflow, but it saves me from loading a heavy web page and waiting for Instapaper to indicate that it has saved the article, so it may save time.)