Zapier Reviews

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.

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.

The most valuable feature of the solution stems from the fact that it offers custom in-built functionalities between two software systems.

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.

I have been using Zapier for a year. I don't know the version 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.

It is a scalable solution. Scalability-wise, I rate the solution a five out of ten.

I have experience with Pipedream.

The product's initial setup phase was very easy.

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.

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.

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.

Zapier is a third-party automation software that connects other applications to each other. I use it to track the clicks I make. Zapier Automation can delete records automatically or add records with certain links between the contact and the opportunity. It can connect to your QuickBooks software, grab accounting data, and bring it into your opportunity. If you want to integrate with PandaDoc and you want to see the status of the e-signature document and at what price it is, you can then put that data back into the opportunity record so it's always updated in Insightly and get your dashboard reports.

I build out integrations for my clients and we can track how many tasks, clicks, or inputs Zapier can save. It saved them millions of clicks which prevented them from having to hire more and more people. My clients spend $80,000 to $200,000 a year on each employee's salary. If I can make it more efficient for them to use Insightly by implementing Zapier Automation all throughout our system, all modules, leads, opportunities, projects, contacts, organizations, and taking advantage of tracking time, then they don't have to hire someone else because that expert-level employee is doing accounting work or tax work and doesn't have to make them 20 clicks to get something done. It is already right there. Clients know when that employee is having trouble based on the time they need to complete a task. Zapier triggers an alert and says this employee needs help on this specific task. It comes in all forms of how it helps the business because it's really general automation.

The most valuable feature is that Zapier has third-party apps that are already connected to the Zapier platform, so it is easy to authenticate with those apps and start using the API connections. It is very simple to put data from one app into another automatically and that is where Zapier really shines. It also does error handling. If there's an error, you will know exactly what's wrong, how to fix it, and how to rerun it so that you can get back to the baseline. Zapier handles everything under the sun that you would think you need in automation.

There were some things that needed improvement in the past, but they've fixed them already. Zapier could be a little faster, but that might not be possible. I would encourage Zapier to make more API endpoints for each application.

I've been using Zapier for about six to seven years.

I don't think there is a limit to Zapier's scalability. I would rate it a ten out of ten. 

Zapier is not always stable, but a lot of times it's because the entire API is down. There's no control over it sometimes. For a small to mid-size business, I would rate the stability a ten out of ten. For a larger enterprise, I would rate it a six or seven.

Technical support is very good. Their team is made up of developers and engineers, so they almost always know just what you need if you fill it out the right way.

Positive

Right after you set it up, you can do simple things with it and start generating your ROI, just like with Insightly. You can also make things extremely complex and generate a huge ROI if you need that automation. The setup is as easy or complex as you want it to be.

You will see a return on investment because Zapier is the most mature integration platform and service on the market.

Zapier's price is high, but it is worth it. You have to pay a premium in order for Zapier to work smoothly. To make your work automation smooth, you have to pay a premium for it because you don't have a developer team. If you have a developer team and an AWS Lambda account or another server where you run your automation, you will pay way less if you use those products.

My advice to people who are considering using Zapier is to have their own developer team.  Zapier is a wonderful software for the SMB market, completely different from CRM. If you do not have your AWS spend account, Zapier would be a good option to develop automations or integrations on a platform that does the error handling for you. If you are a small or mid-sized business, Zapier is a great choice. You have to think about compliance as well. If you need to comply with HIPAA, then Insightly App Connect will probably be the automation platform you will need to use. You have to think about the speed of your ROI. Think about scalability and whether you have the resources to expand with the developer team in AWS. Overall, I would rate it a ten out of ten.

I am using it for automation – any kind of automation that we use along with other tools within the organization.

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.

There is room for improvement in the support. They are not responsive, and they don't take much time to get resolved.

I have been using Zapier for more than four years. I currently use the latest version.

I would rate the stability an eight out of ten. There is room for improvement. 

I would rate the scalability a nine out of ten. There are around ten users in my company using Zapier.

The initial setup is very easy. The deployment didn't take long because we just needed a subscription to get started.

I saw an ROI.

The pricing is average; it is neither too cheap nor too expensive. Moreover, there are additional costs to the standard license. 

It comes along with the number of tasks that you consume. That's something extra cost.

I would recommend using the solution. No prior knowledge or any other no-code automation tool is needed. It's very easy to get started. The advanced features might take a bit of time to grasp, but that's it.

