Zapier and webMethods.io are key competitors in the integration platform category. Zapier appears to have the upper hand in accessibility and ease of use, appealing to a wider non-technical audience, while webMethods.io is favored for enterprise-level integration capabilities.
Features: Zapier offers a wide range of application integrations, including customizable workflows and seamless setup for varied tools. It facilitates task automation and reduces the need for custom development. WebMethods.io equips users with robust B2B integration, strong API management, and comprehensive out-of-the-box solutions.
Room for Improvement: Zapier could improve Google Sheets integration, real-time sync, and support channels, alongside more complex logic flows. WebMethods.io would benefit from enriched documentation and streamlined integration processes, with enhancements in cloud service support and newer API standards.
Ease of Deployment and Customer Service: Zapier's deployment on public cloud platforms allows easy setup and integration with minimal technical support. Its customer service is praised for responsiveness. WebMethods.io often involves on-premises or hybrid deployments, which complicate the setup, and customer service feedback highlights variability in clarity and issue resolution speed.
Pricing and ROI: Zapier's pricing is tiered based on usage, which some find high, but the automation benefits are deemed worth the cost. WebMethods.io's enterprise-oriented pricing is seen as expensive, with complex licensing that can be challenging for smaller companies, though the investment is often justified by large-scale capabilities.
In a scenario where employing three resources for three months might cost approximately $18,000 to $20,000, Zapier provides substantial cost savings.
The experience was positive with prompt responses from their team.
Sometimes, in my early days, when I was stuck with something, they helped me solve these issues, and even helped me solve some of my automations.
Vertically, scalability is fine, however, I have not expanded horizontally with the product yet.
Scaling it gets quite expensive, and while I cannot evaluate it purely from a technology perspective, compared to Workato, I would give Zapier a seven for scalability.
There are some issues like the tool hanging or the need for additional jars when exposing web services.
In my current company, we had significant challenges with Zapier regarding maintenance, as Zaps were often broken, not necessarily due to Zapier, but due to changes in the input variables.
A special discount of at least 50% for old customers would allow us to expand our services and request more resources.
Specific workflows could be created to pull transformed data through Zapier workflow directly into visualization tools for dashboard and report creation.
While Zapier already has more than 2,000 webhooks, users or developers should have the flexibility to create additional custom connectors.
I would appreciate if there would be a feature where we can use actions right after loops. Currently, you cannot use any other action after the loop. Everything needs to be within the loop.
The pricing is in accordance with market standards and even lower in some cases.
It facilitates the exposure of around 235 services through our platform to feed various government entities across the entire country.
Creating integration points through webhooks is particularly useful for anyone working on integration projects.
By specifying conditional logic rather than transforming and performing conditions within the visualization tool, Zapier provides conditional logic on the behavioral side to get specific data and load it into Power BI visualization tool.
They have approximately 7,000 connections.
webMethods.io Integration is a powerful integration platform as a service (iPaaS) that provides a combination of capabilities offered by ESBs, data integration systems, API management tools, and B2B gateways.
Zapier is a tool for primarily non-technical users to connect together web apps.
An integration between two apps is called a Zap. A Zap is made up of a Trigger and one or more Actions or Searches.
Whenever the trigger happens in one app, Zapier will automatically perform the actions or searches in another app in order.
Zaps are very lightweight and easy to set up. Zaps do not import or export old data (they only operate on new items created after the Zap is enabled). Zaps are also not kept in sync ("two way syncing") after the Zap is triggered.
Zaps are deceivingly simple if you're used to dealing with complex and difficult integrations. Their simplicity is what enables anyone to create them.
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.
