[sawyer]

Very interesting idea I hadn't heard of yet; does anyone know how they deal with services that do not have APIs conducive to this type of application? Or are all of the recipes pre-constructed by the IFTTT team to be sure the data in/data out constitutes a valid use of the service APIs in question?

[sathyabhat]

There are some existing recipes, however - you as a user aren't restricted by those recipes. You're free to create any recipe with almost any API supported by IFTTT as long as there are valid trigger points.

[kmfrk]

It's also worth mentioning that your tasks apparently can get turned off. It happened to me when I had a Twitter account tied to an RSS feed where no updates were posted in a couple of days. Bam, task automatically shut down.

It seemed a bit weird and was completely unexpected, so I probably wouldn't rely too much on it initially, until you have used it for a while.

[linden]

Sorry to hear your task got turned off. You should have gotten a notice via email about it. We monitor tasks that have trouble running (in this case perhaps the feed was down?) and always make sure to ping the task owners about it when we turn them off.

[kmfrk]

I got the e-mail, but the only take-away I got from it was sad trombone.

From what you're saying, you did it as a service to me, the user, and not to yourselves to save resources, which is what the e-mail notification sounds like - which annoyed me a bit, I have to admit.

I'll give it a second shot and send you an e-mail when or if it happens again. :)

[linden]

Ok sounds good. Perhaps we need to revisit the tone in that email, it IS intended as a service to you. If something isn't working as expected we wanted to make sure you knew about it. Its on us to make sure to get you more precise information about what is going wrong. Thanks for the feedback!