Zapier Reviews

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.

We use Zapier to make connections between our tech tool stack. Google sheets, Hubspot, Totango, Slack, Promoter.io are some of the tools we connect.

Digging further into the tool integrations, we can use the data from one tool we use, connect it with Zaps to another tool to execute data-driven actions.

One example is the user behaviour on our SaaS-platform.

We can make segments with users that show specific behaviour on the platform. With Zapier, we can connect them to mailing tools for delivering specific, targeted content. This means no more mass mailing.

The countless integrations that Zapier makes possible are easy to set up and are valuable. As a SaaS provider, we use countless online tools for dashboards, tracking, and other metrics. Of course, those databases need to interact with each other. When there's no standard integration available, Zapier provides the answer.

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.

Not all Zaps work perfectly the first time. However, most of the time it is the third-party application that is producing the errors. Some Zaps with custom fields are not easy to integrate on the first try.

I only contacted support once, but from that experience, I can say that there was a fast analysis of the problem and a technically skilled support team.

I never tried a different solution. Zapier is the best known integrator with good pricing. It is probably the market leader in its sector. This builds a lot of trust. I see no need to look in the market to compare it with other tools.

There's no real setup involved. Only the different integrations need a setup, which is really supported and guided by Zapier. It's hard to do anything wrong.

The ROI can't be calculated.

Regarding the pricing, start with a basic plan and go forward from there.

If you don't need a lot of integration, Zapier will cost virtually nothing.

Even going to the business plan, it's pretty cheap and you'll get a lot out of it. Only upgrade when you reach your limit of Zaps.

Try the free version first, just to build and test your Zap. You have nothing to lose!

The connection between Facebook lead forms and MailChimp integrations is the most valuable feature.

Furthermore, we started using the integration for Google spreadsheets. It is real handy!

For instance, using a lead campaign for our clients, we gather data, send it to MailChimp to use it in mail-automation campaigns, and also send it to a Google spreadsheet.  The sales team can then follow up on the leads.

Besides this, we send out an email to the people whom it concerns that there is a new lead that requires action on their part.

We can set up marketing automation processes for our clients in a much faster way. Our marketing personnel can do it. We don't need programmers to build complex code.

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’ve used Zapier for about six months.

We have not had stability issues.

We have not had scalability issues.

The initial setup was straightforward. We didn't need any assistance from Zapier.

Think your Zaps through to make sure you don't use more Zaps than you need.

We did not evaluate any other options.

Just start!

The ability to connect web applications to trigger actions in another app after having enriched, formatted, delayed, grouped, and filtered is really valuable for many businesses.

As a SaaS vendor, we need Zapier to create and manage easy automations across the various apps we use "under the wood" for running our business. This helps us make sure that business critical integrations work without requiring the dev team to get involved.

I use it extensively for core-business usage. This includes:

• - Tracking subscriptions lifecycle to trigger actions
• - Managing payments
• - Keeping track or sharing information
• - Helping our customers go further, thanks to our own product integration with Zapier

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.

I have used Zapier for more than three years, and for more than 2 years as a paying customer.

No specific issues.

There were no such stability issues. It works great and warns us if there is any situation that requires our attention/action. For example, if many actions are triggered suddenly.

There were no scalability issues.

I would give technical support a rating of 10/10. They are always relevant and highly efficient.

We previously used IFTTT. Zapier provides email integrations that work in any situation. That was not the case with IFTTT. Zapier offers more freedom and useful features.

The global setup was easy. The only difficulty was getting the proper event to happen in order to build the Zap from that sample data.

We sometimes had a hard time waiting until specific events happened and for some fields to be available for the setup.

The implementation can be easy if you start with simple scenarios.

Then, if you plan on implementing more refined multi-steps zaps, it can become useful to get some support.

Also catching the sample data and filed you're looking for can sometimes be a bit long and reduce the momentum of the project.

Compared to feasibility and the time it would require to collect and spread the data across multiple apps, this is a no brainer: we need such a tool :)

There is a free plan that is, of course, limited. However, it allows you to understand and check true scenarios for a while.

I then upgraded to the professional plan because of a higher frequency to detect triggers, every five minutes, and multi-step Zaps, which are just incredible. It definitely worth the price.

It revolutionized our back-office. We also built many Zaps and therefore needed more quotas.

We tried IFTTT which did not support the same family of apps and did not provide the same feeling/vision.

Start with basic Zaps and scenarios, and then refine them.

Give the Zapier features a try. These include formatter, delay, digest, translate, email, and parser.

