Interesting. None of these things compel me to use IFTTT.

True, IFTTT recipes are often too limited, because targeting non developers, they limit a lot inputs and ouputs of APIs. But all these APIs can do lot more. The reason why there we made webshell.io , "IFTTT for developers", enabling developers to script APIs in Javascript, with the whole expressivity of a a scripting language for more advanced APIs scripts(recipes) :)

The only recipe I have on IFTTT is one that watches their own Twitter stream and shoots me an email whenever they talk about new channels ;) For now, it's way too limited.

It will be always limited, because APIs are for developers, applications for humans. Only developers can levergage APIs to make advanced services.

They're not for everyone. For some, it saves time and effort immensely. Others use it for discovery. Me and you just watch from the sidelines.