Zapier's use case is similar to that of Pipedream, but the only big difference is that the former would have in-built functionalities to offer to users, especially in the areas concerning products like Google Sheets or HubSpot. Zapier is more seamless to use due to its in-built features, but sometimes there would be issues with bugs or Zaps not firing, so there are certain nuances you have to play with in Zapier that are not very understandable unless you actually check if Zaps are fired and see if it works for yourself.
Zapier
ZapierReviews from AWS customer
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
My Experience with Zapier
A tool to connect everything
Zapier is the tool for everything.
Though the tool offers a visually appealing UI, it needs to improve its documentation
What is our primary use case?
How has it helped my organization?
Like in Pipedream, if users don't want to rely on custom codes, Zapier ensures that it fires one to ten records a day that users need to move or transform data. Zapier is made a lot simpler, considering the use cases for which the product is built, so that users can deal with and ensure that it provides better quality easily.
What is most valuable?
The most valuable feature of the solution stems from the fact that it offers custom in-built functionalities between two software systems.
What needs improvement?
With Zapier, improvements are required in the areas of concerns like bugs, ease of use, and documentation. The product has many bugs, so users have to wait for a period ranging from five minutes to an hour to see where the Zap went. In Zapier, Zaps aren't very understandable owing to the way they work. As a user, you would think that in Zapier, a Zap works in a particular way once you set it up, but it won't happen. At times, some Zaps can interfere with each other, because of which there might be infinite loops that may occur, owing to which multiple Zaps continue to run or break down in general, after which nothing would run in your environment. You would not be notified about the breakdown of Zaps.
The bugs in the product may be considered to understand or get an explanation of how Zaps works between software systems, so for something between Gmail and HubSpot, Zapier would explain through better documentation what would work and what wouldn't work. Maybe if Zapier had better functionality with Python or any other coding language in general, it would make the product a lot better.
For how long have I used the solution?
I have been using Zapier for a year. I don't know the version of the solution.
What do I think about the stability of the solution?
Stability-wise, I rate the solution a six out of ten owing to the bugs and breakdowns of the system that I have experienced. One cannot understand how Zaps work unless you test it out a few times.
What do I think about the scalability of the solution?
It is a scalable solution. Scalability-wise, I rate the solution a five out of ten.
Which solution did I use previously and why did I switch?
I have experience with Pipedream.
How was the initial setup?
The product's initial setup phase was very easy.
What was our ROI?
Return on investment from the use of the product can be experienced by a professional team in a company. Personally, I would say that if you're running one to ten tasks a day, it is free, meaning there is a return on investment for me as I can make money from the product's use. For a company, I guess it costs around 70 USD a month. You could either pay a programmer 70,000 USD dollars to 1,00,000 USD or use Zapier and pay around 60 to 70 USD to take care of everything in the back-end.
Which other solutions did I evaluate?
Zapier was one of the options that I came across during the evaluation phase, as it was actually forwarded to me by someone who had worked on it in the past.
What other advice do I have?
Zapier is pretty fun to work with, considering the fact that its UI is a lot more visually appealing than Pipedream. I would suggest that the product's potential users need to watch out for any Zaps that might not work and try to play around with them to figure out a better solution.
I rate the overall tool a seven out of ten.