I just wish more of these companies would add support for a locally runnable IFTTT equivalent, or at least something like MQTT support so you can bake your own.
... But they do free you from the company. And these days, ball-and-chaining you to their servers is the big "In" thing to do.
Now for me, I'm a big fan of Node-Red. It's best described as a IFTTT for your machine/network. Runs locally, and just works. I also use PageNodes, a client-only modification of Node-Red. You can use it here:
http://ipfs.io/ipfs/QmSCrZUPkqH4gsncsD7tGXPiFpymsbwmywsHXLDh...
(It's an IPFS link, and is on the permanent web. That link will always work as long as machines are hosting it.)
EDIT: Really? Multiple -1's for a valid criticism of "companies want you locked in to their network"? We just got done with Google killing off a whole platform because of extensive tie-in to 'cloud servers'. I'm just giving a converse answer how to approach the problem.
Unfortunately all of the neat IFTTT style stuff is all on their servers. They don't have nearly as many inputs and ouputs as IFTTT yet, but it is still enough to do some pretty neat stuff. They have also made it really easy to do reasonably secure stuff with your own electronics.
[1] Kind of difficult to find, because the just changed their name. http://losant.com
It ended up working, but because the comms had to go through IFTTT servers, the lag was something like 10-15 seconds, which is awful when you want to just turn on a light.