IBM® webMethods offers a hybrid, enterprise-grade integration platform as a service (iPaaS) that allows users to securely control applications, APIs, B2B and files across environments and locations.
$2,500
per month
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.
IBM webMethods was selected vs WSo2 for the reachness of the correspondign features regarding Mulesoft, the flexibility of IBM webMethods compared to the other platform, in relation to the existing architectural landscape was preferred
The two branches of the IBM integration portfolio are coming together nicely, and it's more a question of fully mapping the specific implementation requirements to the respective platform of choice when selecting between IBM Cloud Pak for Integration and IBM webMethods. …
I have seen that other products have different UI to address various business problems like messaging, EDA, MFT. IBM webMethods has unified platform and can also support hybrid Integration. I think it is all rounded iPaaS tool with ease of development and ease of operation. The …
IBM webMethods lags in terms of iPass offering as compared to mulesoft and dell Boomi. In terms of api management Apigee is much better than webMethods.
IBM webMethods is far superior when compared to competition like Microsoft Azure. In functionality and capabilities. Better visibility, uptime, efficiency, etc.
webMethods does better for end to end integrations whereas Azure is more focused on APIs. We selected webMethods because we felt their integrations, especially to mainframe environments, were much better than the others. IBM has been in this space for a long time and know it …
The webMethods platform ranks higher in our ranking because it has more features and has proven itself in many CAC 40 companies in particular.The key elements are robustness, ease of use, a clear business model, and a wide range of features covering all types of enterprise …
Oracle Integration Cloud vs IBM webMethods, hands down IBM webMethods is way better. Lots of features and ease of doing webMethods and super stable stack.
IBM webMethods combines all the essential functions for information system integration in its platform. All products are interconnected to facilitate implementation (ESB, API, BPM, message bus). All tools are easy to use.
webMethods.io IntegrationDescriptionWe uses webMethods.io Integration to solve some of our application to applications and business to business integration needs. It is the Integration Platform as a Service solution that we use in a mix with our continued use of webMethods …
Less programmatic capabilities, somewhat simpler design interface. More sophisticated events supported per task.
Ultimately, the kinds of tasks that need automation are simple, and a simple/easily maintainable user interface ensures no more time than is needed is spent on this …
Zapier is always trying to feed me information I don't want, whereas IFTTT has a clean, easy to use website. Microsoft Flow is time-consuming to set up, IFTTT isn't. In my line of work, time is very important. I need to do the work and get it done. Automate doesn't offer the …
I initially was using Zapier for some of my simple integrations but started using IFTTT for some of our project work as it allowed me to do logical connections between applications. While it's great in some areas, it can be improved upon to allow for more deep configurations.
We have used Microsoft Flow, Stringify and IFTTT for various solutions. Stringify is no longer an option as it was shut down. We have found that IFTTT and Flow both have their place and in some places working together for the same task. We have found there is no one …
IFTTT is free and easy to use, where Zapier has a freemium business model. We actually use both platforms for different things. I prefer Zapier for more complicated connections, where IFTTT allows us to have more connections without the added fee. Additionally, IFTTT allows us …
As IFTTT, Zapier also helps users to connect apps and services, but it seems more directed to the corporative world. While IFTTT provides support for home devices (as lighting and security systems) and voice assistants (Alexa, Cortana, Google Assistant, and Siri), Zapier …
IFTTT has worked better for us than Hootsuite because we utilize it spur of the moment and only have to post to one platform. Once that post is done IFTTT does the rest and we're good to go. Using the native social media apps and software has allowed us to schedule posts in a …
I am using both but for different uses. DLVR.IT seems to be opimized for social media sharing only, whereas that is only a small part of what IFTTT does.
Compared to Buffer, IFTTT has a far greater reach and scope, across numerous Social and off-site platforms. If you work in SEO, Content, or marketing in general, marrying IFTTT with Buffer will provide functionality you otherwise pay for.
Office 365 has a program called Flow that functions similar to IFTTT, however, IFTTT has more integrations with 3rd parties and Flow has problems with getting triggers to go off properly. Unless there were some corporate requirement to utilize Flow only or limit integrations, I …
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 …
In my mind, the only real competitor to IFTTT is Zapier. Zapier is great because of the amount of SaaS tools that it has, but Zapier fails in the ease of use category. Zapier's website is slow, and the integrations can be confusing to set up. IFTTT is simple, easy to use.
In the past, I have run scripting on a Linux server to provide some level of integration of some of the smart devices in the workspace. This had always been cludgy and at times unreliable as it oftentimes fell victim to idiosyncrasies in the devices being controlled.
IFTTT …
Zapier is a more in-depth if-then statement builder with way more detailed integrations to hundreds of applications as well as different tasks that can get implemented within your if then, then that statements. Way cooler and there are certification options that help you get to …
While other paid services might give your a little extra features and possibly a connectivity with enterprise application, it's nearly impossible to beat IFTTT with the cost factor, ease of use, hundreds of channels and a great community of users.
IFTTT has the most integrations, the least bug recipes and it is the cheapest alternative. IFTTT has also been in the game for years. Automation for the people! You cannot get the kind if ideas from any other integration site, and many are missing key apps like Instagram or …
Truthfully I use both of these products. IFTTT is a very robust app but it does not get any where near as robust as Zapier. But although Zapier is more robust, for simpler tasks IFTTT is not only easier to set up, but gets the job done just as well. And now that IFTTT is …
IFTTT is great for personal, home-life use, as it targets social media, personal email preferences, and home-automation devices. Zapier is much more business-oriented and does not provide integrations with Amazon Alexa or WeMo home devices.
With its world-class proven technology, the IBM webMethods products are best suited for solving integration needs, including application connectivity, data aggregation, and data synchronization. The business use cases expand across Healthcare, Aviation, Banking, Insurance, etc., and many other mission-critical systems. Though I feel there is room for improvement where webMethods products are utilized in a containerized platform, especially with the API Management suite of products.
IFTTT is a great tool for people wishing to integrate different productivity tools, but who lack the resources and/or knowledge about programming these connections themselves. Anyone who uses at least email, calendar and social networks on a regular basis can benefit from IFTTT. However, it probably won't be appropriate and/or relevant to casual users, or users inexperienced with the many possible links between smartphones and online apps.
Their UX and UI for creating recipes is brilliant. So easy to use and very well thought out.
I love that you can search for recipes other users have created and implement those if you choose to do so. It saved me so much time vs. having to figure certain recipes on my own.
Their notification and syncing options are spot on. I love how much I can customize what I want to see. Their variety of apps is also phenomenal and I love that they're adding new integrations/apps every week.
The webMethods platform is a fantastic tool for modernizing information systems. It's easy to use and delivers rapid results.The platform is focused on innovation and is accelerating its improvement with the acquisition by IBM.
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.
The webMethods product has a very user-friendly and easy-to-use interface.A weak point is the My webMethods Server portal (administration and monitoring portal for the on-premise platform). This weakness has been addressed thanks to the control plane on the hybrid version of the product. This version should be highlighted and used to ensure a very fluid and functional interface.
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
The webMethods platform is very stable and does not cause incidents: if it is well configured and tailored at the base. Infrastructure incidents represent 20% of incidents (full disk, memory peaks, etc.) 80% of incidents come from the implementation of the code in the platform. If a code is not optimized and a high volume is observed in production, this can cause incidents. Similarly, if all error cases or conditions are not handled in the code, this can cause errors. Finally, there can be common errors if the applications connected to the platform do not return quality data or are unavailable.
The webMethods platform is designed to handle a high volume of small messages. It's a tool for continuous processing.The incidents I've seen involving application performance declines are caused by: - Code optimization issues - File size issues or fragmentation of the transmitted file - Misuse of the platform (batch processing) - Monitoring data was not purged, and the user was working with millions of data points
In the majority of the tickets I've created, support has been very responsive and provided the right solutions or solutions.Resolving a ticket also depends on the information provided by the creator. It's important to provide the technical context and information about the environment, as well as information to help the support team reproduce the incident.
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 received in-person training from the webMethods team. We received standard training from the vendor and custom training on specific security topics.The training sessions went well but remained very standard and did not adapt to the client's specific business. In-person training is more suitable for rapid skill development. It is necessary to practice for a few weeks to ensure familiarity with the tool.
I found clear and easy-to-follow training with realistic use cases for quick understanding and a 360° view of the features. The lesson format allows you to progress and learn by breaking down the allocated time.The technical courses are described step by step, allowing you to quickly get to grips with the products
When implementing webMethods, it's essential to have the right support and guidance.It's important to map out the interactions, document them, prepare test cases, and implement them while making maximum use of the product's native features.Additional tools must also be planned to automate deployments, visualize logs, and monitor the platform.
The two branches of the IBM integration portfolio are coming together nicely, and it's more a question of fully mapping the specific implementation requirements to the respective platform of choice when selecting between IBM Cloud Pak for Integration and IBM webMethods. Pricing and licensing model, cloud strategy, and level of distributed responsibilities and ownership of integration in the organisation can be deciding factors.
IFTTT is free and easy to use, where Zapier has a freemium business model. We actually use both platforms for different things. I prefer Zapier for more complicated connections, where IFTTT allows us to have more connections without the added fee. Additionally, IFTTT allows us to do more unique and one-off automations.
webMethods.io Integration is a cost effective approach to integration in isolation
webMethods.io Integration as a supplement to on-premises integration is pointless and redundant and just adds complexity to the environment and additional costs
webMethods.io Integration is a tough sell for organizations using Microsoft Azure integration products such as Logic Apps
webMethods.io Integration has a faster time to market where the use case means standard provided adapters can be used
IFTTT was a free program for us and has worked wonders.
The time that it saves us when it posts across platforms is great because we only have to post one picture and caption and it goes out to all of our social media accounts.
IFTTT has definitely helped us to communicate more and in better ways.