webMethods.io Integration (formerly webMethods Integration Cloud) from Software AG is designed to make it easy to connect SaaS apps and make business processes more efficient. It enables enterprise subject matter experts and eliminates integration silos, allowing users to integrate applications hosted in public or private clouds, as well as applications hosted on premises.
N/A
Workato
Score 8.2 out of 10
N/A
Workato is a cloud or on-premise automation and integration platform with enterprise-grade
capabilities and no coding required. Workato provides pre-built connectors to integrate with over 300
business applications and enables task automation across apps.
We don't use webMethods.io Integration for scenarios where we need to integrate to on-premises legacy applications that have limited support for modern security controls such as OAuth 2.0 and transport encryption. Likewise, we don't use it for solutions that involve any of our systems that are controlled by safe-working processes. For those scenarios, of which we have many, we maintain on-premises webMethods Integration Server and Trading Networks instances to build and execute and support and monitor those solutions. This then requires us to hook our on-premises integration platform up to the webMethods.io Integration cloud, to ship messages between the two integration platforms. This all begs the question if a cloud solution cannot be used for all use cases or scenarios that the business has, then why add the complexity of using the cloud at all if you still need to maintain an on-premises solution to support the non-cloud appropriate scenarios.
Workato is brilliant to make separate applications work together without much effort or specialists being needed. When specific events on software A should trigger actions on B (or more) and you want that to happen without any development or big budgets, that's where Workato comes into play. It's a great help if you want tasks automated, communications flowing and data synced between different applications.
The Workato product interface is brilliantly thought through and designed. The learning curve for first timers is easy enough to get started and build useful things, and Workato really shines in their ability to handle complex triggers and interactions. Workato allows people to build software apps so much faster than by coding each functionality.
Workato has fantastic documentation, making things accessible without any holes in the product. The product just works, never has any bugs, never lags, and just generally allows us to see and change exactly what we need to.
Workato has an absolutely amazing support team. We tried the free version for a while, then realized it was the single most important software tool we have, and we upgraded. The support at the paid tier is A+, seriously the best from any company we've worked with. Feels more like a good friend then a support rep.
Customer support - responsive, but often not equipped to help efficiently identify root cause of issue. Need to improve escalation to technical resources and turnaround time
Recipe organization and sharing. Can be challenging to copy recipes, or grab recipes from publicly available site. There are often dependencies and errors that have vague descriptions.
Due to prebuilt recipes, Workato is easy to learn and use for non-technical users if their use case fits the existing recipes. It is not easy for non-technical users to create, modify, debug or maintain complex integrations that are outside the prebuilt recipes.
They employ an extremely knowledgeable team of problem solvers. I've never had a disappointing interaction or one that has left me still searching for answers. I know that when I ask for help, they'll partner with me until we find a solution together
We discovered that we could not use Workato for our more complex, large enterprise integrations. It was useful for simple workflows that matched the prebuilt recipes.
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 Integration Server and Trading Networks on-premises. For any solutions that meet the use cases that we deem an appropriate fit for running in the cloud, we build those solutions using webMethods.io Integration. More specifically, we use webMethods.io Integration to synchronize changes in one application or system, in another application or system, by shipping data mutations via integration messaging and API calls. We also use webMethods.io Integration to integrate with external organizations. Our trading partners and supply chain partners provide APIs that we consume, and vice versa, to notify each other of business process events as they occur in the respective organizations. Please provide some detailed examples of things that webMethods.io Integration (webMethods Integration Cloud) does particularly well. Easy to usePriced competitivelySupports robust and resilient integration solutions please provide some detailed examples of areas where webMethods.io Integration (webMethods Integration Cloud) has room for improvement. These could be features that are hard to use, missing functionality, or just things that you'd like to see done differently. Complex logic is hard to understand in a simple diagrammatic user interface too simplistic for solutions that are complicated or go against the gain runtime observability could be improved please describe some specific scenarios based on your experience where webMethods.io Integration (webMethods Integration Cloud) is well suited, and/or scenarios where it is less appropriate. We don't use webMethods.io Integration for scenarios where we need to integrate to on-premises legacy applications that have limited support for modern security controls such as OAuth 2.0 and transport encryption. Likewise, we don't use it for solutions that involve any of our systems that are controlled by safe-working processes. For those scenarios, of which we have many, we maintain on-premises webMethods Integration Server and Trading Networks instances to build and execute and support and monitor those solutions. This then requires us to hook our on-premises integration platform up to the webMethods.io Integration cloud, to ship messages between the two integration platforms. This all begs the question if a cloud solution cannot be used for all use cases or scenarios that the business has, then why add the complexity of using the cloud at all if you still need to maintain an on-premises solution to support the non-cloud appropriate scenarios. What positive or negative impact (i.e. Return on Investment or ROI) has webMethods.io Integration (webMethods Integration Cloud) had on your overall business objectives?webMethods.io Integration is a cost-effective approach to integration in isolationwebMethods.io Integration as a supplement to on-premises integration is pointless and redundant and just adds complexity to the environment and additional costswebMethods.io Integration is a tough sell for organizations using Microsoft Azure integration products such as Logic AppswebMethods.io Integration has a faster time to market where the use case means standard provided adapters can be used describe how webMethods.io Integration (webMethods Integration Cloud) stacks up against them and why you selected webMethods.io Integration (webMethods Integration Cloud). For any organization which is already using Software AG products on-premises, such as webMethods Integration Server and Trading Networks, or Universal Messaging, evaluating and using webMethods.io Integration is the path of least resistance. It will be incredibly easy for your webMethods team to get up to speed on how to use webMethods.io Integration, and start developing new solutions on it. However in my opinion you should only add cloud to your integration product portfolio if you believe you can move 100% of your integration needs to the cloud. Otherwise, you will need to maintain an on-premises integration solution anyway, which means you end up with a more complex IT landscape by adding cloud to supplement on-premises integration for little benefit in terms of cost, complexity, and resourcing requirements. For organizations that are not already a Software AG shop, you should evaluate webMethods.io Integration on its merits, however, it's usually the right decision to double down on your existing products and vendors if you have no big issues with the current state. This is to say that if you are a Microsoft shop then adding Azure cloud products to your portfolio is pretty much inevitable, and avoiding the complexity of multiple clouds should also be something organizations consider.
We already used Zapier, but since it doesn't support NetSuite we had to choose another automation platform. Now that we've been using Workato for a few months, we have plans to move the stuff we're going through Zapier to Workato. We set up a trial account with all the other platforms, and they were all more expensive and A LOT more complicated than Workato.
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
As business consultants, Workato has greatly improved our offerings to our clients as well as improved the time frame to implement automated workflows and integrations.
For our clients, the return on investment is almost immediate. Once a Workato recipe is up and running (which can be done very fast), data is integrating, duplicate data entry and user errors are eliminated, and cross-company KPI metrics are easier to report than ever.
