Posted on 09-13-2011
I believe that REST and JSON are breaking up the web, into smaller more understandable, re-usable, mashable pieces that potentially anyone can use, even non-developers.
I have written several posts on how tools like API explorers and standards like oEmbed are making APIs accessible by non-developers. And I’m always on the look out for new ideas, for new ways to arm the masses with tools that take advantage of APIs.
Evolving on a piece I wrote a couple a months ago about a Widget Builder Environment for APIs, I was envisioning taking Yahoo Pipes to the next level, add in better API support with OAuth, and make it much more simpler to use. I did not get much time to think about it before Audrey introduced me to if this then that (ifttt).
ifttt allows you to creates tasks. Tasks are defined like this: when something happens (this) then do something else (that).
- this (triggers) - The this part of a task is the Trigger. Some example Triggers are "if I'm tagged in a photo on Facebook" or "if I tweet on Twitter."
- that (actions) - The that part of a task is the Action. Some example Actions are "then send me a text message" or "then create a status message on Facebook."
Triggers and Actions come from Channels. Channels are the services and devices we use every day, such as: Twitter, Facebook, Instagram, Email, Phone Call or Weather.
You can put one channel's trigger together with another channel's action to create a task that runs every 15 minutes and can be turned on and off.
Channels are made possible because these services have APIs. ifttt does a remarkable job at simplifying this in a way, I never even imagined, and allows any user to take advantage of two APIs, apply meaningful business logic, and automate the task to run regularly.
What really makes it cool is you can save tasks as “recipes” and share them with friends making this type of API usage and automation a potentially very social thing.
Right now it appears that the ifttt team creates the new channels that are available. Think of the possibilitis if they opened it up to developers to build their own channels and recipes, and created a marketplace of these API automation recipes?
if this then that (ifttt) is pretty cool! I will be playing with more and incorporating into my daily operations, and see if we can make it stick.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Sales, Onboarding And Support In A Self-Service API World
- An API For Developers To Access Their API Account Information
- My Continued Support As Signer Of Oracle v Google Amicus Brief From EFF
- Join Me Tomorrow For A Panel Discussion On API Ecosystems At SF MusicTech
- I Will Review Your API On API Evangelist if You Add An APIs.json File Plus A Machine Readable API Definition
- Hey, Why Isn't This (API) Free
- Resource Base API Monetization vs. Experience Based API Monetization
- Tracking On The Red Flags For API Monetization
- Project Idea: Codenvy-Like Containerized Spreadsheets
- Messente API: Always Use A Backup DNS Solution