Zapier Reviews

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 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.

We use Zapier to connect AirTable to other apps that live on Zapier's platform, like QuickBooks, Google Drive, and Google Docs. We also use Zapier for automated document creation utilizing webhooks, pulling in data from a WordPress site or form software into AirTable. When consulting a client and trying to connect different apps, I often utilize Zapier if it can't be done through AirTable's automation.

Webhooks are the most valuable feature of Zapier.

After mapping them out, and they'd worked for a while, I've had Zapier fail. I set up a very complex app with AirTable, Zapier, and Asana. For generating tasks in Asana based on the template, they changed all the actions with Asana, which no longer made that possible.

I have been using Zapier for four years.

I rate Zapier an eight out of ten for stability. For the most part, Zapier is stable. However, it has downtime like any other cloud-based software.

Zapier is a scalable solution. You can buy as many Zaps as you need and utilize as many tasks as you need.

Zapier’s initial setup is straightforward.

Since Zapier is a tool, it does not need a deployment. It's a tool that can be created in two minutes.

There are products cheaper than Zapier. You can start with a free plan and get limited access. The least expensive plan is $24 a month, and you can go all the way to $800 a month if you're a huge company using many tasks.

Zapier is deployed on the cloud. I would recommend Zapier to other users.

Overall, I rate Zapier an eight out of ten.

Zapier is a really good tool for connecting multiple different platforms and data sources. For example, with Quickbase, I can easily integrate data from other sources like AWS or task-tracking platforms such as ClickUp or Asana. It's very very similar to QuickDesk's pipeline feature but offers more depth. Another example would be integrating with apps like Airtable, Salesforce, or Hub. Zapier has connections for all of these platforms, making it easy to connect and move data. It's essentially a tool for automating tasks.

Zapier has allowed me to integrate between two different platforms a lot quicker than if I had to manually write APIs or Webhooks.

I'm open to using it when there's a use case for it. If something can be handled with QuickDesk pipelines, I would prefer to use that because the client is typically already paying for Quickbase, which includes pipelines. However, if there's a situation where Zapier is better suited, such as having a built-in integration that pipelines don't offer, I would consider using Zapier. Currently, I don't have any specific plans in mind.

The most valuable feature is the wide variety of built-in integrations it offers. In my experience, I haven't come across anything else that provides such a diverse range of connections.

I would like to see them improve the Quickbase integration. Currently, it only allows triggering actions when records are added, but it would be more useful if we could also trigger actions when records are modified or deleted. It would be helpful if these features were there. 

I started using Zapier probably four and a half to five years ago. However, I haven't been using it as heavily. I used it a lot in the beginning, and then I recently started using it again a few months ago. So, I feel pretty confident in using that tool. I am using the latest version.

I would rate it around nine. It's very stable.

I would say it's probably an eight.

I have spoken to thecustomer service and support team about a few technical matters. I would say their technical support is very good.

The initial setup is straightforward. It's essentially a low-code platform for making API and web calls.

In my experience, it provides a good return on investment.

It's very affordable, especially for companies.

I would say that there are certainly other software options available for Zapier, and I would encourage you to explore each one to consider what you're trying to integrate. However, Zapier is a really good tool and worth looking into.

Overall, I would give it a nine.

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.

We're using Zapier to connect third parties.

What's most valuable in Zapier is its simplicity, seamlessness, and smooth plug-in, so you won't need to build code for every action. I'm not a developer, but I can use Zapier, though I've learned from developers how to connect, so it's easier for me to use Zapier.

The solution fits the needs of enterprise-level solutions. My company is more of a small to medium enterprise, and Zapier fits its needs.

The best feature of Zapier is that every third party you could think of is there. It's a cheap place to know all the third parties in the market. webMethods has a similar feature, but it's not as easy as Zapier.

Marketing-wise, Zapier is also better than webMethods. When you Google, you can find Zapier immediately.

Zapier is also great for beginners or people starting to learn about integration and eCommerce, while webMethods is more for integration experts or enterprise-level integrations. Zapier is novice-friendly.

A development background is necessary when using Zapier, so it's an area for improvement. To use Zapier, you need to learn more about IT architecture. It's easier to use for people who spend time learning about productivity and know more about data.

Zapier needs more YouTube or video tutorials or more training for people. That would help a lot. In particular, Zapier should have documentation for every connector. Zapier did a great job talking about connectivity, but it needs more documentation on how you can connect ManyChat with PostgreSQL, for example. 

Its documentation needs to be more detailed and visual. Sometimes people want to watch rather than listen or read guidelines.

More integration with third-party software would be great in terms of what I want in Zapier in the future.

I'd rate Zapier as ten out of ten.

I'm a customer of Zapier.

I've used Zapier for nearly two or three years.

Zapier is a very stable solution, but the problem with it is if your credit card lacks funds, the Zapier team will downgrade your subscription, which impacts your service's stability. I've faced this situation before, and I remember how a lot of data was misplaced, and I had to recover the data, which took a very long time manually.

I tried to make a recovery by batch, but because the license was downgraded, it impacted the number of data. For example, on the free version, you can have up to five hundred data; imagine if you've done thirty thousand data. If your card payment doesn't go through during renewal, Zapier will downgrade your data to five hundred, and the service will stop completely.

Zapier is a very scalable solution.

I have yet to contact the Zapier technical support team.

I didn't use a different solution apart from Zapier because it had many connectors, which I liked, so I didn't look for other solutions.

Setting up Zapier didn't take me long because I had the help of a developer. I would have found the process difficult if I had done it all by myself. After the setup, whenever I encounter an issue with Zapier, I know how to solve it without going back to the developer.

We're still in the trial period for Zapier, connecting with third parties, but if we continue to use Zapier, we could have a great ROI.

Zapier is a paid service. Its license renews monthly, and Zapier will downgrade your subscription to the free version when your credit card doesn't have funds. That significantly impacts your service because everything halts completely.

Zapier doesn't have any hidden costs. You'll see all pricing information on the website so that you won't be surprised at the end of the month.

Only two people use Zapier within my company.

One specialist handles the deployment and maintenance of Zapier.

How extensively you use Zapier depends on the volume of registrations. For example, suppose you have a high volume of registrations and a high volume of usage. In that case, it's better to use webMethods or IBM API Connect because Zapier is more for the number of tasks or times you perform the task, so Zapier could become expensive if you have many visitors and many actions happening inside your application or website. My company's volume is lower because my team has been in the trial phase for two years. Still, after the trial, the volume of sales and visitors increase could become high, meaning the usage of Zapier would be higher.

My advice to anyone planning to use Zapier in the future is to go through the same journey I've been where I sat with a developer to understand how things work because you won't find many YouTube guidelines on Zapier.

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.

The product's most valuable feature is automation. We do not have to deal with any functionality. Another efficient feature is looping. It doesn't incur additional costs for extra steps and requires no coding.

One notable concern is the time-out resources assigned to automation when running. It could support various languages along with Python.

We have been using Zapier for five years.

It is a stable platform. However, when automation fails, they could provide information about the reasons for failure. We have run automated tests again in debug mode with the same data. I rate the stability a seven out of ten.

I rate the platform's scalability a five out of ten.

It is an easy-to-deploy product with free trials available.

The users are willing to work around issues and assist with replacements related to custom firmware and existing software. It demonstrates a proactive and problem-solving mindset. The users prefer integration rather than retraining or retracing to maintain a seamless workflow. However, it is expensive. 

Automating this process through Zapier eliminated the need for repetitive copying and pasting, freeing valuable time for more meaningful and strategic activities. The integration with Python has helped with efficient visual-based data manipulation.

I rate it a seven out of ten.