IBM’s App Connect is a cloud-based data integration platform with data mapping and transformation capabilities within connectors between high-volume systems. App Connect also offers near-real time data synchronization and an API builder that is adaptable to the user’s coding skill level.
N/A
IFTTT
Score 6.7 out of 10
N/A
IFTTT is a marketing automation software solution offered by IFTTT. It is scaled for non-technical
users and less complex, generally two-step connectors and API’s.
- great when you need to integrate applications without any message lost or duplicated and when transnationality is important - if you need the highest throughput possible and not much (or not at all) mapping is required, a system like Kafka is more appropriate
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
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.
The development and the transformation capability is not so great. I believe IBM is looking to incorporate some of features of IBM APP Connect into API Connect.
The authentications features are no way close to CA API Management (f.k.a Laye r7).
The development experience is not as good as Apigee's.
The GUI should be improved. Maybe the product team should see the other API management tools in their offering.
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.
It is the best on-premise application to cloud integration in the market. I guess IBM is planning to integrate IBM App Connect with the IBM API Connect solution.
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.
You can do some really powerful things with this system. The overall design is an attempt to make configurable some of the routine tasks/common functionality, but allow for development/customization of the core of the application.
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
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.
We did not select Cast Iron as our iPaaS solution, it was the weakest competitor in the field that we evaluated. Our experience was that it was not nearly as easy to learn, without in-depth training and guidance, and the developer UI was extremely buggy. We subjected each of the vendors to a battery of integrations, from simple to challenging, and it fell short on each one. One of the most simple integrations was grabbing a CSV file from an FTP source, parsing the data, doing a small amount of transformation, then inserting that data into an Azure MSSQL DB. After 2 hours on the phone with the Cast Iron support team, we were still unable to get this working.
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.