Zapier Reviews

• The concept of creating business rules and workflows without the need to code
• The great number of Zaps available
• The ease of creating Zaps

Our business is an online travel agency. We have created some Zaps that automatically create Zendesk tickets when a booking is made. We also receive Pushover messages in our smartphones when a booking is made or when there are errors.

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.

I’ve been using Zapier for the last eight months.

I did not encounter any deployment issues.

I did not encounter any stability issues.

I did not encounter any scalability issues.

Technical support is very good. I got the proper answer immediately via webchat.

I did not use anything previous to this solution.

The setup was quite straightforward. I encountered some issues that were solved very quickly by customer support.

I did it in-house. In fact, I did it myself.

I think the price is interesting for startups that need to focus on their core and want to solve interface issues quickly. But the minute there are resources to cope with these interfaces, the price is too high to compete with in-house development.

As I said before, it is very interesting for quick wins with a lack of resources.

We use Zapier to integrate Salesforce with other tools that we use within our organization. 

Zapier is user friendly and makes it easy to integrate different tools. It has a drag and drop functionality which makes it easy to connect environments. 

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

I have used this solution for one year. 

This is a stable solution. 

This is a scalable solution.

The initial setup is straightforward. 

We consulted a third party to implement this solution. 

This is a very good solution and I would recommend using it for integrations. There are other similar tools which have the same functionality but I have not used those so I would recommend Zapier. 

I would rate this solution an eight out of ten. 

Zapier interacts with multiple applications and services. The ability to pull in data from a range of services and connect them together into a workflow has allowed us to automate our administrative tasks. We can prototype business tasks into a single process by linking together the tools and apps we use.

Trello, sheets, and emails.

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.

I have used Zapier for eight months.

Once or twice the API did not connected and we weren't sure if it was an error in our Zap setup, Zapier servers, or in the external API.

We have not had stability problems. When you get to 80% of your upper limit, you get a message informing you to upgrade to a higher package. This advanced heads up helps you choose to scale up and it's all easily done.

Support is very good. It was critical in helping us set up quickly and find faults when we had multiple accounts running Zaps at the same time. Most of our issues were responded to within an hour and resolved within the same day.

We looked into using IFTTT, as well as building the services in house.

However, Zapier had links to more services and the user interface was much easier. So the ease-of-use and ability to prototype from concept to working process made choosing Zapier a no brainer.

The setup is very straightforward. Each step is numbered and you constantly know what step you are on. Each step also involves a test and allows you to view sample data as you move through the workflow.

The pricing is reasonable and based on successful completion of a Zap. So use filters.

We looked at IFTTT and coding the services in-house.

Start with the basic package and give Zapier a try. Build small simple Zaps that automate parts of an administrative process.

Zapier's ability to connect disparate systems is incredibly valuable. It saves tons of development time as you're able to point and click instead of building a customized integration between your different solutions.

The variety of Zaps is great. The fact that they have customizable ones, e.g., WebHooks, to build your own for missing Zaps, is also a huge perk.

We use both Marketo and Eventbrite, but there's no direction integration between the two platforms. Even before Marketo became available on Zapier, we were able to use the WebHooks option to feed Eventbrite registrations into Marketo at near-real-time speed. This automated a previously manual process of transferring data from one system into another.

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.

I’ve been using Zapier for two to three years.

Very rarely do we have stability issues. Occasionally, there are instances where it seems like actions that should have triggered a Zap did not trigger it. But it's hard to say whether it's Zapier's fault, or the fault of the tool generating the trigger.

We have not had scalability problems yet. We upgraded from their free offering once we ran into our Zap limit, but the pricing is still very affordable for the value we get from it.

Technical support is great. The few times I've needed them, they have been very responsive and helpful.

Previously, I would tap into individual solution APIs and create custom bridges between them, if it was worth the effort.

The setup is straightforward. Integrations with solutions tend to be OAuth-based, which makes it very simple. Beyond that, there is no real setup other than individual Zaps. That can be as complex or straightforward as you want, depending on what you're trying to make them do.

The free plan fulfilled our needs for a long time and is a great way to see whether Zapier can be useful. But consider upgrading if you're dealing with higher volume, the need for quicker processing, or specific integrations that are only available in the paid tiers.

We didn’t look at alternatives.

Give it a shot. It can save you a lot of time and help you create really elegant solutions at a low price and with a low amount of effort.

The number of connected apps allows Zapier to be my one stop shop when setting up automation processes.

Zapier has allowed our company to focus on important goals and run smoothly, rather than spend our time getting bogged down in mundane, busy work.

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.

I have used this product for approximately ten months.

We encountered a stability issues once when Zapier upgraded the Google Sheets backend. However, this was most likely an error on my part and not Zapier.

Zapier scaled beautifully when we needed it to. We never had any issues here.

I would give technical support a rating of 10/10 for quick and helpful responses.

The initial setup was incredibly easy. Zapier has great tools and a great UI to help us understand what we are doing.

Although the pricing structure can get expensive depending on your needs, I still recommend Zapier to all my friends.

We evaluated IFTTT, but settled on Zapier because of its more diverse app base.

Learn to make the most out of each step in a Zap as it helps cut down on redundant steps.

As a marketer, the most valuable features are automation of the following:

• Content curation
• Client onboarding
• Gathering qualitative data using surveys

