Find out in this report how the two Integration Platform as a Service (iPaaS) solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
We have automated complete order-to-cash processes for multiple customers, saving over 90 million dollars.
The return is faster since development efforts are minimized, allowing for quicker integration delivery.
In a scenario where employing three resources for three months might cost approximately $18,000 to $20,000, Zapier provides substantial cost savings.
Seamlessly meeting SLAs and providing excellent responses to challenges and issues related to interface and data connectivity.
The tech support is very good, offering immediate responses and chat options.
We receive service that is more than adequate, even exceptional.
Their technical support is good; they respond promptly and are very helpful.
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.
The experience was positive with prompt responses from their team.
The reason we wanted to use our own Kubernetes cluster was to do automatic scaling for utilized resources, allowing us to save.
We have built approximately 1,100 interfaces for one customer, which is a significant achievement.
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.
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.
The integration landscape has become complex, and having a data strategy with unified data models would make integration easier for any platform, including Boomi.
A significant area for improvement is version control.
The ETL aspect of Boomi iPaaS is not mature enough at the moment.
The error message options in the dashboard should be improved. It should be user-friendly so that beginners or non-technical users can figure out the problems and solutions on their own.
You can build similar or dependent automations in one Zap, which helps with understanding the process without switching between different records.
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.
While pricing is relative, compared to others, it is favorable.
The pricing for Boomi iPaaS is reasonable, costing around $6,000 per year.
The pricing is in accordance with market standards and even lower in some cases.
The pricing of Zapier is slightly higher compared to other market automation tools such as Pabbly, Make.com, and N8N, which have good features but are priced lower than Zapier.
It automates the creation and population of a data warehouse, reducing the need to write SQL scripts and procedures.
The most valuable features of Boomi are the integration capabilities, the Data Hub product, and the UDI integration.
The maturity of the product is significant.
They have approximately 7,000 connections.
Even a person with no technical knowledge can use Zapier to create automations.
The automation capabilities are impressive.
The Boomi AtomSphere integration platform as a service (iPaaS) supports all your application integration processes – between cloud platforms, software-as-a-service applications, and on-premises systems. Your entire team has online access to a powerful range of integration and data management capabilities, that can be realized in a fraction of the time of legacy middleware technologies.
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 Integration Platform as a Service (iPaaS) 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.