Overall, I would rate the solution a nine out of ten.

It is very extensive when it comes to the integrations it has. So if a particular tool that I'm looking for does not have integrations with Make or n8n, then I'll check whether it has Zapier.

If it does, I use it only for that particular workflow. So I use it only when I cannot use Make or n8n.

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.

My biggest concern with Zapier would be their pricing strategy.

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. 

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.

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.

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.

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.

I use Zapier for my customers, especially those who have already started using Zapier to create automation between their applications. Also, it is a very competitive tool in the market.

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.

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.

I have been using Zapier for five years. I am a user of the solution.

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.

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.

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.

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.

I never faced technical troubles or unexpected behaviors with Zapier. I would rate the overall solution an eight out of ten.

Our primary use case for Zapier is to get leads from our Google Ads landing pages. We also send leads from our Calendly appointments with it and then send those to Salesforce.

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.

I think that this solution should have more apps connected to it. This is not necessarily a Zapier problem. For example, some of the apps require you to create an API to connect, and we do not have the resources for that.

I have been using the Zapier solution for about a year.

My impression is that it's a stable solution.

I would rate the scalability of this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best.

I would rate the technical support of this solution a nine, on a scale from one to 10, with one being the worst and 10 being the best.

Positive

I would say that the initial setup process was quite straightforward. It also took a little time to learn and understand all the features and settings. But once we got the hang of those things, it was straightforward to use it.

I would say that we have seen a return on investment thanks to the automation processes and time-saving features.

My impression is that this solution is a bit pricey.

I think the most important thing to do before starting to use Zapier is to come up with a blueprint of your automation process and understand exactly what you need.

I am using Zapier for social media and data workflows. There are a lot of use cases.

Zapier has helped my organization, similar to any other RPA, by saving me time doing repetitive tasks.

The most valuable feature of Zapier is it saves me time doing repetitive tasks.

Zapier needs to improve in the same way most RPA solutions should, such as Robocorp, Make, or UiPath. They are not good at helping you find the connections that you need for the problem that you have. For example, if need something on Instagram. I'm going to have to do research for hours to be able to find the components or the app, which is going to do what I need it to do. It makes it difficult to use the system when you don't know what to use.

When you have an issue and you're trying to find a solution, they make it difficult for you to figure out if you can use their solution to solve it.

I have been using Zapier for more than 10 years.

Zapier is stable. If I even had an issue, it is fixed within one day.

The scalability of Zapier can be good but it depends on what kind of scalability. We can use multiple applications and if we have enough money to pay for the usage, then it scales well.

We have three users using the solution in my company. We have plans to increase usage in the future.

The support from Zapier is good. Everything was always resolved but sometimes it just took a little bit longer than usual but those times were limited.

The initial setup of Zapier is very easy.

We did the implementation of Zapier in-house. 

I do the maintenance of the solution and the maintenance is similar to any other RPA. You don't touch it until there's a problem or you need to do some adjustments to it. If there's a problem, then you figure out what the problem is and then you fix it, and then you don't touch it again until there's a new improvement to do. That's the beauty of it.

We have received a return on investment from using Zapier. However, it s how you calculate your return. Sometimes it's more difficult to calculate the ROI because it's things that you don't do or it's things that are being done by the system.

The price of Zapier is approximately $75 monthly.

My advice to others is they should do their research on what they can and cannot do with Zapier. For example, I can do stuff with Zapier but Zapier has limitations, I am then obliged to use a webhook to go to Pabbly who can do something a little bit better than Zapier. Then I move on to another webhook to another system that can do something else. You jump from platforms because they don't all do the same thing and they don't all gather things the same way.

I rate Zapier a nine out of ten.

While the solution is lacking in some areas, and it's not always perfect is why I didn't give it a ten.

I primarily use it for Automation. The main mission of Zapier is as an automation tool.

The best thing is to automate workflows with third-party integrations, like Airtable, or Google Drive.

The pricing could be a little cheaper. 

I have been using it for three years. 

I use it myself, for personal use.

I chose Zapier rather than something else because it supports upgraded automation functionalities with various third-party integrations.

The initial setup is pretty easy to do. 

It is straightforward. We just have to create a Zap, and after finishing the editing, we publish it.

The pricing is suitable. It's not cheap, but not expensive.

Overall, I would rate it a ten out of ten. 

It is not difficult to use Zapier for the first time. You need to just type in your requirement, and then Zapier will automatically show supported integrations.