IFTTT vs. WSO2 Integration Platform

Because of the multitude of options with IFTTT, it is hard to describe the best use scenarios, but I will share how I use the platform at this time. I use IFTTT to check Craigslist for certain IT equipment postings and email me if that occurs, turning items on and off with geo-fencing and WiFi network presence, and linking my calendar to my to-do list

Incentivized

The best-suited scenario is the service chain pattern or all patterns used in online mode. The less appropriate scenario is a batch service the duration time of the service is more than 10minutes because it is necessary to increase the HTTP timeout.

• IFTTT manages a number of social media accounts quite well. Being able to login to one platform with access to all your accounts is great.
• IFTTT is easy to set up. IFTTT has a number of crowd sourced and created formulas that you can use, or if you're looking for something specific you can create your own. This allows for an endless number of combinations and ways to engage with the program.
• IFTTT doesn't require constant upkeep. Once you have things setup you can forget about it and it just works.

Incentivized

• Service chain pattern
• Message transformation
• Call more than one backend service
• Call service with different protocoll as the client use
• Use file as input
• Use mail as input

• The website section "Activity" tends to get very crowded over time. It would benefit from some search and filter functionalities.
• Some services lack ingredients. "Ingredients" are attributes passed from one service to another to enhance IFTTT's power. However, some services (like Evernote's notes, for example) currently have too few ingredients available.
• It is not possible to link more than two services. It would be great, for example, to have an option to take a mail message and post in multiple social networks and blogs with the same applet.

Incentivized

• View deploy artifact in date time order
• Easy way to map data
• Easy way to manage payload

There is no better alternative and although Integromat is new and the GUI is slick, they make you pay per push and IFTTT does not. The rest of the competition make you pay per integration or are just not as seamless in usage or have the depth of catalogue. If you use Zapier for instance, it is because they have an integration you have to use, not because Zapier does a better job.

Incentivized

For the most part, IFTTT is great but it does have its limitations. You may only do one thing at a time. If you want branching logic it can be cumbersome and clunky. This it where something like Microsoft Flow does better. For simplicity, nothing can beat IFTTT for how easy it is to set up and use right out of the box

Incentivized

I have had a few issues with apps over the years. Compared to other services, ITFFF is the best choice but no service is perfect unless you build it yourself for yourself. ITFFF needs more tutorials on how to create a custom platform, but overall I will recommend it as an easy to use, time-saving service.

Just try it for your own social media platforms. Then imagine how much money it can save/make.

Incentivized

I haven't used Zapier extensively, but it seems that IFTTT is much simpler to set up. However, Zapier appears to be a much deeper integration where you can sync a variety of fields of data and customize the sync more than you can with IFTTT. Zapier may be more valuable for someone with a complex need and IFTTT is built for simple solutions for more basic apps.

Incentivized

We can start with the community version and then when we moved into production we can buy the supported version. The supported and community version have the same code so we can do every test before deciding to buy the supported version.

• We have not had to purchase a subscription to a social media automation tool.
• We have saved time sharing information between systems.
• We have been able to reach out to our clients faster because notifications are coming to our attention in more ways than just our inbox.

Incentivized

• Reduce development time to the service integration
• We can use junior developer
• Clustered in easy way