IFTTT Twitter triggers are back!

Update – 5/20/2014 –

IFTTT has restored Twitter triggers. By using a Max Twitter client: https://reactivemusic.net/?p=7013 you can now connect Max with IFTTT

A possibility with curl

http://blog.tomdoggett.net/2013/05/ifttt-recipe-http-commands.html

A few notes…

It doesn’t appear that IFTTT has a public API.

One method would be to use intermediaries for example – sending email using php (see this post https://reactivemusic.net/?p=4840) Then IFTTT could pick up the trigger – for example, from gmail. Commands could be embedded in the subject or body of message.

Or you could simply use Twitter as the intermediary – using existing internet sensors methods: (see this post: https://reactivemusic.net/?p=5859)

Would this work in reverse?

Other methods:

temboo: The temboo API should be accessible via Max using a ruby server. Temboo has many common points of interaction with IFTTT

mashape: I think the same applies as with temboo.

Marcus Povey describes a workaround using web hooks: http://www.marcus-povey.co.uk/2012/11/07/using-webhooks-with-ifttt-com/

Another idea: http://forums.getpebble.com/discussion/5816/restful-api-iftt-integration-android

Or what about Zapier

Here’s an article about IFTTT Twitter triggers: http://iag.me/socialmedia/how-to-replace-ifttt-twitter-triggers/