Zapier Review

Connects web applications to trigger actions in another app.

What is most valuable?

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.

How has it helped my organization?

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

What needs improvement?

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.

For how long have I used the solution?

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

What was my experience with deployment of the solution?

No specific issues.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

There were no scalability issues.

How is customer service and technical support?

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

Which solutions did we use previously?

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.

How was the initial setup?

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.

What about the implementation team?

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.

What was our ROI?

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

What's my experience with pricing, setup cost, and licensing?

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.

Which other solutions did I evaluate?

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

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment
Sign Up with Email