question

This doesn't look like "real" support. It all revolves around the to-do list and shopping list. Are they using the hack that went around a while ago, by keying off the url that exposes those lists? That doesn't seem all that useful to me. Since I was planning to launch EchoTTT.com, I hope they don't steal my thunder. :)

Yes, I saw that and thought it's probably a basic (right now) implementation just to get support into IFTTT quickly. When you oauth with Amazon (from IFTTT) you're asked to grant permissions on: - Access to your Alexa information (like To-do lists) to trigger recipes you create. - Permission to publish information to, and write and modify information on, Alexa in order to execute recipes you create.

I'll be interested to see if they support the Echo as the target in recipes. If I get an email, can it make my Echo announce it? I think that would be even more useful than Echo being the source.

With the new IFTTT "Maker" Channel ( https://ifttt.com/channels/maker) and the Alexa Skills Kit, it's even easier to use IFTTT as a way of rapidly prototyping new Alexa Skills. The Maker Channel allows the use of POST requests as triggers for IFTTT recipes, and allows up to three parameters to be passed along as well, making it a perfect match for Alexa Intents. I've created a basic Lambda that takes an Intent and the content of the slots and passes them over to IFTTT for use as inputs, along with an example Intent Schema, Utterances and IFTTT recipes that can be used to create a "FindMyPhone" skill that tells Alexa to ring your phone and a "Send a Text" skill that will send some common SMS messages and placed them at https://github.com/mefogle/AtoIFTTT. Any comments or suggestions are welcome!