• We use it for social media curation, sales funneling, and client onboarding automation.
• We also use it to gather qualitative data from our audience via Typeform integration.
• Internally, it helps us with team productivity and collaboration.
• Curation of top articles for social media marketing has never been easy. Our team can now seamlessly collaborate using Pocket to Buffer integration. Through Zapier, we are able to vet all content before they get shared on social media platforms.
• As an SaaS business, client onboarding is a crucial part of our workflow. Zapier makes it a lot easier for us to create sales (Pipedrive) to CRM (Autopilot) integrations, as well as setting up the necessary push notifications (Slack), so all team members get constant updates about what’s happening.
• This allows the team to be more transparent and accountable as everyone knows who’s doing what and everyone is on the same page.

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.

I have been using Zapeir for seven months.

I haven’t experienced major stability problems. There were a few instances when a trigger-action did not fire or there was a delay. During these instances, however, I would just retest the step and it was fine.

Our database is not that large. So far, we haven’t encountered any scalability issues, even though we’re gradually scaling.

I haven’t had the need to contact support, as the use of Zapier has been straightforward.

Zapier has been "top-of-mind" when an automation tool is mentioned.

The initial setup was very straightforward.

We are a startup, so getting the starter plan was the most practical option for us.

We didn’t look at any alternatives.

Zapier is a powerful tool. It’s really up to the users to maximize its capability and use it with as many Zapier hacks (for both marketers and developers) as possible.

The included actions that satisfy our requirements are very useful.

Since we are using this product for Salesforce and JIRA integration, whenever a new case gets created in Salesforce, a new ticket is created in JIRA.

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.

Until now, we have had no stability issues.

Until now, we have had no scalability issues.

We have not contacted the technical team yet.

We started with Zapier only.:>

The setup is very user-friendly.

Pricing and licensing are reasonable.

We did not look at other products.

It saves time and is maintainable.

Zapier is more on the notification side. We're doing work for a last-mile logistics company which deals with vegetables, meaning that it's farm to table. They're trying to eliminate storage and they want to make it as fresh as possible to the table itself.

They have their GPS-enabled vehicles, and sometimes trucks, picking it up. So they have to track them all. They have to track all vehicles, whether it's their own or third-party, all the way, for all exceptions, and then suitably handle it.

They also have the delivery sites and there are a lot of exceptions that happen. They use another third party called Bookam for last-mile delivery tracking.

Again, a lot of exceptions happen that are not tracked by Bookam, so we take care of the exceptions. Those events come to us, and through Zapier we then process them all.

It's third-party tracking events, with GPS events on one side, all of which are tracked by the applications. We take the events from them and push it into Zapier for orchestration, and from there on we alert the right parties.

With Zapier we are easily able to set up a custom notification and event-tracking service in only a few hours as opposed to several days. It has really cut down on the time needed to get up and running with the day-to-day operations in our line of work. 

We find it effortless to set up. We really don't have to do anything other than finding the application in the Zapier catalog. And as long as the application has been re-integrated into Zapier, they're able to then just provide the connection details and hook it up.

One thing about being able to select the particular event: If we want to track activity from any third-party application, and then perform some actions on it, whether it is going in and putting something in some database or doing some communication, like an email or whatever. We are able to do so and integrate very easily. So we integrate with Twilio, we integrate with Google Mail, Google SMTP, and then we also integrate with CRM applications, and so on.

So it's an event-orchestrated thing. We're able to very easily pick the events that we want, which is very straightforward, and then be able to perform different actions, some communication, and information and data actions, on that event.

We are able to do that in almost a few hours as opposed to several days. This is what's so exceptionally powerful for us.

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.

I have been using Zapier for two and a half years. 

It's a very stable product. The logging is comprehensive and it also has reliable logging applications for all the different states of everything that is logged, which is excellent for troubleshooting issues.

It's possible to scale, but we have not gone too far with it. Given how Zapier is being used currently, I definitely think it's a very scalable product for the volumes that we want. I don't see a problem there.

I don't think we've had any issues with technical support. The only problems that we have had were more about clarifications, for which we called on maintenance staff. And I believe we didn't have a problem with that, nor did we need to use live support at all.

Everything was very straightforward. The first deployment itself was a couple of days. And then every time we have new requests coming in, they're doing it in a day or two. With all the testing and everything, it takes a couple of days, maximum.

We are a small organization with about four or five people working with Zapier. We are the integrators, and we also do a few other things also that Zapier is not able to do. We address some of those gaps in our own implementation.

It's very straightforward licensing. There's only one cost you have to pay, and if you want a relevant pricing plan, I think you have two or three different models or packages which include the number of notifications or Zaps, as they call it, that you can program.

Before we started using Zapier exclusively we also tried Microsoft Flow (now called Microsoft Power Automate). And there was one more product that we looked at. I don't know if it was Appian or something similar.

Microsoft Flow is definitely one of the solutions that we looked at, but Zapier was much more comfortable for us to use. I think Microsoft Flow had a lot more features, but we didn't need them.

I definitely recommend Zapier if your use case is very similar to ours, meaning that it's a bit of task automation between system-to-system. It's a great product.

And if you want to do any unidirectional communication to users, it's also a great product. But if you want to try and push a notification and then get something back from the user, then it's got shortfalls, and you will need to do something more than just use Zapier.

I would rate Zapier an eight out of ten.