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.

My biggest concern with Zapier would be their pricing strategy.

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.

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

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

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.

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.

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.

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

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. 

I think it’s brilliant because the webhook feature allows you to basically send information from any application and connect to all the most common applications on the market.

The possibilities are great and the limitations are very small.

The only frustrating thing was the support. Most applications have a chat or call center function for support. Zapier did not have this function, which meant you had to send a case and wait up to 2-3, or sometimes even 4 or more days, for a reply.

Being able to share Zaps and organize them with teammates would allow sharing and refining scenarios and even combining steps that require different people's credentials.

There are no areas for improvement that I can think of.

The pricing of the solution is quite expensive. 

What I miss the most is the ability to share my Zaps with my teammates. If/Then/Else branching for multistep Zaps is the closest next thing. So far, you only have the filtering function "If criteria are met then continue, else stop the workflow", but I do want to define what should be done if criteria are not met.

Also I want to know a little bit more about my Zaps. Now I can see the history of the executed Zaps and see its status (If it is on or off). But I would like to know when it was last updated, if it has any tags (such as "beta" or "do not touch") and also get a quick summary re its performance for the last 7d (number of times it was executed, how many times it was successful).

I think the history of "zaps" could be improved. Zapier is not practical to produce indicators.

Some colleagues don’t find the chat/email channels that intuitive. I would really like a Slack integration for this. I would also like to know:

• Comparative visibility of other times
• Retrospective reports on best time vs. worst time
• Percentage of max reach CS achieved for us on messaging on the requeue. In this way, the algorithm can be ‘proven and trusted’ more.

Some apps are not available yet. For instance, a connection with Joomla! would be great. In general, all the most-used apps are available, but I bumped into Joomla! with a client.  We would like to import new subscribers on the Joomla! website automatically into MailChimp. I requested this connection.

I would love to see the availability of logic into Zaps; not just a simple "if-then" but closer to the Excel-type logic.

In the past years, I've seen Zapier improve a lot in the user interface and in the amount of possible integrations.

I would like to have more integration with lesser known, local tools. Zapier serves all widely used global apps, but not all well-known local applications.

I would expect to see more Zapier-own-built apps that provide business rule capabilities. The current apps are basically acting as an interface. It would be interesting to be able to create business rules within the Zap, connecting to databases and such.

For more detail:

Zapier has a set of self-developed apps- webhooks by Zapier, Formatter by Zapier, Code by Zapier, etc. I would be interesting for me to at least to have more apps of Zapier that enable me to create more complex logic flows.

For example, let’s say I want to create a Zap where I can input some data and based on some logic and some static values, there is an output to that data.

An example of this application would be a simplified fraud prevention tool for ecommerce where there is an input of several parameters from the customer and the output is the result of the fraud scoring from 0 to 100.

There would be several steps where, based on the input parameters and several key,value dictionaries, in every step a partial score would be added so that finally there would be a final score in the output. For example, one dictionary would be country/score so that the partial score of the credit card country or the IP country would be added to the total score.

Another example would be to have a Zap to manage A/B testing. There would be again an input with the navigation parameters, and an output to send the customer to the A or B funnel. The decision would be made based on the parameters and/or adding an random factor so it would be possible to send for example 70% of the customers to A and 30% to B.

So, to achieve these two examples, I would expect to have:

- Input/output interfaces: there is already a Zap called webhooks that would do the job.

- Static values: there is a zap called storage but it would be great to have a zap that can connect to remote databases.

- Decision steps. I miss a zap to configure complex decision flows. Maybe it could be a Zap of Zaps.

- Maths. For the example of the random factor and any other math function it would be nice to have a zap that can apply math functions to the input values.

To be fair, there is a zap to do all this, “code by zapier” that gives a lot of flexibility as you can code freely whatever you need. But as I pointed out, the great of Zapier is precisely the fact that you don’t need to code to build workflows. So, if I use Zapier and I end up having to code, it loses its sense in my opinion.

The user interface for Zapier could be improved. It also takes some time to sync the data between different environments. 

The error reporting UI and organizing Zaps could be improved.

We had a problem where multiple users were firing similar zaps on the same
data set. Debugging this issue was really difficult using the task history
view. Luckily the zap customer support was able to confirm there were other
users zaps running. This would have been good to see by our main
developers. It appears that zap has introduced zapier for teams recently
which would possibly resolve this issue.

The organisation of zaps was also resolved as we learnt to use the folders
feature and added a naming convention to the zaps to keep them in order to
match our business work flows.

Continuing to build out the library of Zaps would be great, as well as exploring how to improve upon the limitations of the APIs they're tapping into. Also, while it's very difficult to turn API connections into a simple process, continuing to improve the Zap builder flow can only help make it less intimidating.

Zapier could improve on some Google Sheets features. For example, having the Zaps not break down when one row has been moved, but the header has stayed the same.

Some integration isn't available. I think the expansive list of software that they support just reflects Zapier’s commitment to doing great work.

Zapier has also been very proactive and they really listen to what their users want.

In our case, very limited actions and limited objects are supported. For example, there is no delete action.

I have used my custom zap to integrate Salesforce and JIRA.
Whenever new case created in Salesforce, new JIRA ticket is created(I have my own JIRA instance).
JIRA ticket has description, status etc... fields which we are populating from Salesforce Case record.
What if description/status of the Case is changed in Salesforce. The changes are not reflected in JIRA ticket as Zapier supports only create action trigger.
Same for delete. It does not delete JIRA ticket whenever Case is deleted in Salesforce.
I think this can be done by using external Ids.

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.

• 2-way synchronization: The zaps work one-way, but sometimes two-way is needed.
• Startup sync: Zaps only work on records created from the day you put the zap in action.

Sometimes, it is hard to work with leads and some custom objects through Zapier.

• The Google Analytics integrations (especially the Facebook Lead Forms to Google Analytics)
• HubSpot, that leads to Android phone integration

I had to disconnect it, because it was not working right. Our CRM system is not well-known, so I think that was part of the problem.

Customer service could be better. When I asked questions about how to connect it again, I was told it could not be done. I know that is not correct, because Zapier does have connections with our email system.

Some recent changes to the solution have made it bulky and not as intuitive to use as it previously was. 

The visual display of connections, say, in a process map; not really high priority, more of a nice to have.

Right now, Zaps only run once. Also, you cannot do automations in bulk.