Once you've tried it, you'll really enjoy the new world that opens up for you in terms of making stuff work together seamlessly.

We integrate with Zapier, allowing our users to use their services. So, it's important that I am up-to-date on how we can use Zapier to integrate with other platforms.

We integrate with Zapier, thus allowing our users to use their services.

On a personal level, I used Zapier to automate otherwise tedious and manual tasks. For example, my team maintains the Help Center and we collect feedback on how the content could be improved. One way is that whenever someone wants to suggest an improvement, they can do it by answering a few questions in a Typeform. When they submit the Typeform, a Trello card is generated via a Zap that I have set up, so it is added to our backlog.

I have used this solution for two years.

There were no stability issues.

There were no scalability issues.

The technical support team is very helpful.

The setup is not the easiest thing but absolutely learnable. They have improved the UX a lot in the past two years, i.e., ever since I started using Zapier.

If they get stuck, they should check out the help documentation for answers.

• Ability to easily connect almost any API to another API. We can get synergy that wasn't available before.
• Ability to use logical functions and multi-step algorithms for these connections, thus we can avoid triggering certain processes or workflows when we don't want to.
• Customize the web-hook handler which allows us to easily connect our internal applications with all the third-party tools that we use for our business

Improved communication and efficiency through interconnection of instant messaging, email, CRM, ERP and ticket management systems is the main output of using Zapier at Glispa.

Glispa doubled its number of employees last year and this brought a challenge of scaled communication. It was easy to be on the same page when you work in one comparatively small team, but when you have two hundred people with different goals it is hard to be aligned and deliver the best for our clients. However, there are tools which can help teams to be on the same page such email, instant messaging services or CRM tools. The drawback of all these systems is that they are usually independent and updates in one of them will not be seen in another.

With Zapier we tried to connect them and it worked out really well. One of the basic examples can be automation that we use to onboard our customers and handover from sales to account management team. When a sales manager moves his or her deal to the "setup" stage in CRM system with Zapier we send notification to responsible account managers on Slack. If certain crucial information was omitted in a deal, another Zapier automation will send a pre-filled Google form to the sales manager with a request to fill the gaps. When it is done, the account manager gets a nice and shiny handover form and is able to act in a timely manner. Moreover, a respective account is automatically created for the new customer in our ERP system, thus saving the account manager's time.

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

We have used this solution for two years.  

Yes, I personally used for my private automations. I also had some experience with IFTT, but the latter looks significantly weaker in terms of functionality and usability. I also know of an open source project called "Node Red". It looks promising and can give additional flexibility and reliability. However, it requires programming skills.

We did it on our own. I guess vendor's assistance is unnecessary.

We define value by comparing the amount of time that we could have spent developing integrations on our own with the price of Zapier's licence. In casual cases, we saves the time of one full-time developer. It makes total sense to use the paid version of the Zapier. But when it comes to automation of actions that happen more than 5000 times a day, it makes more sense to invest time and money into one's own solution.

If you want to save money on developer efforts and get quick automation, Zapier is the tool. And if your Zap runs more than 1000 times a day, it shows you where development efforts are actually required.

The webhooks allow me to create my own integrations.

It allowed us to create integrations between our own proprietary operations tool, and a variety of other tools like Salesforce, Slack, and HubSpot. Zapier, combined with MailParser, is an essential element of our back-end operations. It allows us to maintain dynamic datasets about customers and sales without a ton of overhead.

We have been using this solution for three years.

There were not stability issues.

There were not scalability issues. This tool is what allows our company to scale.

I've never contacted their support, so I can't say, but their support documentation is always helpful.

I'm not aware of others who can do what Zapier does.

It is a bit complex to learn how webhooks work and how to leverage them. The initial learning curve can be steep, particularly for non-technical people. Once you've learned it, it's quite simple/straightforward. The tool makes it as simple as possible.

We did not evaluate other options.

Be patient and really think about which actions you want automated before you set anything up. Planning and labeling are key to staying organized.

I like the ability to connect one system to another, whereas that wasn’t previously possible without a custom integration.

More automation means less manual work, and improved efficiency for me.

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

I have used Zapier for six months.

Occasionally, we did have stability issues. Sometimes an error is reported, such as a connectivity problem between systems.

We have not had scalability issues.

I rate technical support very high.

The only thing similar was IFTTT. We switched to Zapier because of the integration to Facebook Ads, but have since found it more robust.

Setup was fairly straightforward.

Expect to pay at least $50/month.

We looked at IFTTT and manually doing the work without an integration.

It’s not as difficult as you imagine. Take note that it is a one-way integration solution, not two-way.