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.
Lead Consultant for Cloud Implementations at ZeroClick.ai
Real User
Top 5
2023-09-08T16:39:00Z
Sep 8, 2023
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.
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 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.
CEO at a financial services firm with 1,001-5,000 employees
Real User
Top 10
2022-11-22T19:59:48Z
Nov 22, 2022
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.
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.
Founder & CEO at a tech services company with 11-50 employees
Real User
Top 20
2020-12-13T06:33:00Z
Dec 13, 2020
The only thing that we find that could be better is system-to-user task automation. That's actually where we come in and what gives us work. System-to-system is fine, but when it comes to system-to-user, where Zapier is helping to communicate to a user, that's a one-way communication. If that user has to perform some action on that notification, the action isn't handled by Zapier. So there's no way to orchestrate that and it's very cumbersome. If they're able to move Zapier in that direction, with two-way communication between the users and Zapier, it will be very powerful.
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...
One notable concern is the time-out resources assigned to automation when running. It could support various languages along with Python.
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.
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.
At the moment, they allow a limited number of apps. I look forward to getting more apps for each package.
The solution does not work properly when we apply filters and we get errors.
My biggest concern with Zapier would be their pricing strategy.
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 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.
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.
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.
Some recent changes to the solution have made it bulky and not as intuitive to use as it previously was.
The pricing of the solution is quite expensive.
The only thing that we find that could be better is system-to-user task automation. That's actually where we come in and what gives us work. System-to-system is fine, but when it comes to system-to-user, where Zapier is helping to communicate to a user, that's a one-way communication. If that user has to perform some action on that notification, the action isn't handled by Zapier. So there's no way to orchestrate that and it's very cumbersome. If they're able to move Zapier in that direction, with two-way communication between the users and Zapier, it will be very powerful.