We performed a comparison between webMethods Integration Server and Zapier based on real PeerSpot user reviews.
Find out in this report how the two Cloud Data Integration solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The tool supports gRPC."
"The solution's ease-of-use is its most valuable feature, in which complex issues may be resolved."
"One of the most important features is that it gives you the possibility to do low-level integration. It provides a lot of features out of the box, and over the years, it has matured so much that any problem that is there in the market can be solved with this product. We can meet any requirements through customizations, transformations, or the logic that needs to be put in. Some of the other products struggle in this aspect. They cannot do things in a certain way, or they have a product limitation, whereas, with webMethods, I have never faced this kind of problem."
"Given that you have one integration API in place, it takes very minimal effort to scale it to any other application that might want to use the same. Its flow-based development environment is a breeze and makes it really easy to re-use most of the existing components and build up a new API."
"I like the stability of the webMethods Integration Server."
"A product with good API and EDI components."
"One valuable feature is that it is event-driven, so when new data is available on the source it can be quickly processed and displayed. Integration is definitely another useful feature, and B2B is one area where webMethods has its own unique thing going, whereby we can do monitoring of transactions, monitoring of client onboarding, and so on."
"The stability is good."
"Zapier luckily has a wide range of integrations, I would say."
"Webhooks are the most valuable feature of Zapier."
"Zapier handles everything under the sun that you would think you need in automation. It is the most mature integration platform and service on the market."
"Zapier is a really good tool for connecting multiple different platforms and data sources. For example, with Quickbase, I can easily integrate data from other sources like AWS or task-tracking platforms such as ClickUp or Asana."
"The connection between Facebook lead forms and MailChimp integrations is the most valuable feature."
"Zapier is user friendly and makes it easy to integrate different tools. It has a drag and drop functionality which makes it easy to connect environments."
"With the previous CRM we were using – the Google Ads landing pages we had – we were collecting leads manually. That process was not efficient and took a sales team a lot of time to insert these leads manually. Currently, the process is smooth and we use Zapier to collect the leads for us."
"There are a few valuable features, like the stability that it comes with and also the number of features that it offers. I've used other services like Pabbly, but they don't offer similar numbers of applications that Zapier has or allows to integrate with – it's maximum."
"The Software AG Designer could be more memory-efficient or CPU-efficient so that we can use it with middle-spec hardware."
"The patching of infrastructure is not very smooth and improved authentication should be added in the next feature."
"The stability of the various modules of the product suite have been a bit of a concern lately. Though their support team is always easy to reach out to, I would prefer it not come to that."
"Documentation needs tuning. There is a lot of dependency with SoftwareAG. Even with the documentation at hand, you can struggle to implement scenarios without SAG’s help. By contrast, IBM’s documentation is self-explanatory, in my opinion."
"Upgrades are complex. They typically take about five months from start to finish. There are many packages that plug into webMethods Integration Server, which is the central point for a vast majority of the transactions at my organization. Anytime we are upgrading that, there are complexities within each component that we must understand. That makes any upgrade very cumbersome and complicated. That has been my experience at this company. Because there are many different business units that we are touching, there are so many different components that we are touching. The amount of READMEs that you have to go through takes some time."
"In terms of improvement, it would be better if it adapted quicker to open standards. It took a while for API specification before the last version was available. The spec of version two was rather quick."
"A while ago, they were hacked, and it took them a very long time to open their website again in order to download any service packs or any features. I don't know what they could do differently. I know that they were vulnerable, and there was some downtime, but because they were down, we were unable to download any potential service packs."
"The UI for the admin console is very old. It hasn't been updated for years and is pretty much the same one that we started with. This is something that could be refreshed and made more modern."
"Zapier needs more YouTube or video tutorials or more training for people. That would help a lot. In particular, Zapier should have documentation for every connector. Its documentation needs to be more detailed and visual."
"After mapping them out, and they'd worked for a while, I've had Zapier fail."
"There is room for improvement in the support. They are not responsive, and they don't take much time to get resolved."
"System-to-system is fine, but when it comes to system-to-user, where Zapier is helping to communicate to a user, that's a one-way communication. If that user has to perform some action on that notification, the action isn't handled by Zapier. So there's no way to orchestrate that and it's very cumbersome."
"The user interface for Zapier could be improved. It also takes some time to sync the data between different environments."
"It is not worth the money if you have a little bit of a technical mind...Zapier is not able to set up different modules. When automation doesn't work, it's not that easy to find why it didn't work."
"It could support various languages along with Python."
"Zapier could be a little faster, but that might not be possible. I would encourage Zapier to make more API endpoints for each application"
More webMethods Integration Server Pricing and Cost Advice →
webMethods Integration Server is ranked 3rd in Enterprise Service Bus (ESB) with 60 reviews while Zapier is ranked 10th in Cloud Data Integration with 40 reviews. webMethods Integration Server is rated 8.0, while Zapier is rated 8.6. The top reviewer of webMethods Integration Server writes "Event-driven with lots of helpful formats, but minimal learning resources available". On the other hand, the top reviewer of Zapier writes "A tool for automation purposes requiring an easy initial setup while offering a very helpful technical support team ". webMethods Integration Server is most compared with IBM Integration Bus, webMethods.io Integration, Mule ESB, TIBCO BusinessWorks and Boomi iPaaS, whereas Zapier is most compared with AWS Glue, Alteryx Designer, Tray.io, Coefficient and MuleSoft Composer. See our Zapier vs. webMethods Integration Server report.
See our list of best Cloud Data Integration vendors.
We monitor all Cloud Data Integration reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
