Zapier Reviews

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.

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

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

Its integrating feature, especially Facebook Lead Ad Forms to Gmail integration, is the most valuable feature of this product.

This product has made our daily reporting task simpler, by automating and integrating different apps. Now we can automate our campaign leads directly to our clients' Gmail accounts.

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

I have been using this product since December, 2017.

I haven't encountered any stability issues.

I haven't encountered any scalability issues.

The technical support is good. They respond to our doubts and queries, without any delay, through the registered Gmail ID.

I have tried a few solutions for automation, but they didn't support all the apps nor fully serve my purpose. Those are the reasons why I switched.

The initial process is quite straightforward.

Use the free work plan, then you can upgrade to the higher plans. Considering its use, the pricing is pretty good.

I tried the free version of HubSpot before this.

Just try integrating a few basic apps with the free plan or maybe with the $20 work plan. After you get the basics, which are quite easy to learn, you can try the higher plans and more complex integrations.

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.

We use this solution to integrate different third-party software. We use it with service management software such as Zendesk, Freshworks and Jira. When events take place in that software, we use Zapier to pick up that event and perform specific actions. It is used to integrate a number of different solutions. 

The most valuable aspect of this solution is that it is very intuitive and has a very flat learning curve.

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

This is a scalable solution. 

We have not needed any major technical support.

This solution is very easy to start using.

There are three variations of pricing. We use the middle one.

I would recommend Zapier to anybody that is trying to do a similar kind of integration or who has a similar kind of business use case.

I would rate this solution an eight out of ten.