Automation tool IFTTT cuts Twitter triggers in wake of API violations

ifttt no twitter

With Twitter’s API guideline changes, popular mix-and-match app pushing service IFTTT is now among the services that have been dealt a blow. If you have recipes set up that include Twitter as a trigger, you’ll find them disabled come September 27.

IFTTT sent out an email yesterday notifying its users of the upcoming changes due to the enforcement of Twitter’s new API guidelines. While Twitter Triggers (an IFTTT feature that works by pulling Tweets from Twitter’s cloud onto other services) has been restricted, IFTTT will continue supporting the ability to publish Tweets.

The Twitter guideline that IFTTT specifically refers to, and that the service is affected by, is section 4A: “Exporting Twitter Content to a datastore as a service or other cloud based service, however, is not permitted.” Instead, Twitter data can be extracted as a spreadsheet or PDF, both which are rudimentary forms of storing information that would be not be wise to be implemented into any third-party services. Does anyone really want an excel sheet of tweets?

In the email sent to IFTTT users, the company explained its respect for Twitter’s decision. “We’ve still got a long way to go, and to get there we need to make sure that the types of connections that IFTTT enables are aligned with how the original creators want their tools and services to be used,” IFTTT’s CEO, Linden Tibbets, wrote in the email. Many other third party developers, however, don’t share the same sentiment about Twitter’s latest moves.

Last month, developers and Twitter users expressed their discontent with the new changes through a petition to “protest” Twitter’s restrictions to its API. Services like Tweetbot were forced to shut down new feature implementations in the wake of the API changes, while other developers have resorted to filing complaints with the Federal Trade Commission asking them to review Twitter’s restrictions.

IFTTT’s situation might doesn’t quite bear the same significance as other shut down apps, however. As TechCrunch first pointed out, based on the Twitter policy, which has been outlined above with regard to exporting Twitter content, IFTTT may have been violating Twitter’s Terms of Service policy all along.

The changes are going to affect many IFTTT users considering the popularity of the platform, but until the end of the month rolls around, you’ll have time to figure out what recipes you’ve created with Twitter as the trigger. Luckily IFTTT says it will continue to build for Twitter. “We’re sad to see [Twitter] go, but remain excited to build features that work within Twitter’s new policy,” Tibbets added.