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.
Great capabilities
Zapier provides good experience with the users.
Zapier is great for quick custom zaps that save time
Exhaustive integrations and easy to use
What is our primary use case?
What is most valuable?
There are tools that don't connect with n8n or enable integration by default. So it means that I'll have to use Zapier because Zapier luckily has a wide range of integrations, I would say. So for those kinds of use cases, I think it still works, giving it a shot instead of trying to build your own custom integrations using code.
So that way, it's still worth the money. But if Make or n8n has an integration, I would definitely go ahead with them and not with Zapier.
What needs improvement?
My biggest concern with Zapier would be their pricing strategy.
For how long have I used the solution?
I have used Zapier. I still use it, but to be honest, I find it a little on the pricey side, you know, a bit more expensive than other products like Make or n8n.
How are customer service and support?
The community was decent enough to help me with basic stuff. Anything was much more interesting.
There were times when, you know, we received responses from the founding team, and sometimes we received input from the overall user community who were really ambitious and passionate about the platform. So in terms of customer support, I would say n8n is higher than Make, maybe, and then Zapier.
How was the initial setup?
The initial setup is actually the easiest among the three tools: Zapier, Make, and n8n. With Make and n8n, you need to have some understanding of technology, at least knowing what a webhook or field is. But Zapier simplifies it with more common English terms. For example, instead of "new role," it would say "new task." So I believe getting started with Zapier is better than the other two.
What's my experience with pricing, setup cost, and licensing?
I think their pricing is, like, way off the chart. So that's the reason why I try to stay away from Zapier.
The pricing actually depends on how many steps you have. For example, let's say for each lead, you have to perform four actions. Let's say there's a marketing lead. You have to do four things whenever a new lead comes in. Zapier calculates these as four different items or units of work.
So technically, the more actions you take and the more times you do it, the cost starts to grow exponentially. It grows pretty fast. So it can be a little expensive. I think they have a starting price of around $20, but if you have more than 30 tasks, it starts to add up. And each task can involve multiple actions. For example, with 25 tasks, you're almost reaching your quarter limit.
So you have to consider the volume you'll be using.
What other advice do I have?
If you can afford it, don't think about anything else and go ahead and build it. It's exceptional. But if you're expecting high throughput, meaning a lot of operations and steps, you might want to take a step back and see if you can afford it or if there are alternative features. Feature-wise, I think it's on par with the others.
Overall, I would rate it an eight out of ten. One reason is that I don't think it provides great value for money, but it has exhaustive integrations, the highest number compared to others.
The second thing is that it's not open source, which is a big issue when it comes to no-code platforms because you become dependent on their pricing strategies and sustainability. So having vendor lock-in and pricing revisions would be nice to see.
A tool for automation purposes requiring an easy initial setup while offering a very helpful technical support team
What is our primary use case?
What is most valuable?
Zapier's interface, for me, is the solution's greatest value proposition. It is designed and developed for people who don't have a clue about what they're trying to do. It has a very user-friendly interface. It is definitely designed for non-technical people. For example, you ask an accountant who only works with Google Sheets to develop automation using Zapier, and the accountant will be able to do it in an hour. So, it is very easy.
What needs improvement?
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. So, it's not about the automation process but the triggers that trigger an automation to start running. Sometimes if you set up an automation trigger on a specific application, we wouldn't know if Zapier received data to start running. So we cannot understand whether the problem is in Zapier or the steps before.
Branching scenarios is something I want to add to the solution to make my life easier. We want to apply a logical workflow with a yes or no condition. On Zapier, you can have a condition, but you can build the actions after one value on this condition. So, the question can be responded to with a yes-no option or not answered. In your scenario, you have only the actions after yes get chosen. A second scenario is needed for the answer, no, and a third one for not answered. While in Make, we create a diagram, according to which if the response is yes, then do follow this path, and if it's no, then follow another path.
For how long have I used the solution?
I have been using Zapier for five years. I am a user of the solution.
How are customer service and support?
I have contacted Zapier's technical support team only once. My experience with Zapier's technical support was very nice since they were very polite and helpful.
How was the initial setup?
The initial setup was very easy. The solution is deployed on the cloud. The deployment process takes a maximum of one hour if it's something very simple and not more than four hours if you have a more complex scenario.
What was our ROI?
It is not worth the money if you have a little bit of a technical mind. So, it's quite good for starting, especially in the first weeks, after which you have to switch.
What's my experience with pricing, setup cost, and licensing?
Price-wise, Zapier is expensive when compared to Make. Payments can be made per month or per year. They have different plans, and they charge for the automation one developed using Zapier. Also, it can run only for a fixed number of times while not being able to optimize anything. Per task, there is a monthly plan involving 15 euros. They have a similar pricing model to Make and Zapier charge per task. Also, in different forms, they just give you the ability to use different features. They charge 18.58 euros for the first standard plan, which includes 750 tasks. So, it is about 25 cents per task.
What other advice do I have?
I never faced technical troubles or unexpected behaviors with Zapier. I would rate the overall solution an eight out of ten.
Zapier makes integrations easy for people with a simple solution and frees time for important stuff
Probably the best, but not practical due to pricing
Regarding features and UX, Zapier is still superior to other alternatives like Flowmattic, which I am currently using. While Flowmattic is more affordable and offers no limits on tasks/runs/integrations and full ownership of logs and data, Zapier has a broader range of integrations with niche apps.
Zapier needs a more affordable pricing plan for businesses operating in developing countries (parity pricing).
User friendly, yet powerfull and mature solution for you automation needs
Don't be fooled by the simple UI, this tool does a lot, including your own code execution.
Zapier con Duda
We can save a lot of work in process validation, we save many hours of work