AFAIK, there are several parts to IFTTT:
- Web Server to hold and process all the "Recipes" and "Dos"
- Apps (Web, iOS, Andriod etc) to both create the "If" and "Do" Recipes (see attached pics of examples of the two types)
- Integration with dozens of exisitng IOT devices
I see a couple of options:
- Make JRiver Media Center and Smart Theater IFTTT compatible
- Use the IFTTT calls to control IFTTT compatible devices from JRiver Smart Theater (eg a user whould then not need an IFTTT account as you would control these devices directly, eg it would use the IFTTT Calls to the devices directly).
From Wikipedia
IFTTT employs the following concepts.
Channels are the "basic building blocks of IFTTT",[21] they mainly describe a series of data from a certain web service such as YouTube or eBay. It can also describe some actions controlled with certain APIs like SMS. Sometimes, it can represent information in terms of weather or stocks.[22] There are particular triggers and actions in each channel.[23]
Triggers are the "this" part of a recipe. They are the items that "trigger" the action. For example, from an RSS feed, you can receive a notification based on a keyword or phrase.[6]
Actions are the "that" part of a recipe. They are the output that results from the input of the trigger.
Recipes are the predicates made from Triggers and Actions. For example, if you like any picture in Instagram (trigger), the photo will be sent to your Dropbox account (action).[21]
Ingredients are basic data made available from a trigger. For example, the data that are available from the email trigger include subject, body, attachment, received date, and the sender’s address.[21]
