https://github.com/ottawaruby/whenbot

A simple personal ifttt.com clone
https://github.com/ottawaruby/whenbot

Last synced: 3 months ago
JSON representation

A simple personal ifttt.com clone

• Host: GitHub
• URL: https://github.com/ottawaruby/whenbot
• Owner: ottawaruby
• License: mit
• Archived: true
• Created: 2012-02-28T17:17:15.000Z (over 12 years ago)
• Default Branch: master
• Last Pushed: 2015-08-11T23:51:44.000Z (over 9 years ago)
• Last Synced: 2024-03-26T01:49:28.338Z (8 months ago)
• Language: Ruby
• Homepage:
• Size: 303 KB
• Stars: 225
• Watchers: 43
• Forks: 54
• Open Issues: 2
• Metadata Files:
  • Readme: README
  • License: LICENSE

Awesome Lists containing this project

README

        
Whenbot - a personal open source ifttt.com clone. (check out

http://ifttt.com)

Whenbot is no longer supported!

Wiki page with more info: https://github.com/ottawaruby/whenbot/wiki/_pages

simple luuunchbot app: https://github.com/redronin/luuunchbot

The idea: A simple web service that runs on Heroku that lets you

listen on certain triggers and perform actions to other web services

based on that.

For example: Whenever I post an Instagram photo, create a Tumblr blog post.

It would be personal - in that it's meant for each person who wants to

run it to clone the repo, and host it on their own Heroku instance.

Heroku provides enough free addons and services that you can get it up

and running and functional without paying for anything (or at the

most, a few bucks a month).

Basic premise is that you have:

Triggers - things that you listen on (new instagram post, a tweet, a

new email, a new RSS feed entry, etc.). This can be a scheduled

polling to a certain API endpoint (heroku offers regular schedule

tasks every 10 minutes), or webhook endpoints.

Parsers - things that take the output from a trigger, and

massages/normalizes the data into a known format that can be consumed

by...

Publishers - things that you publish to (send a tweet, create a Tumblr

post, send an email, etc.)

The basic engine could be a very simple app, and the Triggers,

Parsers, and Publishers can be individual modules/classes. This would

allow people to work on various triggers, publishers, etc. on their

own while still contributing to the project as a whole. There'd also

be UI work to create the actions, configure services, etc.

Most triggers and publishers would just be using various API wrappers

for web services like Flickr, Tumblr, Posterous, etc. This would be a

great way for people to get exposed to APIs from various web services.

Some are complicated, some are pretty simple, so there'd be lots to

choose from.

I created a simple Instagram => Tumblr / Posterous app for

http://luuunch.com which I could show. It uses a ridiculously simple

Tumblr publisher, Posterous publisher and an Instagram webhook

trigger.

An immediate use case for something like this would be to create an

instagram / flickr / etc. feed to add to the OttawaRuby  website.