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
Workato
Score 9.1 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.
N/A
Zapier
Score 8.8 out of 10
N/A
The Zapier Automation Platform designed to integrate data between web apps. It is scaled for small to mid-sized businesses, with a functional but limited free version of the program.
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 …
We were able to get into contact with Workato faster, and at the time preferred the native integrations offered in Workato compared to Zapier. As of today, their offerings are much more similar.
Workato is much simpler to learn and configure than Dell Boomi. While powerful, I struggled with Boomi's interface. I know Boomi is powerful and trusted by many enterprises, but it seems a little inaccessible to me - the learning curve is a little too steep and I don't have the …
From what I could see, Zapier was very limited against what Workato was offering. The model of Zapier, at first sight, was very easy to understand: you pick 2 connectors and create a process in the middle, but that's where Workato made the difference, on how easy the recipe …
Zapier was great for simple integrations, however, error handling and recipe writing isn't as strong. We also found the pricing to be deceiving once working on more complex integrations.
Zapier's integration tools are impressive, especially considering the cost. Their connectors are lacking functionality vs Workato, which ultimately leads to more development time and cost. Workato's built-in functionality, like lookup tables, are extremely impressive. They …
Verified User
Supervisor
Chose Workato
Workato is much more advanced than Zapier, and although less apps/integrations are offered - but the ones offered are really deep ones. This is also geared towards enterprises is what I believe whereas Zapier focuses more on SMEs and Mid-Market. Although learning curve is steep …
Workato is definitely the easiest tool to work with. We found other tools more challenging when there are no pre-built connectors, and it requires coding knowledge to extract objects from JSON payload for example. In Workato, the payload is auto parse and each object can be …
Workato beats the competition pound for pound, not even close. It's a much more enterprise-grade tool, designed from the ground up to be stable, solid, and secure. The other tools I've tried were either buggy, lacking in capability, felt like toys, or were really hard to scale.
Verified User
Director
Chose Workato
I use Workato for the full view of my process. Both the console on errors and debugging as well as the unified view of each task I'm automating. In addition, I know that Workato has all the power necessary for enterprise integration.
A market leader when it comes to an out of the box/do it yourself integration tool. It is very user-friendly with an excellent track record for new connectors and reliability.
We found Workato to be easier to use, more powerful and more robust than other solutions we tested at the time. It simply does the trick and allowed us to implement all that we needed in all the precise details we needed. It gave us all the power, flexibility and autonomy we …
Founder and Growth Hacker at Big Red's Equipment Sales
Chose Zapier
PieSync is historical real-time 2-way syncing. It doesn't get any better than that. However, Zapier has way more connectors, so there is a place for both. Workato looked robust, but was really lacking on triggers and actions, and it cost more than Zapier and PieSync combined. …
The only other major alternative we've tried against Zapier is Workato. Workato was great and had a lot of features, but was a bit overkill for what we needed. It was definitely more feature-rich, but it was also 3-4x the price and we didn't really need all the features it …
Zapier, in my opinion, is more user-friendly than Workato. Their pricing is also much better. I believe Workato's ability to handle complex steps may be superior to Zapier, but not by much. I chose and continue to choose Zapier because of its overall presentation, usability, …
In any scenario where a distributed enterprise IT landscape needs a unified approach to solve the challenges of enabling a common information supply chain where different stakeholders as well as citizen developers can be empowered to contribute, participate and own their own parts of the integration landscape - IBM webMethods offers a capable, architecturally sound and cost efficient way of supporting a wide range of enterprise system integration needs.
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.
If you have processes that are now managed and controlled using a spreadsheet, Zapier will give you a lot more control over what is happening and will help you increase productivity by eliminating simple steps such as sending emails and sharing information with your colleagues. It frees time for very transactional activities.
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.
Ease of use - multiple people in the organization can set up and run Zaps per their specific use cases without much training.
Connectivity - Zapier is able to connect to multiple applications we use on a regular basis.
Functionality - Zapier provides embedded functionality within the app itself (email, data conversion), but also appropriate triggers and actions for apps it connects to.
Versatile - Zapier can execute complicated and simple tasks and thus has many use cases.
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.
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.
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.
The sheer work Workato eliminates from people's daily jobs is simply a great contribution to people's productivity and a boost to capability. It actually strikes the balance between business and tech teams. It also reduces dependency on developers, and speeds up their delivery too. The only reason it's not a full 10/10 is for the price - it's a bit expensive for what we'd like, and their batch or high data volume processing can be improved.
The interface is very user-friendly, and there are also many tools to help a brand-new user get started. For example, you can put your Zap idea into the AI bot, and it will basically build a shell of your Zap to get started on. The format for each step within a Zap is also very helpful (set up the connection/app, set up the fields/details, then test).
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.
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
Before we purchased Zapier, I contacted support and asked them if Zapier could support my intended workflow (this is actually a selection on their support form - awesome). Within 2 hours, I was contacted by a support team member who seemed sure it would work, but granted me premium access for 2 weeks to try it out for myself. Sure enough, it did! Ever since then, support has replied rapidly to any problems I have experienced and answered my questions within a few sentences.
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.
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.
We actually utilize both Integromat and Zapier at our company, for all the reasons detailed in this review. Though Zapier is excellent for simple client integrations, we often run into internal use cases that require complexity that Zapier cannot provide. Specifically working with API calls (not just webhooks), complex multi-step integrations with Routing/parsing/etc, and large volume integrations. Integromat is perfect for these use cases, but doesn’t provide the simplicity and account scalability that Zapier offers.
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.
